77 lines
4.1 KiB
Markdown
77 lines
4.1 KiB
Markdown
# SPRINT 8 — SHIP THE WEEK (instructions for Opus 4.8 lanes)
|
||
|
||
*Sprint 7's gate 0 was this repo's best hour as an engineering team: B refuted
|
||
with an elimination sweep, C brought a third witness and instrumented the
|
||
breaks, D found the settle (the cause nobody's candidate list had), A
|
||
post-mortemed their own undeclared tension and made testkit's skips real. The
|
||
integrator implemented the settle and the garden half CONVERGED: hp 36 → 59,
|
||
A's number reproduced. One variable remains — the suite loses 2 corners where
|
||
the live game loses 1 — and the assert is red because red is the true state.*
|
||
|
||
*And: THE WEEK HAS SLIPPED TWICE. This sprint it ships. Gate 0' goes to B+D so
|
||
that A builds the week uninterrupted from day one.*
|
||
|
||
Read THREADS from the last [I] entry.
|
||
|
||
## Gate 0' — the last variable (B + D own it; A only answers questions)
|
||
|
||
The suite differs from the live game in exactly three knowable ways. Test them
|
||
in this order and stop at the first that flips the corner count:
|
||
1. **Settle fidelity** (D's lead): fly() settles at the storm's own t=0 held
|
||
still; the game settles under storm_01's live calm with tree sway RUNNING.
|
||
Settle under live calm wind + live sway, then swap to the storm.
|
||
2. **Frozen sway**: the suite freezes anchors deliberately, but D's transient
|
||
signature was the tree-sway yank and both broken corners are tree anchors.
|
||
B measured live-sway-worse once (pre-settle) — re-measure it settled.
|
||
3. **Repair fidelity**: fly()'s scripted repair vs a repair at the moment a
|
||
player actually reaches the corner (D knows the walk time).
|
||
Land D's settled-at-entry guard while you're in there. Outcome A: the line
|
||
wins → assert green, gate closed forever. Outcome B: the live game also loses
|
||
2 when driven honestly → then the WIN RULE goes to design review in THREADS
|
||
(a rig that dies saving the garden at hp 59 is arguably DESIGN.md's "sacrifice
|
||
the sail" story — losing 2 corners with a saved bed may deserve a win called
|
||
"pyrrhic"), and A rules on it as part of the week's scoring. Either outcome,
|
||
post the numbers like B post-mortemed decision 11.
|
||
|
||
## Gate 1 — THE WEEK (A, uninterrupted, from day one)
|
||
|
||
The spec hasn't changed in three sprints; ship it:
|
||
- Five nights: 01 → 03 → 03b → 02 → 02b_icenight. C's variants exist.
|
||
- Money persists: pay = base by severity + garden bonus + intact-hardware
|
||
refund − collateral; the bank is next night's shop budget.
|
||
- Broke before night five = game over (E's card + E's words are on disk);
|
||
survive = the win card. The dawn-tint CSS is also on disk — paste it.
|
||
- "Play again" → "next night". Night counter on the forecast card.
|
||
- E's card text is drafted (THREADS 2026-07-18) — take, edit or bin.
|
||
Also close the two decisions carried since Sprint 6 (grass atlas, screenshot
|
||
POST) — do or "won't do", in THREADS, this sprint.
|
||
|
||
## Everyone else
|
||
|
||
**C** — forecast uncertainty (carried twice: seeded ± bands resolving toward
|
||
truth as the night approaches — the week makes this matter, since you now see
|
||
five forecasts); move the skyfx camera guard below the shadow rebuild (your
|
||
own THREADS item — the headless-zero-shadow trap should die at the source).
|
||
**D** — after gate 0': the full-week feel pass, the last read before John
|
||
plays. Douse guard check if pond masses moved.
|
||
**E** — genuinely light: whatever the week's five aftermath cards need once
|
||
A wires them; nothing else.
|
||
**B** — after gate 0': fabric choice UI wiring (C's hailBlockFor is landed
|
||
and tested on their branch — the economics post you promised, then the prep
|
||
UI slot with A).
|
||
|
||
## Gates
|
||
|
||
```
|
||
gate 0': the corner-count variable named and closed — assert green OR the
|
||
pyrrhic-win rule lands, numbers posted either way
|
||
gate 1: the week runs end to end — five nights, money carries, game over
|
||
and win cards live — played, screenshotted, in docs/
|
||
gate 2: John plays the week; three sentences in THREADS
|
||
```
|
||
|
||
After this sprint the game is whole at every scale it has. Sprint 9 opens
|
||
DESIGN.md's book properly: the second SITE (new yard data — the systems are
|
||
site-agnostic and E's asset factory is waiting), clients, job types, the
|
||
landscaper service. That's the game becoming the game.
|