THE MONEY. B ruled on the rig that a cut is a decision and emitted no `break`
— but _releaseCorner sets c.broken for a cut exactly as for an overload, and
every ledger surface reads broken. So taking the signature decision billed you
for it five ways: the hardware, the $180 carport you cut the sail TO SAVE
(billed AND wrecked), the gnome's two-corner rule, the clean bonus it voided,
and a free warranty callout tomorrow plus half a star. The invoice would have
printed "You spent the sail to keep the steel" directly above a $180 charge for
the thing you kept. Nobody wrote a wrong line; the join is a flag no verb set
until now. A cut now bills nothing, wrecks nothing, warranties nothing and
costs no standing — and the refund counts it, because "save the anchors" is a
ledger line and not a slogan. `lost` still counts it: the sail IS on the lawn.
THE FOUR SEAMS, all found by playing night 5 and reading the cards, all data or
a name in A's files, all pre-authorised in THREADS, none of them visible to 574
green asserts:
· B's authored cowboy rig had not landed, so the carport corner ARRIVED DOWN
and the knife had no object.
· pay.garden = 0 had not landed; the first emergency invoice paid $38 for a
bed nobody had a prep phase to protect.
· rig.breakCorner?.() — the door is called failCorner. An optional call to a
renamed method is a silent no-op that reads exactly like a call.
· attach({at, wind}) was never passed: clockSkew read 30.02 on the one night
that starts mid-storm, and the knife's own invoice line said "9s in" on a
night you arrive at 30.
And the paper half of John's ruling: at ★0.0 the clamp eats the stand-up
charge, so the card promised a price the game would not take and the invoice
carried "−½★ standing" four rows above "★ 0.0 → ★ 0.0". The documents now print
what will actually be charged. Whether the ruling should have teeth at the
floor is John's, and it is filed with the measurement.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
db1977f55d