A builder wants a higher-volatility cut of Trunk Raider: same mechanic, same pick-em structure, no engine changes — just four config knobs pushed toward more extreme outcomes. This example traces the config diff, the Math-Sim proof run that validates it, the human math-owner gate that separates a tune from a reskin, and the resulting sandbox session. The math gate is the story.
At the Build Path Picker, the builder selects Tune (config-only variant) — the path that branches from an existing mechanic and allows config field changes, but no mechanic code changes. The base game chosen is Trunk Raider (trunk-raider in the mechanics library — certified, RTP 96.0%, turn-based pick-em with bonus escalation).
TrunkRaiderConfig schema — betting limits, multiplier ranges, bonus thresholds,
and the free-round counts. Volatility retuning is the canonical use case: push the
multiplier ceiling up, raise the threshold for bonuses to trigger, and the game plays harder
with the same base mechanic. The scaffold PR is auto-raised against the certified
base-game reference; no mechanic changes are permitted within this path.
Trunk Raider: Overdrive changes exactly four config fields. Everything else is inherited verbatim from the base game. The table below shows all changed and unchanged rows; tunes are judged by their deltas — the smaller the diff, the easier the Math-Sim proof.
Note on defaultRtp: it is inherited unchanged at 0.96 (96%). This is
intentional — the target stays the same. The Math-Sim agent must prove that
the new, more extreme multiplier ranges and adjusted thresholds still land on that
target within tolerance. That proof is what the math gate is for.
| Field | Group | Base (Trunk Raider) | Build (Overdrive v0.2.1) |
|---|---|---|---|
|
minBet
Minimum bet amount
|
Betting | 0.25 | 0.25 ≡ |
|
maxBet
Maximum bet amount
|
Betting | 1000 | 1000 ≡ |
|
defaultRtp
RTP target — must be proved by sim
|
Math & RTP | 0.96 (96%) | 0.96 (96%) ≡ |
|
cheatCodeThreshold
Rounds needed for Cheat Code bonus
|
Bonuses | 65 | 65 ≡ |
|
informantFreeRounds
Free rounds granted on Informant
|
Bonuses | 5 | 5 ≡ |
|
cheatCodeFreeRounds
Free rounds granted on Cheat Code
|
Bonuses | 10 | 10 ≡ |
|
winMultiplier
Base win multiplier range
|
Math & RTP | {0.1–5.1}× | {0.1–5.1}× {0.05–8.0}× |
|
cheatCodeFirstPickMultiplier
Cheat Code first-pick multiplier range
|
Math & RTP | {0.1–1.9}× | {0.1–1.9}× {0.1–2.6}× |
|
silentPickThreshold
Rounds needed for Silent Pick bonus
|
Bonuses | 15 | 15 12 |
|
informantThreshold
Rounds needed for Informant bonus
|
Bonuses | 32 | 32 40 |
Four changed fields out of the full config. Tunes are judged by their deltas — the diff is the proof surface the math owner reviews.
The Math-Sim agent consumes the saved config and runs a 10-million-round simulation, producing an RTP proof artefact and a volatility/max-win summary. This is the primary evidence the math owner reviews when the gate opens. The sim is queued automatically when the last math-touching field is saved.
10M rounds · these figures are illustrative; the RTP pass / tolerance band and the version reference (95.97% vs 96.00 ±0.25) are consistent with the agent feed in Architecture · agent workforce.
rtp-proof #341 — running simulation against config v0.2.1rtp-proof #341 — RTP within tolerance, volatility class confirmedThe validation panel for this build mirrors the step-5 hi-fi mock in Vision, titled "Validation · Trunk Raider: Overdrive v0.2.1". Two states are shown below: the gate panel before the sim completes, and after the math owner approves.
When the builder first opens validation, the sim is queued but not yet complete. The RTP sim proof gate shows a Warn — the last proof was for a prior version and does not cover the new config. The math gate row is amber: it cannot resolve until the sim proof is attached.
The Math-Sim agent posts the sim result to the work item. The math owner reviews the proof (RTP 95.97% vs target 96.00% ±0.25 — PASS, volatility class now High) and approves. Both gates move to green.
rtp-proof #341.rtp-proof #341 — RTP within tolerance, volatility class confirmed. Build cleared for sandbox-to-promote.All gates green. The build is cleared for sandbox-to-promote.
Elapsed time from path choice to playable sandbox session, in hours:minutes. Agent steps are fast; the human gate dominates.
rtp-proof #341; 10M-round simulation beginsrtp-proof #341; all validation gates greenThree hours and ten minutes from "Add a game" to a live sandbox session. The sim takes seventy-five minutes; the math owner's review window accounts for most of the rest. A day-scale path, dominated by the human gate — which is the point.