Vuong Hoang
d37b81ab9f
The two dated log sections had never been split, so every one of their 29 entries sat inline and the startup index had grown to 372 lines — which is the cost the two-tier scheme exists to remove, paid on every session that reads the file. 27 entries were over threshold. All 29 now have a detail file under persistent-memory.d/ and a one-line index entry that routes rather than restates. Index: 372 -> 93 lines. No archival. The soft cap fired, but every entry in this repo is dated 2026-09-21 or later, so the under-14-days guard held all of them back — and the split alone took the index well under the target without moving anything out of the active file. The in-flight section is rewritten for the post-release state: nothing is in flight, no gate is outstanding, and the next unit is explicitly recorded as the operator's undecided call rather than as a plan. The session's recommendation (U4, on three grounds) is written down so it does not have to be re-derived, alongside the two alternatives and why they are alternatives. Two dated predictions are carried forward with their dates and their instruments: the U5 adoption re-measure on 2026-09-29, which already reads 3 of 24 announced and 2 with a why from peers told nothing, and the .forever re-count a fortnight AFTER U4 lands, which is U4's own success criterion and is destroyed by running it early.
17 lines
969 B
Markdown
17 lines
969 B
Markdown
# Deterministic order is a cross-cutting v1 invariant
|
|
|
|
_2026-09-21 · booth_
|
|
|
|
**Deterministic order is a cross-cutting v1 invariant** —
|
|
operator directive, mid-implementation. Every ordered collection the Booth
|
|
renders must have a *stated* rule producing the same sequence on every render
|
|
of the same state; the rule can be anything defensible (byte order, time, an
|
|
explicit number, an arbitrary-but-recorded sequence), but no rule at all is
|
|
forbidden. It binds harder here than elsewhere because the Booth's job is
|
|
**comparison** — the operator judges tile 47 against tile 47 and refers to
|
|
artifacts positionally, so an order that moves between renders misfiles a flag
|
|
or a note rather than crashing. Recorded as `ROADMAP.md` § "Cross-cutting
|
|
invariant" (with the per-collection table) and `CLAUDE.md` invariant 6, and
|
|
tested. Still undecided and must be settled before those units ship: **U7's
|
|
section ordering and compare pairing**, and **U6's bench listing**.
|