Gameplay Framework Walkthrough — one mission, every piece

Reference / worked example — one simple mission walked start to finish, with a tag at each beat showing which framework piece fires. A coherence test (does the A–F system actually run end to end?) and an onboarding read (the whole loop in one page). It instantiates the framework; it introduces no new canon — where a beat and a per-system doc differ, the per-system doc (and its ADR) wins.

Date: 2026-06-21
Related: the connective map gameplay-framework.md; the companion walkthroughs gameplay-framework-walkthrough-depthcharge.md (the same A–F tags on DEPTHCHARGE — the generalization test) gameplay-framework-walkthrough-black-ledger.md (BLACK LEDGER — the program/cart-boundary test), and gameplay-framework-walkthrough-neongrid.md (NEONGRID — the floor / borrow test), where this is the coherence test; and the per-system docs each beat cites:
Source: docs/software/gameplay-framework-walkthrough.md

runtime/mission-control.md (board ↔ UDS) · runtime/mission-objectives.md (objective graph) · runtime/currency-and-economy.md (currencies)
cartridges/design-bibles/mission-type-catalog.md (A) · cartridges/authoring/verb-partition.md (B) · runtime/recon-mode.md (C) · programs/enrichment-contract.md (D) · cartridges/authoring/capability-shapes.md (E) · programs/knsalk.md (F) · programs/dossier-data-model.md (DOSSIER) · cartridges/modules/ice-breaker.md (the cart)

Scope: a deliberately simple job — one cart (ICE BREAKER), low threat, a single EXTRACTION. No multi-cart campaign, no exotic edges. The point is to show the pieces interlock on the ordinary case.

The contract: GLASS PAYROLL — lift a corp’s payroll ledger

0 · The board

Operator HOSHIKO boots. Mission Control synthesizes the board seeded by Universal Deck State — reputation sets the threat tier, cartridge_history shows ICE BREAKER registered, cipher_seed is the entropy. One contract surfaces: EXTRACTION · NETWORK · T2 · ¤900. → foundations: Board ↔ UDS (mission-control.md §3)

1 · The type

The board prints the class EXTRACTION = the Tier-3 verb OBTAIN × the affinity NETWORK — the player-legible “data exfil.” A single-type job, not a composite arc. → A (mission-type-catalog.md)

2 · Accept → the objective graph loads

○ P1  Breach the payroll subnet       ¤300        primary · briefed · on-complete
○ P2  Exfil the ledger                ¤600        primary · briefed · :requires P1 · on-resolve
+ O1  Ghost run — :hold (trace < 40)   +3 REP      optional · briefed · on-resolve (escrow)
◌ O2  [latent] Exec bonus dataset     ¤400 +INTEL  optional · revealed @ HR node · on-resolve

Mission succeeds when P1 + P2 are :done. → foundations: objective graph (mission-objectives.md, ADR-0043)

3 · Recon (HOSHIKO plays measured, not rip-and-run)

She drops into recon mode and opens bzbx against the target’s simulated network — the cart supplied that world via (launch-app :bzbx :world …); there is no real network. A passive SCAN (≈ free heat) maps the surface; one active PROBE on the finance node (a little heat) surfaces a fact → (dossier-commit acct:payroll:topology). → C recon mode + heat (recon-mode.md) · D enrichment / simulated world (enrichment-contract.md)

4 · DOSSIER

The key lands as a fact-node under a :target profile (GLASS-CORP) — :prov (mission … :via bzbx), :conf :verified. Now (dossier-has? acct:payroll:topology) → true, which de-risks the breach (pre-revealed topology → fewer nodes / lower start difficulty). (A rip-and-run operator skips step 3 and jacks in blind — both styles are valid.) → foundations: DOSSIER (dossier-data-model.md); the recon → intel → de-risk loop

5 · Jack in — `(load-capability :ice-breaker)`

ICE BREAKER’s capability is a mini-game — the real-time OODA netrun. Inside it HOSHIKO works Tier-2 action verbs: CORE CRACK (defeat the ICE layer) and a COMPOSITE GHOST = CONS(MASK, JUMP) to ride under the logging threshold for O1. She reaches FINANCE → (goal-complete 'P1) → ¤300 banked (on-complete). → E capability shape: mini-game (capability-shapes.md) · B CORE + COMPOSITE verbs (verb-partition.md)

6 · The fork

Pushing toward the ledger she hits the HR node → (goal-reveal 'O2) (the exec bonus appears). Grabbing it means more time in-system → trace climbs toward 40, threatening the O1 ghost. She goes for it. Trace rises. → foundations: latent reveal + risk-coupled escrow (mission-objectives.md §3)

7 · They hit back

The accumulated heat (the active PROBE in step 3 + the O2 greed) crosses the threshold → counter-intrusion. knSALK’s passive shield eats the first probe, but it’s serious → breakthrough → the netrun interrupts → the active stand: HOSHIKO defends with DEFENDER verbs — QUARANTINE the trace payload, BANISH the intruder (a grammar engagement — the other capability shape, in the same run). Her hardened knSALK (bought earlier with credits) wins the stand — but the spike pushed trace over 40. → F knSALK: heat-triggered, passive → active (knsalk.md) · E grammar shape — both shapes fired this run

8 · Resolve — `(complete-mission)`

Both primaries :done. Settlement:

Goal	Reward	Outcome
P1	¤300	kept (banked on-complete)
P2	¤600	paid (mission succeeded)
O1	+3 REP	forfeited — the ghost was broken by the trace spike
O2	¤400 + INTEL	paid — grabbed and survived

One sanctioned UDS write (ADR-0040 §6): credit_balance += 1300, reputation += the success delta (no ghost bonus), ICE BREAKER mastery += threat-weighted, the O2 intel key → DOSSIER, cipher_seed advances, phase_chain clears. New mastery nudges the next board; the banked key de-risks a future GLASS-CORP follow-on. → foundations: economy — all four currencies move (currency-and-economy.md)

Coverage — every piece fired

Piece	Where
A — mission-type catalog	EXTRACTION = OBTAIN × NETWORK (§1)
B — verb partition	CORE `CRACK`/`FETCH` + COMPOSITE `GHOST` (§5); DEFENDER verbs (§7)
C — recon mode	bzbx casing, passive/active heat (§3)
D — program enrichment	bzbx + the simulated network via `launch-app :world` (§3)
E — capability shapes	ICE BREAKER mini-game (§5) and knSALK grammar stand (§7) — both in one run
F — knSALK	heat-triggered counter-intrusion, passive → active stand (§7)
objective model	the goal graph + escrow forfeit (§2, §8)
economy	¤ + reputation + mastery + intel all move (§8)
DOSSIER	fact-node + `dossier-has?` de-risk (§4)
Board ↔ UDS	seeded board, sanctioned write (§0, §8)

Why this proves coherence

The cleanest tell: the heat HOSHIKO spent on offense (the recon PROBE + her greed at the HR node) is exactly what summoned the defense. Recon (C) and knSALK (F) are not two systems — they are one heat meter read from both ends. And a single ordinary run naturally exercised both capability shapes (E): a real-time mini-game for the breach, a grammar engagement for the defensive stand. Nothing was bolted on to make the example work; the pieces fit because they were designed against one shared spine.

A rip-and-run variant of the same contract — skip §3/§4, jack in blind, stay cold, no counter-intrusion — is equally valid and exercises a different subset. That both playstyles run on the same machinery is the point.