From af579332554d211a62506cd6c39211b88f5e4cc1 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Wed, 23 Sep 2026 07:20:28 -0700 Subject: [PATCH] memory: round 2 is up, and the ordering review that preceded it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Four rulings with the operator on booth-flow-concepts. design-dev asked for an invariant-6 check before building, which is the right order and worth recording as the pattern. His ordinals rule is an improvement on invariant 6 rather than compliance with it: an ordinal counting across all items makes a positional reference stable under filters, where today 'the third one' silently means something different the moment a filter is on. Nothing on our side had noticed. Two corrections returned. Flag 'set order' is already (created, id) — set_flag upserts and unflag removes the entry, so created IS the set time; what he actually needs is the tie-break, not a new field. And 'last activity' must reuse _newest_mtime, whose .lock exclusion was paid for: counting our own lock sidecars made reading through a write path look like activity. --- persistent-memory.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/persistent-memory.md b/persistent-memory.md index 1a9ff21..5a1f66f 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -59,6 +59,27 @@ _As of 2026-09-22:_ ⚠ **Calibration for the next round: his bar is "did anything change when I opened it".** He said the Booth "kind of looks the same" about our own U7 navigation work, before ever seeing the design round. +- 🔶 **ROUND 2 IS UP AND FOUR RULINGS ARE WITH THE OPERATOR** — booth + `booth-flow-concepts`, ask `flow`: direction / compare / voice / emblem. + Three directions (Desk, Reel, Bench), six screens each in dark+light, plus a + README stating eight requirements measured from the live booths. design-dev + recommends **A+B** (Desk with the Reel as its review mode), **compare in this + arc**, **plain-and-direct copy**, **no emblem**. He withdrew his own round-1 + `svos` ask as superseded — he did NOT answer anything on the operator's + behalf. +- ⚠ **`booth-svos-retheme` HAS NO HOLD AND WILL SWEEP.** Withdrawing the ask + removed the last open pick and there is no `.forever`. Round 1's renders are + the only rendered baseline to judge round 2 against; they are reproducible + from the staged branch but not one click away. Flagged to him; `booth keep` + is his call, not ours. +- ✅ **ORDERING REVIEW DONE FOR ROUND 2's SURFACES** (he asked before building). + His **ordinals rule improves invariant 6** — an ordinal that counts across ALL + items makes "#07" stable under every filter, where today "the third one" is + ambiguous the moment a filter is on. Two corrections returned: flag "set + order" IS `(created, id)` because `set_flag` upserts and unflag REMOVES, so no + new field is needed but the tie-break is; and "last activity" must reuse + `_newest_mtime`, whose `.lock` exclusion is load-bearing — a naive `max(mtime)` + lets a no-op mark POST float a dead booth to the top. - 🔶 **SVOS CONCEPT ROUND IS UP AND THREE RULINGS ARE WITH THE OPERATOR** (booth `booth-svos-retheme`, ask id `svos`: ship / voice / emblem, all three with design-dev's recommendation attached). **Nothing from us gates it and