diff --git a/LANE_PROMPTS.md b/LANE_PROMPTS.md
index b2a85bf..fd0196c 100644
--- a/LANE_PROMPTS.md
+++ b/LANE_PROMPTS.md
@@ -382,3 +382,47 @@ measured in THREADS' last [I] entry). Gate 1 is JOINT and comes first.
 > Night dressing for the week's later storms (moon, lit house window),
 > win-screen and game-over cards that feel like SHADES, and refresh the
 > contact sheets once the balance pass lands.
+
+---
+---
+
+# SPRINT 7 prompts (one truth, then the week)
+
+Same rules: own clone, own branch, rebase onto latest main FIRST. Read THREADS'
+last [I] entry (the harness dispute) then SPRINT7.md. Gate 0 is A+B jointly
+and NOTHING else lands before it.
+
+## Lane A — Sprint 7
+> You are Lane A on SHADES 3D, Sprint 7. Rebase onto main, read THREADS' last
+> [I] and SPRINT7.md. Gate 0 first, paired with B on balance.test.js: reproduce
+> your hp-58 win there or find why it doesn't (tension? repair timing? drain
+> path?) — post the cause like B post-mortemed decision 11, delete the
+> integrator skip. Then gate 1, the week: five nights (C's icenight is night
+> five), persistent money, broke = game over, survive = E's win card with your
+> text. Wire window_glow + moon for the night storms. Close the carried grass
+> and screenshot-POST decisions — do them or write "won't do".
+
+## Lane B — Sprint 7
+> You are Lane B on SHADES 3D, Sprint 7. Rebase onto main, read THREADS' last
+> [I] and SPRINT7.md. Gate 0 first, paired with A on balance.test.js — your
+> suite is the single truth now; make it reproduce or refute A's win, name the
+> cause. Then fabric choice per C's ruling: honest pricing + stone-size hail
+> pass-through (ask C for hailBlockFor), fabric economics posted in THREADS
+> before UI so A can slot prep.
+
+## Lane C — Sprint 7
+> You are Lane C on SHADES 3D, Sprint 7. Rebase onto main, read SPRINT7.md.
+> Land hailBlockFor(size, porosity) when B asks; forecast uncertainty bands
+> (carried — seeded ±, resolving toward the real numbers as the night nears);
+> stand by on gate 0 in case the drain-wiring path is the discrepancy.
+
+## Lane D — Sprint 7
+> You are Lane D on SHADES 3D, Sprint 7. Rebase onto main, read SPRINT7.md.
+> When gate 0 closes: the feel pass on the final balanced storms — it's the
+> last read before John plays the week — plus the douse re-measure if pond
+> masses moved (your guard assert is the tripwire). Until then, hold.
+
+## Lane E — Sprint 7
+> You are Lane E on SHADES 3D, Sprint 7. Rebase onto main, read SPRINT7.md.
+> Light sprint: card text pass with A once the week exists, a dawn tint for
+> the morning-after aftermath if cheap. You've earned the short one.
diff --git a/SPRINT7.md b/SPRINT7.md
new file mode 100644
index 0000000..0410764
--- /dev/null
+++ b/SPRINT7.md
@@ -0,0 +1,68 @@
+# SPRINT 7 — ONE TRUTH, THEN THE WEEK (instructions for Opus 4.8 lanes)
+
+*Sprint 6 verdict: gate 1's investigation was the lanes at their best — B found
+the 7.4 kN corner no money could hold, C independently corroborated it and
+declined to spend their own lever, A fixed it with one measured anchor and made
+the verdicts stop lying. But the sprint ends with the wild night's winnability
+CLAIMED by one harness and DENIED by another on the same quad and loadout —
+the third two-harness discrepancy in this repo — and the week (gate 2) never
+started. Sprint 7 closes the dispute first, then ships the campaign.*
+
+Read THREADS from the last [I] entry.
+
+## Gate 0 — ONE TRUTH (A + B, first, nothing else lands before it)
+
+`balance.test.js` is the single source of truth from now on. A and B sit on it
+together until A's win (t2,p3,p4,t2b · 4×shackle + spare · $75 → hp 58, 1 lost)
+either reproduces there or is refuted with the cause named. Check in this
+order: **tension** (the shop defaults 0.9 — what did A rig at? A's line may
+simply want 0.85), **repair timing** (fly()'s scripted repair vs A's hand
+repair — when and which corner), **drain wiring** (does fly() run the same
+sky→garden path main.js runs, including my HAIL_WEIGHT wiring). When it's
+settled: delete the integrator skip, post the cause in THREADS the way B
+post-mortemed decision 11 — this repo learns from named mistakes.
+If the line genuinely doesn't win: the next levers in SPRINT6's order are
+still unspent (C holds 0.40 downdraft proven safe; win bar last).
+
+## Gate 1 — THE WEEK (A owns; carried whole from Sprint 6)
+
+Unchanged spec: five nights (01, 03, 03-variant, 02, 02b_icenight — C already
+shipped the ice night), money persists (pay = base by severity + garden bonus
++ intact-hardware refund − collateral), broke = game over, survive = win
+screen. E's end cards are on disk (diptych, left third reserved for your
+text). "Play again" becomes "next night". One file if you can.
+
+## Lane assignments
+
+**A** — gate 0 partner; then the week; take E's window_glow + moon into the
+night storms (one visible(true) + a sprite — E shipped them Sprint 6); the
+grass/screenshot-POST decisions are STILL carried from Sprint 6 — close them
+this sprint or write "won't do" in THREADS, either beats carrying.
+**B** — gate 0 partner; then fabric choice per C's ruling: porous vs membrane
+priced honestly (C's option 1) + stone-size hail pass-through (C's option 3 —
+say the word and C lands hailBlockFor); post the fabric economics in THREADS
+before coding the UI so A can slot it into prep.
+**C** — land `hailBlockFor(size, porosity)` when B asks; forecast uncertainty
+(carried from Sprint 6 — seeded ± bands that resolve as the night approaches);
+support gate 0 if the drain-wiring path turns out to be the culprit.
+**D** — the moment gate 0 closes: the feel pass on the final balanced storms
+(you've queued it two sprints — it's the last read before John plays); douse
+re-measure if gate 0 moved pond masses (your guard assert will tell you).
+**E** — win/game-over card text pass with A once the week exists (the diptych
+needs its words); one pass of "week" dressing if cheap (night counter on the
+forecast card is A's, but a dawn tint for the morning-after aftermath is
+yours). Otherwise a light sprint — you've earned it.
+
+## Gates
+
+```
+gate 0: balance.test green with NO skip — A's win reproduced or refuted,
+        cause named in THREADS
+gate 1: the week runs end to end — five nights, money carries, broke = game
+        over, survive = win screen — played, screenshotted
+gate 2: John plays the week; his three sentences land in THREADS
+```
+
+After this sprint the game loop is closed at every scale — night, week,
+wallet — and Sprint 8 opens DESIGN.md's real book: sites, clients, job types,
+the landscaper service.