0.80 adopted as E proposed, reasoning endorsed not re-derived: it earns the
highest rung below the sail post because it is the only palette structure BUILT
to be tied to, and it stops short of 1.00 for section rather than condition.
De-rating honest steel for looking dangerous is the corroded post's lie
inverted, and one of those on a ladder is a trap — two is a pattern the player
learns to distrust generally, which would cost the rust post its teeth. The
"it usually holds" half is ruled IN explicitly: the lesson is "the same failure
has a different price depending on what is underneath it".
Palette hunk applied verbatim to editor.js (eighth application), with E's three
warnings carried into the code. HIDDEN on bare lane/a by `requires` — the
self-healing seam that filter was written for — so it appears by itself at merge
with no third commit. ANCHOR_TYPE widening ENDORSED, deliberately NOT duplicated.
E asked for a second one-variable law (a new TIER must not debut with the
callout). I built it, measured it on E's own poisoned scenario, and it returned
ZERO offences: rule 2 already requires the emergency's yard to be rigged by a
strictly earlier night, so every tier resident in that yard necessarily debuts
on that earlier ordinary job. Permanently green for a structural reason — the
exact shape of my own S17 stormsToPreload filing. Deleted rather than shipped;
the measurement lives in board.js beside the rule it would have extended.
⚖️ Gate 5: the gnome BELONGS in exposureOf and stays — the two harnesses differ
because they answer two questions, and that difference is legitimate where
$45-vs-$90 was not. After E's world.js hunks the remaining delta should be
exactly the gnome and nothing else.
Selftest 539/0/0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Eyes on the cards found what the suite structurally cannot:
· the board advertised $57 while the dispatch quoted $114 one click apart — the
quote-vs-settle lie walking back in through an unreachable closure inside
boot(). pricedOffers is now the exported pure priceOffer(), rigRecordFor's
precedent, and the bug has its own pin.
· the emergency wore the same grey "callout" tag as the Tuesday alternative
beside it — the tell rule broken on the surface the tell rule is for.
· the invoice argued with itself: the ledger said CB1 "is not on you" and the
verdict blamed CB1. verdictFor now reads `yours`, and the ruling is extracted
as answerableFor() so the RULING is pinnable, not just its consequences.
· the shop lied by $20 — the session charged me for the cowboy's carabiners.
· "the Hendersons IS expecting you", live, on the ruling's headline line.
Gate 5 (A's half): collateralKeyClashes() turns D's second-rust-post landmine
into a tripwire carrying both harnesses' numbers. It reports and does not throw
(D and E are authoring in parallel), and it deliberately does NOT make
exposureOf dedupe — the card is the honest side, the failure route is what needs
per-instance keys, and matching a bug converts a loud disagreement into a quiet
lie.
⚠️ RETRACTED IN THREADS: my $180 balance measurement is contaminated. C found
SailRig.step accepts `t` and never reads it, so setPhase('storm',{at:30}) moves
the sky and not the cloth (4.12× understated load, 93× light rain). B must not
rule the garden bonus against my $38. The TELL survives — CB1 still blows at
t≈33 — the ECONOMY does not.
Selftest 539/0/0 — 522 + 17, the exact sum. 19 mutations, all red with their own
words, controls green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The gate-4 entry says to check asset_report.json's `blender` field before
building. My own run then regenerated that file, so it reads 5.0.1 while 37 of
the 39 GLBs beside it are still the 5.1.2 exports I reverted — the field now
says "you are on the right Blender" precisely when you are not.
Same defect shape as everything else this sprint hunted: a source of truth that
quietly starts answering a different question. Recorded rather than papered over,
with what is actually true of the committed tree (my two files are 5.0.1, the
other 37 plus all textures are untouched 5.1.2), why reverting was still safe
(the report's per-asset facts are identical either way, measured), and the check
that does not lie: build, then git status — if files you did not author come back
modified, you are on the wrong Blender.
The generated file is left alone deliberately. It says do-not-hand-edit, and a
doctored report is worse than a mislabelled one.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two entries at the tail. Gate 4: the premise correction (S16 already shipped the
glasshouse; the gap was that its $320 could not be reached), the asset, the tell
measured twice, the 0.80 rung with the reasoning beside it, the five controls,
the determinism result, the Blender 5.1.2-vs-5.0.1 finding, placement facts and
the wreck apron, plus the editor palette hunk verbatim for A and the flag that
the tier is placeable — with the one-variable law restated as A's to enforce.
Gate 5: my half (two author-time pins) and the exact wiring A needs — why
renaming the structures' keys alone makes it WORSE (the anchors take their key
off the baked GLB node, so both stop matching and both corners become free),
the two world.js hunks and the validateSite refusal, and what it buys: D's
$115-vs-$45 split closes to $115 vs $90, leaving exactly the gnome's $25 as
A's ruling rather than two unknowns.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Seven new pins, ten new rows (the two assets also add dims/nodes rows).
Gate 4 — the tier:
· the frame BRACKETS the glass: footprint strictly contains the glasshouse's
on both axes, head clears the ridge by 0.47 m, all four eyes above it. The
tell is a measurement because the tell is a position.
· the 20 m read is METALNESS not lightness: powder-coat <= 0.15, galvanised
>= 0.6 as the control, and the paint the brighter base colour. An assert
whose stated reason is the mechanism, so the docstring cannot be "fixed"
the wrong way (S17's inverted-sign lesson).
· a NEW RUNG at 0.80, pinned against the MANIFEST not a literal: above the
pergola, below the post, collateral 'glasshouse', four agreeing sources.
· the APEX IS REACHABLE — this one was RED by construction before this
sprint, and its message says why. Plus the corollary: nothing but the
glasshouse may CLAIM its key.
· the wreck folds at one end, keeps its height, carries no glass, offers no
anchor, and is unpriced by ruling.
Gate 5 — D's second-rust-post landmine, disarmed at author time:
· no shipped yard gives two structures the same resolved collateral key
(mirrors structKey() exactly), and structure ids are unique — a duplicate
id makes structures.set() silently replace the first, which then never
renders, never bills and never wrecks with nothing said anywhere.
· every collateral an authored anchor names is OWNED by exactly one thing in
that yard. RULE 2's runtime twin: RULE 2 proves a key is priced somewhere
in the palette, this proves it is owned in the yard that names it. Zero
owners is the gutter bug reborn; two is the landmine.
Five negative controls witnessed red in the real harness, then green: the frame
un-bracketed, the paint turned galvanised, the frame claiming the glass's key,
the anchors no longer naming the glass (the pre-sprint state), and a second
corroded post in the pool yard. Counts held at 533 throughout, so nothing
vanished while other things were red.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
S16 shipped the glasshouse and priced it at $320. e.test said the rest in its
own words: "nothing in the sim wrecks a glasshouse yet — the value is inert
data". main.js bills collateral off a broken rig corner's baked key, and a
glasshouse rightly offers no anchors, so the most expensive object in the game
could not cost anybody a cent — RULE 2's mirror image, a price with no key that
can reach it.
DESIGN.md line 179 named the missing asset: hail nets rigged OVER glass. You
tie to the frame that straddles it. hail_net_frame_01 / _wrecked: a powder-coat
portal frame clear of the glasshouse on all four sides, head at 2.75 m to clear
the 2.28 ridge, four welded eyes at 2.690 baking collateral 'glasshouse'.
The tell is a POSITION, not a defect — the frame's numbers are good and the
hazard is where it stands. Pinned as geometry off two GLBs (footprint strictly
contains the glass; head clears the ridge) rather than as paint on one. The 20 m
read is metalness: powder-coat at 0.05 renders bright where every trusted
galvanised steel at 0.90 goes near-black with no environment map (S17's measured
lesson, applied on purpose this time).
Rung 0.80, proposal, A rules: it earns the highest rung below the honest post
(engineered frame, four footings, the only structure built to be tied to) and is
de-rated 20% for section, not condition. It usually holds — that is the tier:
the corner failure that costs a shackle on a sail post costs $320 here.
The root deliberately carries NO collateral_key. structFor() takes the first
match, so a frame claiming the glass's key would bill the panes and wreck the
frame, both papers agreeing and both wrong. That omission is gate 5 in one line.
Wreck racks at one end (0.45 in at the head, 0.45 out at the feet) after the
first cut still read as a clean level rectangle in the render. Carries no glass:
the glasshouse swaps independently. Unpriced by ruling.
ANCHOR_TYPE widened with 'hail_net_frame' (contracts.js is A's — revert and tell
me; corroded_post precedent). Manifest unambiguous: 0.80, glasshouse, 4 sources.
Determinism held: runs 2 and 3 are 56/56 byte-identical. NOTE the shipped GLBs
were exported by Blender 5.1.2 and this box has 5.0.1 — the 45-binary churn that
causes is semantically nil (60 nm accessor drift, PNGs losing sRGB/gAMA/cHRM
with identical pixels) and was reverted, not shipped. Documented in the header.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
NIGHTS ∪ POOL grew a third member this sprint, and an emergency is the member with
the most to hide: no forecast card, no quote, and a storm entered at a t nobody
walked up to. Both arms checked per entry — dispatchHonest(def, arriveAt) for the
storm-and-instant, pairingRefusal(storm, site) for the yard, because a read can be
perfectly honest about a storm and still be an invitation to a night nobody can
work, which is worse on a callout the player cannot decline once they are in it.
Read through a NAMESPACE import (board.EMERGENCIES), not a named one, so this file
survives the window where A's spine is on lane/a and not in my tree — a named
import of a not-yet-exported symbol is a hard module error, not a graceful no-op.
A's own reasoning for weather.midStormRead?.(), applied back at them.
Walks a FIXTURE mirroring A's §6 as well as the real table, so the gate is
exercised on known data TODAY rather than reading green off an absent import — the
calm-day vacuity that has now bitten this repo in three separate gates. Verified
against A's actual lane/a tree out of band: their one shipped emergency
(corner_block_emergency, night 5, storm_03_southerly x site_02_corner_block,
arriveAt 30) passes both arms, so the walk binds clean at merge. Three vacuity
guards, one per arm plus the late arrival.
533/0/0 (+1).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A's §8 seam, built to their shape: an ordered {key, text} list the card maps, the
offerBand construction, reachable through weather.midStormRead?.() under a
namespace import.
THE INVERSION IS THE DESIGN. offerBand's sin is OMISSION — the board lied about
night 7 by printing two of the fields it held. A dispatch's sin is INVENTION, and
the consequence is that the read is SHARPER than a forecast, not vaguer: standing
in the yard you know the wind on your back to the km/h, so the present tense is
exact where the offer card was banded. What you do not have is the bureau's
numbers — how long it runs, the peak, whether a southerly lands at t=48.
So the read is ruled by TENSE. Permitted: NOW (exact, unhedged); THE VISIBLE
IMMINENT (a gust front crossing the grass — DESIGN.md line 149, a 1.5 s telegraph
horizon earned by looking); and THE PAST AS WRITTEN ON THE YARD — at t=30 you have
no memory of the storm because you were driving, but hail lying in the grass and
water standing on the flat are a record you did not have to be present for.
Integrals over [0, t] are honest; over (t, ∞) they are not. The future is
forbidden outright.
And the admission is mandatory: on an offer card a missing hail line means the
storm does not hail, on a dispatch it means nobody knows, and silence cannot tell
those apart. The read says so first and last, in constant words — the ignorance
line is unconditional because a line that appears only when there is something to
not-know becomes the very fact it claims not to have.
dispatchHonest(def, t) extends the gate: forecastHonest unchanged (no forecast
card is not a licence for an indescribable storm — it raises the bar, since the
read is the only description there is), plus the three things only an arrival can
get wrong. My own S17 filing was wrong and testing it said so: hail.size 0 was
already refused by validateStorm a layer up. The reachable hole is size ABSENT —
it passes every gate and defaults to the MIDDLE of the vocabulary, so the soaker
minus one field prints "marble stones" for its real 0.45 fine pea.
Pins +5 (527 -> 532). The strongest states the rule rather than policing a
vocabulary: THE READ AT t MAY NOT MOVE WHEN THE STORM'S FUTURE BEYOND t MOVES,
with a vacuity guard proving the mutations really do change the storm. Four
mutations red and restored.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
setPhase('storm', {at}) is the whole engine change: windTime() already returns
phaseT during a storm, tick() already ends at STORM_LEN, so an emergency night
is 60s long inside weather that is already working. No new phase.
EMERGENCIES, scheduled per night, not a POOL entry — a seventh pool entry would
re-roll every night's draw, and the one-variable law needs an author to place a
set-piece. Diffed the whole week against HEAD: exactly one line moved, and what
it replaced was corner_block_southerly — the same yard and the same storm as an
ordinary job. The job type is literally the only variable.
⚖️ Rulings: emergency rate ×2.0 (DESIGN.md line 29, canon, UNMEASURED-by-play);
a corner that ARRIVED broken bills nothing, wrecks nothing, books no warranty
and costs no standing (`theirs` on the rig record — without it the game charges
you for a cowboy's carabiner and books you a free callout to fix his work); the
inherited steel does not come home; the ute carries one free spare, or triage is
a verb with no object.
THE ONE-VARIABLE LAW IS NOW CODE: oneVariableOffences() accuses, offersFor()
throws, three-way vacuity guard. E's glasshouse cannot be the emergency's debut
stage no matter who wires what.
The DISPATCH is defined by its refusals: no schedule, no total, no AMOUNT DUE —
nobody costed this job. It prints the call, C's mid-storm read (feature-detected
through a namespace import), the rig that is already up with the down corners
marked ON THE GROUND, and the rate. Pinned in DOM, refusals included.
Seams live and waiting: B's breakCorner door, C's midStormRead, D's cutAway
event (tallied, carried to the settlement, printed on the invoice).
Selftest 535/0/0 — 528 + 7, the exact sum.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The emergency callout arrives at t≈30, which makes a NON-ZERO START a first-class
case for the storm clock. Measured before writing anything, and the debris module
failed two ways that had nothing to do with the callout:
· the same storm flown twice through one module spawned DIFFERENT crates
(wildnight height 1.582 m then 1.165 m). main.js builds one debris module at
boot and clear()s it per phase change; clear() rewound the leaf accumulators
and not the piece PRNG. Live on main today — night 2 of the seven-night week
never flew night 1's crates, and no test looked.
· an entry at t=45, past the wildnight's t=38 event, gave every LATER crate the
skipped crate's height, spin axis and phase — the stream sat 5 draws behind.
Skipping history corrupted the future, not just the present.
One cause: a crate's jitter came off a shared stream whose POSITION encoded how
much history had happened. Keyed on the event itself now, so a crate is a pure
function of its event — the move weather.core.js's header already argues for.
debris.enterAt(t0, dt) for the one part that is a genuine path integral: the
ambient leaf layer. A t=0 run has 6 leaves crossing the grass at t=30 and a cold
entry has ZERO, staying becalmed ~7 s while the 2.5 s EMA climbs off zero —
DESIGN.md line 149 makes that moving grass the gust front's tell, and gate 1's
whole premise is that the grass is the only briefing a callout gets. It runs the
ladder rather than skipping it, and the ladder ACCUMULATES: i*dt is the more
accurate ladder and therefore the wrong one (1770 of 1800 steps disagree, first
at step six), because main.js, fixedLoop and sail.js all accumulate.
Pins: +5 (522 -> 527). Wind order-independence broadened to every storm and five
scalar observables plus the exact callout ladder, and a BACKWARDS peak scan
cross-checking what the dispatch will quote. All four mutations went red; the
first draft of the stormStats case could not fail (it memoises per def, so it was
comparing an object to itself) and was rewritten rather than shipped.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
John's ruling, 2026-07-25 ("it adds pressure"), wired end to end.
REP.STOOD_UP = -0.5, the exact mirror of REP.CLEAN: a stood-up client costs
you what a flawless night earns. Bounded above by REP.COLLATERAL so a broken
promise cannot outrank a wrecked carport. UNMEASURED per house rule; it is the
lever, not CLEAN.
isBooked(kind, night) — the diary is booked, the phone is not, and an emergency
in the diary's chair is not a booking. The first cut derived it from the night
alone and the pool yard came back booked; the probe caught it in one call.
take() records the broken promise, settle() charges it at dawn — charging inside
take() drops standing between the board and the sheet, and the fee is priced off
standing. That is the quote-vs-settle lie moved one card earlier.
Three surfaces off one ledger: the offer card prints the cost before the choice
in the client's own terms, the job sheet says they have not forgotten, the
invoice carries an OFF THE BOARD block. Two callouts and no booked job reads as
free, in words, with a vacuity guard behind it.
Selftest 528/0/0 — 522 + 6, the exact sum.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two Lane D sessions ran gates 3.2 + 4 in parallel; found via push rejection.
Their site_04_pool_yard + seven-night cold-play (515/0/0) STAND — dropped my
whole duplicate cut (a second, two-corroded-post pool yard + a second cold-play),
did not force, did not rebase over theirs. Verified their tree green (515/0/0)
before adding a line.
Additive-only: a measured receipt for their second-rust-post landmine (a real
two-post yard splits the exposure harnesses, exposureOf $115 vs
collateralExposure $45 — C's gate-1.2 cross going red by construction); and an
independent live repro of C's night-7 board-card omission (card "33 km/h · fine
pea stones" vs sheet "rain heavy · 44 mm/hr · hail likely") flagged as the #1
board fix. Scratch merge judged the wider tree (main + newest b/c) at 517/0/0,
per-lane sum verified, nothing lost.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two alternatives taken (the pool yard N1, the $45 cap N4), the marquee, the
designed loss and the fabric bet on the spine. THE WEEK HELD 7/7 · 6/7 · $401
· star 0.0 · 5 warranty jobs. Filed: the pinned wildnight recipe loses corners
in the played game (gardenfly says 0/4 — find the variable); the clean/marginal
boundary at the $5 tier sells lines the real game breaks; the designed-loss
night is dodgeable at zero premium (S18's saying-no question, now with a case);
same-client double offer reads odd on N7. Final tree 515/0/0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The piece the 0.2/0.3/2 pass explicitly deferred. Pins E's corroded tier
through the card's own pricing surfaces, off E's real resolver (not a
hand-typed 0.55):
- STEEL half (rigging.selftest): factoryExtras('corroded_post') -> hint 0.55
+ collateral key; _effRating on a corroded corner is rating x 0.55, so the
same load a carabiner holds on a sound post is over a carabiner on a
corroded one. The rust costs a tier.
- COLLATERAL half (gardenfly.selftest, real dressed world): a node-less
corroded placement -> collateralFor = 'the corroded post', summed by
collateralExposure -- through the resolver, not the baked GLB value direct
(the carport-to-null shortcut).
Cross-lane seam: the tier lives on lane/e, so both pins skip-with-disclosure
on bare lane/b (SKIPPED, visible in the report) and go live at integration.
Measured GREEN on a scratch merge of lane/a + lane/e (hint 0.55, collateral
). Browser 485/3/0, node sail 47/47 rigging 29/29.
Test-only + THREADS; adopted the landed 0.2/0.3/2 unchanged rather than
overwrite pushed work.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
site_04_pool_yard: E's ring (fourteen honest noes) east, the bed poolside, ONE
corroded post in the venturi channel where the NE corner wants steel. Authored
in the editor (palette shapes, iterative SCORE IT x3, canonical export).
Gauntlet: WINNABLE at $80 — 13 quads, 6 clean, 1 marginal; cheapest hold $40
(h1,t1b,p2,p3, 92.7 FULL, no rust); every 92%-cover line routes through c1 —
clean $65 rated on t1,p1,p2,c1, UNHOLDABLE on the two shapes that pull the eye
harder. audit.html over the shipped file reproduces the card to the digit.
Separation REFUSED with receipts (bare 83.7 FULL — mild-night canon, A's 0.4).
board.js (A's granted edit): pool_yard_southerly POOL entry with the audit
receipt. d.test: +5 pins (chosen-never-scripted, ring/rust facts, judged-XOR,
wreck apron, exposure $160). gardenfly.selftest (B's file, flagged): judged
walk 3 -> 4 in the same commit that ships the yard.
Selftest 515/0/0 (510 + 5, the count moved by exactly what was added).
Mutations: 1 full-suite (finding stripped -> DOUBLE red: B's walk 'UNJUDGED'
+ my XOR pin, 513/2), 10 probed (entry deleted/re-paired/receipt stripped/
scripted-slot, gnome unpriced/rust zeroed/fence priced, apron x3) — every one
red with its own words, controls green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Landed ON TOP of f029274 with not one line of it changed. Two Lane C sessions
ran gate 1 in parallel; I found out by having my push rejected. forecastHonest
answers "can the forecast describe this STORM" and is better than the storm-side
half I had written, so mine is deleted. These are the two things it structurally
cannot reach — it takes a def, not a pairing, and it never touches the card.
weather.js is +180/-0. The only line of theirs I touch anywhere is widening one
c.test import from { NIGHTS } to { NIGHTS, nightAt }.
1. THE OFFER BAND, and the finding that motivates it. A's card prints f.wind
and f.stones, and under that pair NIGHT 7 LIES:
soaker (scripted) gusts to ~55 km/h · fine pea stones
early buster (alt) gusts to ~76 km/h · pea stones
On both printed lines the soaker is the softer job. It is not: 14.9s of hail
against 2.4s, 44 mm/hr against 16.5. The soaker's whole design is that its
wind reads gentle and its hail is the trap, so the board recommended the trap
in the storm's own voice. offerBand(def, lead) returns an ORDERED LIST, so
the forecast decides which facts a night carries and a card cannot drop the
next one added — same construction as A's stormsToPreload(nights, pool).
Verified in the real card on :8826.
Second finding: storm_03 and storm_03b are identical in every number the band
prints except the change time (30s vs 18s), and the board offers exactly that
pair on nights 5 and 7. Without the change line it offers two indistinguish-
able jobs and calls it a choice. Pinned.
2. PAIRING_LAW. A band can be perfectly honest about a storm and still be an
invitation to a night nobody can work. A's three POOL exclusions were prose;
promoted to checked data with the measurement in each message, credited by
owner (the soaker's is mine with the S16 ~31% receipt; wildnight and icenight
are recorded as A's reasons, not re-measured by me). Absent key = unrestricted
deliberately — inventing a refusal for a pairing nobody flew is the same
offence inverted, and that direction is pinned too. pairingRefusals is NOT a
filter: silently dropping an entry is a runtime surprise wearing a fix's
clothes. Walks NIGHTS u POOL carrying the SITE: 12 pairings, 0 refusals, with
a vacuity guard in the same case.
Mutation-checked on THIS tree after the code changed address: hail line dropped
(RED, names the storm and the seconds), soaker restriction deleted (RED x2,
including the vacuity guard), change line dropped (RED, names the two busters).
All restored, 494/0/0.
Filed in THREADS, not landed: the hud/main hunk for A (leadFor precedent), and
a floor for stoneWord — hail.size 0 words itself "fine pea stones" because
stoneWord has no floor. Their STONE_WORD_CEILING fixes the top of that range;
nothing fixes the bottom. It belongs inside forecastHonest, which is theirs.
Selftest 494/0/0 (their 490 + 4).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GATE 0.3 — THE CHARTER, SAID OUT LOUD (D's soaker finding, A consulted on
wording and their every-card rule adopted). The audit always flew shade cloth
and never said so; on the soaker that silence read 'WINNABLE over an all-DEAD
garden — the night is broken'. Now: AUDIT.POROSITY is the one charter knob
(sweep.js + gardenfly.js both read it), scorecard.fabricCharter() names the
fabric and whether tonight's stones pass its weave (same hailBlockFor the sim
charges), and the SCORE IT header prints 'fabric · shade cloth (sweep
charter)' on EVERY card — plus, on leaky-storm nights, A's wording: the
fabric is the bet, and the audit does not place it.
GATE 2 — CLIENT CONSTRAINTS: A's shapes (seam contract, built against as
posted), this lane's teeth.
· rigging.js: validateNightConstraint (checked enum, both ends of the seam),
setConstraints (survives reset like _startBudget; [] is the only clear).
The house ban refuses the pick with the CLIENT'S WORDS as the ticker
reason; the cap refuses at SPEND time on every path (rig / cycle / set /
spares / fabric), exact at the boundary, refunds always free — and commit
is belt-and-braces: a caller who walked around the doors gets a THROW.
The cap covers the whole invoice, spares included — the client queries the
invoice, not the hardware line.
· sweep.js: applyNightConstraints, ONE function both drivers share — bans
shrink the candidate list (a card that recommends a forbidden line is the
card lying), the cap re-prices affordable/clean without touching a load.
· scoreSite carries constraints/budget/constrainedOut; the card prints the
client's terms next to funnel and fabric, and tells 'no geometry' from
'client forbids all of it'.
· spent getter now measures against _startBudget (the re-banked session was
measuring spend against the default bank).
Selftest 485/0/0 in the browser (474 + exactly the 11 added: 1 sail, 4
session, 2 charter, 4 audit-constraints). Wiring line for A filed in THREADS:
session.setConstraints(week.job?.constraints ?? []) at the night boundary.
D's S16 poison poke, filed for this lane: _checkFailure's corner loop is the
heal's only trigger and it skips broken corners, so once all four were
divergence-broken a SECOND poison had no unbroken corner left to read NaN
through — the corpse stayed NaN forever and rendered as nothing. A lost sail
is still cloth in the yard; it must LOOK lost, not vanish.
The sentinel runs ONLY on a fully-broken rig (the corner wire covers every
other case): sum pos+prev — any NaN/±Inf makes the sum non-finite (Inf−Inf is
NaN), finite cloth cannot overflow it. Branch-free O(n) adds, no mutation, so
a finite lost sail is untouched byte-for-byte.
Test replays D's gait: cascade 4/4 → 5 s finite with ZERO heals (the negative
control — the sentinel must never mistake 'lost' for 'sick') → second poison
heals in one substep, finite a full second on. Node suite 47/47.
- forecastHonest(def): "a storm the forecast can't describe honestly doesn't
get offered" as a predicate, not a sentence — validator + measurable stats +
the stone vocabulary ceiling (STONE_WORD_CEILING 2.0: past it, "golf ball"
undersells the ice and the word ambushes where the band can't). The band-
containment recomputes are disclosed as structural regression armour, not
counted as coverage.
- c.test walks NIGHTS ∪ POOL from the shipped data (the union, per A's
stormsToPreload finding — a pool-only storm is covered the day it exists).
Negative controls: a lying windchange, a cricket-ball stone, both refused
by name. Lead-0 card pins: the offer card's gust/sustained figures parsed
back out and matched against stormStats; a lead-0 offer must not hedge.
- The exposure cross (the S14 pin pattern, third outing): my failure-route
envelope (built world, anchor collateral keys through world.collateralFor,
the gnome per scoreRun) vs A's exposureOf — item-level equality on ALL
THREE yards: backyard 115, corner block 205, swing lawn 255. Zero unpriced
keys. Teeth proven in-suite: strip the carport key and the cross reds.
Selftest 490/0/0 (A's 485 + 5), browser-verified; board verified live on
:8826 — both cards print the honest lead-0 lines and the crossed dollars.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Gate 0 rulings (written, with reasoning, in THREADS):
- 0.4 hail-light balance: CANON. B's finding reproduces exactly ($4/$2 garden
spread), but the mild-night rig market buys the STEEL and the collateral, not
the bed — a cheap rig that fails on site_02 swings $184 and two stars against
the same rig holding, and the cheapest HOLDING line is $40, not the $20 floor.
Ruled for B's option (b): the separation block asks the wrong question on
those nights; the new shape is B's and is NOT this sprint. Rain drain-weight
lever declined at its proper price (full gauntlet re-measure, own gate).
- 0.4b gradeFor scraped/solvent >=3 STANDS on the seven-night shape, ruled on
the arithmetic (savable 6 → solvent is 4-6 dead, which is what the copy says).
- 0.3 score-header wording consulted for B (no code from me).
Gate 1 — the board: board.js (pure data, node-testable), week.offers()/take(),
seeded from week+night via contracts' mulberry32 — no Date.now, no Math.random.
An offer carries a whole NIGHT ENTRY and take() installs it, so sheet, quote,
invoice, ledger, warranty, rep and end card all read a chosen job through the
path they already had — seven surfaces, zero changed lines. Scripted spine runs
byte-identically when nothing is taken.
Gate 2 (data half) — constraints as night data, checked enum, premium ruled
(+25% anchor ban / +20% budget cap, both UNMEASURED and flagged cut-first),
stated on the offer, the job sheet and the invoice it was paid under. ONE
calloutFee() now serves quote() and settle(). Enforcement is B's.
Two bugs found off the suite: take() stored raw pool entries (crashed quote()
on a missing pay block) → normaliseNight() split so both doors share it; and
NIGHT 1 HAD NO BOARD — the splash bypassed it — found by looking, not testing.
Pool pairings audited in the browser before shipping; both constraints checked
for soft-lock against real holding lines.
Mutation-checked ×6. One did NOT go red: "every pool storm is preloaded" passed
with the POOL source deleted, because every pool storm is also in NIGHTS — the
same coincidence that hid the calm-day bug. stormsToPreload(nights, pool) split
so it can fail. Selftest 485/0/0 (474 + 11).
Recovers an interrupted session and finishes its verification honestly.
RESTORED (the predecessor was killed mid-mutation-check):
- build_sail_post_corroded still had negative control M1 APPLIED — clean
galvanised steel, DROOP=0 — so both shipped GLBs were the untelled post.
Restored: steel_weathered/rust/rust_deep, DROOP_DEG = 38.
- asset_report.json held 1 of 37 assets and contact_sheet.png was a 196 KB
truncated write. Both were interrupted artifacts, not decisions; a clean
rebuild restores 37 assets and a 5.07 MB 1680x4200 sheet.
DETERMINISM: 37/37 GLBs byte-identical across two consecutive full runs;
report and contact sheet byte-identical too. Zero churn on the 35 pre-existing
GLBs.
ASSERT THAT COULD NOT FAIL, KILLED: the sag pin (honestY - corrodedY > 0.05)
reads 0.060 at ZERO droop, because the eye hangs off a weld line 160 mm down
the post — measured on the M-B build, anchor at (0, 3.920, 0). It measured the
weld offset and called it a sag. Replaced with the droop ANGLE derived from
the exported anchor and pinned to baked extras (padeye_droop_deg / arm_m /
weld_y_threejs / dir_threejs), all stated in three.js coords — the axis trap
closed the swing_set way, so note and mesh can only lie together.
ASSERT WHOSE REASON WAS BACKWARDS, FIXED: the 20 m pin claimed the corroded
shaft read darker. Measured off look.html's canvas at 20 m: honest lum 50,
corroded lum 94 — it renders twice as BRIGHT. Base colour is darker but
metalness drives the pixels (gal 0.90/0.35 goes near-black with no env map;
weathered 0.55/0.60 is diffuse). Test now pins both halves and names the
mechanism the player actually sees.
Three tells split into three tests so one failure cannot mask the others —
pre-split, the M-A mutation went red on rust area and never reached the
lightness or droop asserts at all.
Mutation-checked in the browser, all three witnessed red: M-A clean steel
(1/3 + 2/3 red, 3/3 green, factory GREEN throughout — the trap it cannot see,
confirmed); M-B flat eye (3/3 red, others green); M-C baked note lies while
mesh is honest (3/3 red, proving the pin reads the extra, not a literal).
Selftest 483/0/0 (474 baseline + 9 exactly). Tell verified by looking at
20 m at the game's own camera height, screenshots taken.
editor.js untouched — palette hunk filed verbatim in THREADS for A.
contracts.js ANCHOR_TYPE widening flagged for A.
Lane D flagged: the tier is placeable, gate 3.2 unblocked.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Preserved verbatim from the interrupted session. NOTE: build_sail_post_corroded
still carries the M1 mutation (clean galvanised steel, DROOP=0), so the two GLBs
in this commit are the UNTELLED post, not the shipped asset. Restored in the
next commit after the red-check is witnessed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Ladder: gentle, southerly, earlybuster×site_02, southerly×swing_lawn,
WILDNIGHT×backyard, icenight×backyard (beyondSaving rides the night),
soaker×site_02. Icenight brief reverts to 'less wind than last night'
(true again); new Hendersons brief sells the pyrrhic stake. Law pins
retitled + one new ruling pin (wildnight in, known yard, before the
icenight); a.test re-pinned to the seven-shape; gradeFor clean bar
derived (held >= savable) per the S16 same-commit demand. Selftest
474/0/0; verified live on :8827.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- site_03 re-scored on the post-ruling tree, S15 loop, FUNNEL ON: every number
reproduces the S14 card to the digit (81 quads, 11 clean/16 marginal, cheapest
honest $65 h3,t2,t2b,p1 85.3 FULL, bare 83.7, best clean 90.0, sep +6.3,
best-reading 91.8 MARGINAL). Nothing moved; nothing to fix; B's PIN REFUSED
(measured) card renders the finding on this yard.
- NIGHTS is six: gentle, southerly, earlybuster(s02), SOUTHERLY over the SWING
LAWN (new site, survived storm), icenight (flag intact, no longer final),
SOAKER over the CORNER BLOCK (C's measured pairing). Two new briefs: Ruby's
swing set sells the crossbar trap; the Vasilaros return sells the cloth
default the forecast argues against.
- THE STRUCTURAL CONSEQUENCE, filed loudly: six slots cannot hold five old
storms + a survived-storm debut + the soaker. The WILD NIGHT leaves the
rotation (every other candidate is load-bearing); storm file, tests and the
pinned backyard separation all stand. If the eviction is wrong the fix is a
seven-night week — one entry, a ruling.
- week asserts updated (a.test): six nights, final-night=6 both directions on
the broke rule, three clients with night 6 a RETURN booking.
- four six-night-law pins in d.test: one new site / one new storm / never same
night; survived-storm debut; soaker pairing (C's receipt in the message);
beyond-saving night neither new nor final.
- hud surfaces read NIGHTS.length (splash, morning header, end card) — flagged
for A; hardcoded 'five' would lie on every paper.
- selftest 473/0/0 (469 + 4); mutations M1 soaker→backyard, M2 debut→wildnight,
M3 flag→final each RED with the law's own words, restored, green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
