Standout Builder Studio · planningIndex / Examples / Import · Golden GalleonreviewUpdated 12 Jun 2026
Worked example · Golden Galleon (existing-game import)
A third-party studio has a finished treasure pick'em — three screens and a PDF info sheet — and
wants it on the platform today. This example traces the full import path: upload, extraction,
mechanic matching, prefilled spec, and handoff into the normal guided flow. The headline: from
"we want our existing game on your platform" to a signed-off spec by the same afternoon.
The uploads
The builder selects Import existing at the
Build Path Picker and is presented with a
drop zone accepting screenshots and a PDF info sheet. Screenshots are optional but helpful —
they give the Info-Sheet agent visual context
for paytable layout and bonus-round structure. The PDF info sheet is the richer
source: it carries structured math targets, RTP declarations, and formatted field data
that screenshots rarely include.
Import upload drop zone — Golden Galleon
CONCEPT · proposed
Drop files here or click to browsePNG / JPG screenshots · PDF info sheet · max 50 MB per file
PNG
galleon-base-game.png
screenshot · base-game round in progress
2.1 MB
Ready
PNG
galleon-bonus-round.png
screenshot · free-spin bonus round
1.8 MB
Ready
PNG
galleon-paytable.png
screenshot · paytable and prize structure
1.4 MB
Ready
PDF
golden-galleon-info-sheet.pdf
info sheet · 11 pages · primary extraction source
11 pp
Primary
4 files ready · extraction will begin on confirm
Why the PDF is the richer source
A well-formed info sheet carries RTP declarations, paytable row counts, max win figures,
and mechanic descriptions in structured prose — exactly what the
Info-Sheet agent is trained to parse.
Screenshots add paytable visual layout and bonus-round context, which raises confidence
on fields the PDF may describe ambiguously. Neither is required to proceed; the agent
flags whatever it cannot resolve for human correction.
The extraction
The Info-Sheet agent parses the uploaded PDF
and screenshot set, producing a manifest field table with a confidence score per field. High-
confidence fields (≥ 0.90) are pre-filled and marked green. Medium-confidence scores are shown
in amber; only the low-confidence volatility row is flagged for mandatory review at this stage.
The agent never auto-commits a value it is uncertain about.
Extraction is assistive — never silently authoritative
Every extracted value is a proposal, not a commitment. Low-confidence fields
(volatility at 0.62 in this example) are explicitly flagged and cannot be committed
without human sign-off. Medium-confidence fields are pre-filled but highlighted amber —
the builder must actively confirm or correct them before the spec is locked. Nothing in
the extraction output auto-commits to the GameSpec record without the
builder's review. The agent's job is to reduce blank-form fatigue, not to replace
human judgement on numbers that affect player outcomes.
The match
Once the mechanic label is extracted ("n-choice pick"), the system queries the
mechanics library for the nearest
certified mechanic. Golden Galleon's structure — three choices, turn-based, single-player
session — maps closely to Trunk Raider's three-choice pick'em. The similarity is high but
not complete: the bonus hooks differ, which the system surfaces before any path is chosen.
Mechanics library — nearest match result
CONCEPT · proposed
Decision shape matches: both are n-choice pick mechanics — the player selects one option from three per turn, each resolving to a multiplier or bonus state.
Session model matches: both are turn-based, single-player sessions — no shared-world state, no real-time cashout timing.
Bonus hooks differ: Golden Galleon uses triggered free spins — a randomly triggered bonus round layered onto the base pick'em. Trunk Raider's bonuses are earned through play (threshold-based: Silent Pick at round 15, Informant at round 32, Cheat Code at round 65). These are structurally different bonus state machines.
The bonus-hook difference is flagged before the builder commits to a path. Two options are
offered as explicit choices:
Option A — recommended · fastest path
Build as a Trunk Raider variant
Map Golden Galleon onto the Trunk Raider mechanic. Adapt the bonus expectations: the
triggered free-spin concept is noted in the spec, and the bonus hooks are configured
using Trunk Raider's earned-through-play threshold model. The builder documents the
delta in the spec; it will be surfaced during math review. No new mechanic is needed
— this path enters the guided flow at step 2 immediately.
fastest · same-day spec
Option B — slower · engineering-assisted
Flag a mechanic gap
Request "n-choice pick + triggered bonus" as a
new library mechanic. This creates a
mechanic-gap work item and initiates an engineering-assisted new-mechanic proposal. The
path is correct if triggered free spins are a first-class design requirement and adapting
the Trunk Raider threshold model would misrepresent the game's intent. Expect days to
weeks before a new certified mechanic is available.
slower · days to weeks · engineering required
Which option is right?
Option A is the right choice when the free-spin trigger is a bonus flavour rather than a
structural mechanic requirement — i.e. when the player experience can be faithfully
delivered via the Trunk Raider bonus threshold model with different thresholds and
documented expectations. Option B is the right choice when triggered free spins are a
non-negotiable design element that a threshold model cannot represent without misleading
the math record. The builder makes this call; the platform surfaces both options honestly
with their respective costs.
The prefilled spec
Assuming the builder selects Option A, the spec form is pre-populated with extracted values
and presented for review before entering the guided flow. High-confidence fields appear
in green — the builder may accept them as-is. The two lowest-confidence fields in this
example — volatility (0.62) and max win (0.75) — are highlighted amber and require explicit
confirmation; the rest auto-confirm. The form entry point is
step 2 of the guided flow.
Prefilled spec form — Golden Galleon · import path
CONCEPT · proposed
From here it is the normal flow: the import path merges into the standard funnel from the
Build Path Picker at step 2, with the
extracted and confirmed values already in the spec. The builder completes mechanic
configuration, attaches assets, and runs validation exactly as for any Trunk Raider variant.
The clock
Elapsed time from file upload to spec entry. Agent steps are measured in seconds;
the human review window dominates.
0:00
Files uploaded
Three screenshots and one 11-page PDF info sheet uploaded to the drop zone; extraction triggered on confirm
0:04
Extraction done
Info-Sheet agent parses PDF and screenshots; six manifest fields extracted with confidence scores; field table presented to builder
0:06
Match proposed
Mechanics library returns Trunk Raider as nearest match (87% similarity); bonus-hook difference flagged; two path options presented
0:20
Human corrections
Builder reviews amber fields (max win · volatility), confirms mechanic match (Option A — Trunk Raider variant), adds bonus delta note; all fields confirmed
0:25
Enters guided flow at step 2
Spec confirmed and locked; builder routed to step 2 · Define the game package with extracted values pre-filled — the import path merges into the standard funnel
Twenty-five minutes from "here are our files" to a confirmed spec entering the guided
flow — and most of that is the human review window, not the agent. This is the path that
turns "we want our existing game on your platform" into a same-day spec: extraction reduces
blank-form time from hours to minutes, mechanic matching surfaces the decision that matters
(adapt vs gap), and the prefilled form eliminates transcription work entirely.