SESSION PLATE REQUEST — STRUCTURAL / PRESENTATION REFERENCE PACK
UPDATED: 12 SEPTEMBER 2026

PURPOSE
This permanent reference pack contains the accepted structural precedents for future Deterministic Blackjack Session Scorecards. The included plates are presentation/structural evidence only. They must never be used to copy, infer, backfill, transplant, or reverse-engineer current-session numeric values, zeros, N/A values, completion counts, scores, outcomes, or session-specific statements.

CURRENT ACCEPTED STRUCTURAL PRECEDENTS

1. Session7.png — STANDARD COMPLETE COMPARISON PRECEDENT
Use when the current evidence supports a conventional observed Frozen session plus a source-complete Casual counterfactual/reconstruction.
Relevant structural features include:
- observed Frozen journey on the left;
- session identification/comparison evidence in the centre;
- complete Casual counterfactual on the right;
- formal-session summary strip;
- shuffle-robustness table;
- Key Findings / Most Significant Observations / Important Notes / Overall Conclusion footer modules.
Do not force this structure when the current evidence contains a preamble, Hybrid observed journey, source-exhausted reconstruction, or another materially different evidence condition.

2. Session8.png — PREAMBLE / ENTRY-CONTEXT PRECEDENT
Use when the current session has a linked observed preamble or comparable entry/shoe-context evidence that must remain separate from formal-session metrics.
Relevant structural features include:
- a clearly visible PREAMBLE / ENTRY CONTEXT section in the main plate body;
- separate preamble-start Frozen/Casual replay evidence where source-supported;
- formal observed session kept distinct from preamble evidence;
- source-exhausted / not-source-complete reconstruction boundaries shown explicitly;
- formal-session summary excludes the preamble.
Never merge preamble hands/cards/bankroll/exposure/W-L-P/decision totals into the formal session unless the authoritative current-session evidence explicitly defines them as part of that formal session.

3. Session9.png — HYBRID OBSERVED-SESSION PRECEDENT
Use when the current observed live session mode is HYBRID.
Relevant structural features include:
- observed Hybrid player/live journey clearly labelled and authoritative for what was actually played;
- Frozen reference visibility without relabelling the observed Hybrid journey as Frozen;
- Hybrid wager/action comparison and decision provenance shown from current-session evidence;
- a clearly separated HYBRID FORMAL-START COUNTERFACTUAL section for unchanged Frozen and fixed Casual replays where supported;
- source-exhausted counterfactuals shown as N/A outcome with last source-supported bankroll rather than falsely presented as completed final outcomes;
- observed Hybrid formal-session summary kept separate from counterfactual evidence;
- shuffle-robustness results and four closing interpretation modules retained within the accepted visual family.

REFERENCE HIERARCHY
A. Current-session authoritative evidence always has scientific priority.
B. Select the structural precedent according to the evidence scenario; do not simply imitate the immediately previous session.
C. Session8.png remains a strong overall visual-family reference for the established scorecard presentation, while Session7.png and Session9.png provide evidence-specific structural variants.
D. When the current session is Hybrid, Session9.png is the primary Hybrid structural precedent. If that Hybrid session also contains a preamble/entry context, combine only the relevant structural principles from Session9 and Session8 while keeping each evidence layer explicitly separate.
E. If the current evidence introduces a genuinely new scenario not represented by Sessions 7–9, preserve the established visual family but construct an evidence-appropriate module. Do not invent content merely to fill a familiar panel.

EVIDENCE BOUNDARIES
- Observed journey evidence, reconstructed/counterfactual evidence, preamble/entry-context evidence, and synthetic shuffle-robustness evidence are distinct evidence layers.
- A legitimate journey that terminates under a declared bankroll, table-minimum, depletion, exit, or other valid completion rule is COMPLETED when the authoritative source says it is complete; fewer than 30 hands does not by itself make a journey partial.
- SOURCE_EXHAUSTED / NOT SOURCE-COMPLETE counterfactuals must not be presented as completed final outcomes.
- Preserve last source-supported values only with their correct source-boundary label.
- Every displayed zero and N/A is data and requires support from current authoritative evidence.
- Never infer absolute shoe penetration unless an observed shuffle establishes the shoe origin; otherwise report only observed cards since the latest observed shuffle/start.
- Any correction/addendum must remain explicit and traceable. Preserve raw observed evidence and apply only the verified correction layer authorised by the current evidence.

PRESENTATION RULE
Make the PNG visually consistent with this accepted Session Scorecard family: landscape scorecard presentation, strong section hierarchy, aligned panels, established typography hierarchy and colour family, readable dense tables, formal summary strip, findings/observations/notes/conclusion structure, and footer style. Evidence-appropriate structure takes priority over mechanically reproducing a previous plate.

Treat every plate in this pack as presentation/layout evidence only. Do not copy, infer, backfill, or transplant any reference-session numeric value, zero, N/A, completion count, score, card count, outcome, or session-specific statement.

LEGIBILITY AND AUDIT
All values, decimal points, currency symbols, percentages, headings, footnotes, and multi-column table entries must remain comfortably readable at normal full-plate viewing size. After rendering, audit every displayed number and substantive label against the frozen current-session manifest and authoritative evidence. Rendering alone does not make a plate COMPLETE.

PACKAGING
All files that actually need to be placed into the working blackjack environment must be supplied together in one ZIP using their exact production filenames so the user does not need to rename them after extraction. Presentation-only artifacts such as generated PNGs or audit/support files should remain outside the runtime environment ZIP unless the workflow explicitly requires them.
