Classic Fruits 3×3
Legacy frozen math
Draft v2 math — measured
v2-draft-0.1 implements GDD 0.2.0: five fixed paylines, nine regular symbols, no Wild, and a
count-anywhere 7/8/9 SEVENS jackpot paid beside the line wins. The pack is exactly enumerable
(70 stops per reel, 343,000 states), so these are closed-form figures, not estimates:
Against the GDD's 96.08% reference target: −0.0115 pp. A 10,000,000-round run reproduces the
enumeration — RTP 95.97038%, 95% CI [95.70550%, 96.23526%], 0.73 σ from exact, 1300× observed — see
the Draft v2 Math Spec and the report at
evidence/simulation/2026-08-23-draft-v0.1-10m.json.
The 10M run is a measurement. It is not balancing, not a freeze and not certification.
Runtime status
Wired and graded, deliberately not served:
- registered in the canonical pack-hash gate, the reference↔runtime parity corpus (six vectors executed from both sides) and the math-studio authoring registry, whose preset canonicalizes to the identical config hash;
- payout composition, replay identity, forced-grid path and no-double-crediting verified through the real spin orchestrator, including against live PostgreSQL;
- the SEVENS jackpot reaches the client as
wins[].type: "jackpot"and asjackpot_symbols/jackpot_payoutsin the config contract — the word "scatter" reaches the player nowhere.
Nothing serves it to a player. No migration seeds it, no config cache resolves it, no dev gate
admits it; the Game ID classic-fruits-3x3 still resolves to frozen v1.
Known blockers
- Not frozen and not published. Switching DEV to v2 is a separate, explicit decision.
- Hit frequency 11.75% and σ 4.32 have not been accepted by Product; the GDD sets no target for either. This is the one genuinely open math question.
wins[].payouton a line entry is the award for one payline and must not be summed; documented inopenapi.yamland GDD §5 rather than repriced, because the units are the same for every line game.- GDD §7 and §8 still carry the open "confirm against a captured reference round" sentences for the payline-division rule and the 1300× composition.
- The unique-mechanic presentation gate remains open until moving Visual Refs, backend receipts and deterministic DEV scenarios are approved.
- No PAR sheet, no certification evidence, no compliance review.
- Frozen v1 must remain unchanged as historical evidence.
Evidence routing
evidence/exact/— exact calculation artifacts.evidence/simulation/— aggregate simulation reports and manifests.evidence/parity/— reference/runtime comparison.evidence/par-sheet/— generated PAR sheets.evidence/certification/— certification reports.test-vectors/— deterministic portable fixtures.