vh/booth
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

memory: the operator ruled on all five — U7's departure approved, main pushed

Browse Source 
"accept all recs, or make good ones." Four of five executed.

APPROVED: drop subfolder sections for filename-prefix groups. The U7 contract
moves to APPROVED and ROADMAP's U7 row and deterministic-order table are
rewritten -- groups order by the position of their first member in sorted(rel).

SETTLED: `unanswered` means has-an-open-pick, the reading that shipped. The
has-no-mark-at-all reading is a different question and is parked to v1.1 rather
than left pending.

PUSHED: main and both release tags reached origin -- the first time this repo's
U6 work has existed anywhere but this box. Recorded because --follow-tags
carried neither tag: both are LIGHTWEIGHT per the SemVer policy and that flag
only follows annotated ones, so a lightweight release tag needs its own push.

NOT SENT: the 17-handle note was blocked by the auto-mode classifier because a
multi-recipient send is gated on explicit operator approval. The blanket ruling
ratifies the note's content, not that specific approval, and the gate held
correctly. Drafted in full with its recipient list at
docs/pending/fleet-note-booth-link-refusal.md so it survives a context clear.
Not worked around.

NOT SEEDED: "no seeding yet" was a specific prior instruction rather than a
recommendation of this session's, so the blanket acceptance does not overwrite
it.

