10 most recent check-ins occurring on or after 2026-08-26 23:31:23.
More ↑
|
2026-08-27
| ||
| 00:03 |
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. closed check-in: 02f6aadcad user: dmestas tags: strata-ui | |
| 00:03 |
RFC 0006: the strata is derived, and the queue counts decisions
AttachStrata reads the chain from target -> branch across landings: base, position, depth, and why a chain cannot be walked — a cycle, or a rejected base. Derived at read time, never stored, so a segment retargeted by zit#144 after its base lands simply stops being one. landing.list carries the reading and counts DECISIONS: a stack of five is one, the base's, because nothing above it can be acted on. landing.get carries the chain for the record's map and reports a rung above the bottom as stacked, which the merge probe must not overwrite: its answer is true and useless there. check-in: 3e3ad17751 user: dmestas tags: strata-ui | |
| 00:02 |
markup: fossil wiki resolves mentions and refs, like markdown does
An artifact with no N card IS fossil wiki — fossil's default, and what anything writing through the zit CLI produces. fossilInline resolved this dialect's own [target] links, but @mentions, [[wiki]] refs and bare hash refs are dialect-independent and were reaching only markdown bodies, so 62 of quarry's own 90 forum posts lost every mention in them. The two passes run after sanitizing, as they do in Render: resolveRefs mints the identity mark and the policy would strip it. It parses HTML and skips a/code/pre, so the anchors fossilInline just built and every block are left alone — both asserted.check-in: b00045e163 user: dmestas tags: trunk | |
|
2026-08-26
| ||
| 23:51 | Landed layer 6: the heading gone, the strata proposal in RFC 0006. check-in: 2a95e40671 user: ai-local tags: trunk | |
| 23:51 | Landed phase 5: every row of the RFC's table, proved the way a person would do it. check-in: 763b776f6f user: ai-local tags: trunk | |
| 23:51 | Landed phase 4: the rule has a page, and the page says what it costs. check-in: 8f527acdb5 user: ai-local tags: trunk | |
| 23:51 | Landed phase 3: the merge is the fact, the reply is the claim, accept asks MayJoin. check-in: 2d30e99800 user: ai-local tags: trunk | |
| 23:51 | Landed phase 2: identity becomes a rule, the child enforces it. check-in: 8c6e2b5b59 user: ai-local tags: trunk | |
| 23:51 | Landed phase 1: the policy table and the decision function. check-in: 4742a00a65 user: ai-local tags: trunk | |
| 23:31 |
Landings list: drop the h1; RFC 0006: how a strata is shown
The tab already says landings and the page's first line is the state chips; the heading said the same word a third time. RFC 0006 gains the rendering proposal it deferred, written after this forge's first real strata listed as five independent open landings. Grounded in what GitHub (native stacks, July 2026), Gerrit (relation chain, submit whole topic) and Graphite do: a position on every member, a map on the record, one action at the landable end. quarry groups in the list because its list is a queue and a queue that shows five rows for one decision counts wrong. closed check-in: 3693d77992 user: dmestas tags: protect-6 | |