Artifact 1c1d1619a30b0ee67056767cd73481286e1bce4e3f1277c155750b89393ada05:
- File
internal/web/web.go
-
2026-08-27 00:03:48
— part of check-in
[02f6aadcad]
on branch strata-ui
— Landings: a strata is one row, and a map on the record
The open queue folds a stack under its base: a strata mark, the segment count, the landable end named, and the rungs in a details element with 1/N badges — no script. Settled views stay flat; a settled segment has left its chain.
The record page draws the map: every rung bottom-up, this one marked, the landable one named, a rejected base as a broken rung. Above the bottom the accept control is disabled and says the segment below lands first.
Proved with a real zit: two stacked landings count one decision; the top rung's accept is refused; accepting the base retargets the next onto trunk and it becomes the landable end, still one decision. (user: dmestas, size: 703337) [annotate] [blame] [check-ins using]
- 2026-08-27 00:04:13 — part of check-in [ca52fa73e4] on branch trunk — Landed: a strata that looks like one thing, because it is one thing. (user: ai-local, size: 703337) [annotate] [blame] [check-ins using]
-
2026-08-27 00:03:48
— part of check-in
[02f6aadcad]
on branch strata-ui
— Landings: a strata is one row, and a map on the record