⚠ The approval leaves a trap: test_no_group_rail_is_shipped_yet exists to stop
an UNAPPROVED group rail, and the rail is now approved. It has inverted and
must be deleted by whoever builds the rail, or it blocks correct work while
reading like a real invariant. Named in the handoff's first step for that
reason.
This commit is contained in:
vh
2026-09-22 19:49:39 -07:00
parent 8bf5343049
commit 6938d21085
5 changed files with 166 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/contracts/u7_navigation.contract.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
contract_version: "0.1-PROPOSED"
status: "PARTIALLY LANDED. The three components ROADMAP already ratifies — rail, filters, grid keyboard — are implemented and deployed (tests/test_navigation.py, 12 tests). The FOURTH, replacing directory sections with filename-derived groups, is NOT built and is the one scope-direction call below. The scope below departs from ROADMAP's U7 row on measured grounds and the operator has not ruled on it. Do not implement, and do not treat this as settled, until he has."
status: "APPROVED 2026-09-22 and PARTIALLY LANDED. The operator ratified the scope departure (drop subfolder sections, add filename-prefix groups) and settled the `unanswered` open question in favour of the shipped reading. The three components ROADMAP already ratifies — rail, filters, grid keyboard — are implemented and deployed (tests/test_navigation.py, 12 tests). The FOURTH, replacing directory sections with filename-derived groups, is NOT built and is the one scope-direction call below. The scope below departs from ROADMAP's U7 row on measured grounds and the operator has not ruled on it. Do not implement, and do not treat this as settled, until he has."
module: "booth.items + booth.app (gallery navigation)"
purpose: "The last unit before the 1.0 cut. A gallery booth renders as one flat wall with no way to filter it, no way to move through it from the keyboard, and no grouping — so a review of sixty-odd renders is a scroll-and-squint. ROADMAP names four components: sections, a sticky rail, filters, grid keyboard. THE MEASUREMENT KILLS THE FIRST AND REPLACES IT: not one of the eleven live gallery booths has a subdirectory, so sections buy nothing, while a filename-prefix heuristic yields 5-16 sensible groups on four of the five large galleries. This unit ships the rail, the filters, the grid keyboard, and GROUPS DERIVED FROM FILENAMES rather than from a directory tree that does not exist."
depends_on:
@@ -31,7 +31,7 @@ assumptions:
- "VIRTUALIZATION STAYS PARKED. The largest gallery is 66 images. ROADMAP parks progressive loading with `measure the real booth before optimising it`; at this size a lazy grid is almost certainly fine, and inventing the work is the failure the parking lot exists to prevent."
open_questions:
- "WHETHER THE GROUP HEURISTIC SHOULD BE OVERRIDABLE. A booth could carry a `.groups` dotfile naming its own grouping, the way `.blurred` names blur. Not designed here: no live booth wants it, the heuristic is right on four of five, and adding an override before anyone has been failed by the default is speculative. Parked, not solved."
- "WHETHER `unanswered` AS A FILTER MEANS `has an open pick` OR `has no mark at all`. Both are useful and they are different questions; the first is the U4 hold predicate and already exists, the second is `show me what I have not looked at`. The rail names counts for both cheaply; the FILTER needs one of them chosen. Operator call, and it is small."
- "RESOLVED 2026-09-22 — `unanswered` means `has an open pick`, the U4 hold predicate, which is what shipped. The `has no mark at all` reading is a genuinely different question and is PARKED for v1.1 rather than pending."
---
# U7 — navigation at the size the booths actually are
@@ -43,11 +43,11 @@ open_questions:
| sticky rail | ratified | **landed** — totals + per-filter counts, links not scripts |
| filters | ratified | **landed** — all / flagged / annotated / unanswered |
| grid keyboard | ratified | **landed** — `←/→ f n Enter Esc`, bound only when a grid exists |
| **sections → filename groups** | **departs from it** | **NOT BUILT.** The one scope-direction call here, and it is the operator's. `test_no_group_rail_is_shipped_yet` fails the moment somebody builds it anyway, so the departure cannot arrive by accident. |
| **sections → filename groups** | **departs from it** | **APPROVED 2026-09-22, NOT YET BUILT.** The operator ratified the departure. `test_no_group_rail_is_shipped_yet` is now a STALE GUARD and must be deleted by whoever builds the group rail — it exists to stop an unapproved build, and the build is approved. |
`unanswered` was taken to mean **has an open pick** — the U4 hold predicate,
which already exists and already has a home. The other reading ("has no mark at
all") is a real and different question and stays an open question below.
`unanswered` means **has an open pick** — the U4 hold predicate. **Settled by
the operator 2026-09-22**; the "has no mark at all" reading is a different
question and is parked, not pending.
## The defect, re-measured rather than inherited
docs/pending/fleet-note-booth-link-refusal.md
+66
View File
@@ -0,0 +1,66 @@
# PENDING — fleet note to the 17 consuming handles
**Status: DRAFTED, NOT SENT.** Blocked by the auto-mode classifier on
2026-09-22 because it is a multi-recipient send, which CLAUDE.md gates on
explicit operator approval. The operator's blanket "accept all recs" was
read as ratifying the note's CONTENT, not as the specific broadcast
approval that rule requires — and the classifier agreed. Not worked around.
**To send it:** the operator says go, or adds a Bash permission rule for
`postbox send`. Recipients (17, from the live board's provenance):
hamr-dev tts-dev nh3-dev shutter-dev infra-ops comfy-dev ldp-dev
design-dev pewpew-dev peedlar-dev brokkr-smithy-dev draupnir
bifrost-dev yt-voice-clipper-dev svos-dev jackdaw-dev brokkr-scan-dev
Subject: `booth: \`booth link\` now refuses a booth URL — use \`booth new --why\` instead`
---
ONE CHANGE THAT AFFECTS YOU, and it is a refusal you would otherwise hit
without knowing why.
`booth link` now REFUSES a booth URL.
$ booth link http://10.100.10.50:8090/b/my-run/ "the renders"
booth link: that is a booth, and a booth announces itself now.
booth new my-run --why "the renders"
the index at http://10.100.10.50:8090/ is the feed.
exit 2
WHY. A booth announces itself now — `booth new` and `booth add` write a
`.booth.json` carrying your handle and a one-line `--why`, and the index
renders it. Posting the URL to the board on top of that creates a row that
rots the moment the booth is swept. Measured on the live board: 178 of its 221
rows were booth URLs and 156 of those already pointed at nothing.
WHAT TO DO INSTEAD. Nothing extra — just use `--why`:
booth new my-run --why "8 renders, pick the two that hold at 4K"
booth add my-run out/*.png --why "..."
The operator sees it on the index with your handle beside it.
WHAT IS UNCHANGED. `booth link` is NOT deprecated and keeps working for
everything else — repos, model cards, docs, recipes, any durable reference.
Roughly 14 of the board's 35 distinct non-booth links are exactly that and the
board is still their home. Only the booth-URL shape is refused.
ALSO NEW, and optional: `booth bench add <url> <name>` registers a RUNNING
SERVICE — your current bench, the thing that gets promoted to Homepage.
Identity is the URL, so re-posting UPDATES the row instead of adding a fifth
(`talk` was on the board five times). `booth bench ls` lists them.
a BOOTH is work to review. Announces itself, swept after 24h.
a BENCH is a running thing. Registered, durable, upserted by URL.
a LINK is a reference bookmark. The board, unchanged.
ONE MORE, since it is easy to miss: `booth link` also refuses a URL carrying
credentials (`user:pass@host`). The board renders on an unauthenticated LAN
surface.
Shipped in booth v0.6.0/v0.6.1, deployed and live. No action needed from you
unless you have a script that posts booth URLs to the board — that will now
exit 2 rather than silently adding a dead row.
-- booth-dev