| Comment: | RFC 0005: record what implementing the derived events taught |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
17317e830fc4ac4e67bf806f7f02e003 |
| User & Date: | dmestas on 2026-08-24 16:32:55.188 |
| Other Links: | manifest | tags |
|
2026-08-24
| ||
| 16:57 |
Close the push gap: derived events all come from the fold
The index holds the state an op would have read, so a pushed artifact gets the same event a forge op would have raised. Ticket transitions and landing verdicts compare folded state before and after; forum, wiki and technote need only the artifact or one lookup. Op sites stop raising derived events, so 2.1's split is now enforced rather than documented. check-in: 06942dcc5d user: dmestas tags: trunk | |
| 16:37 |
RFC 0006: strata — stacked landings, rendered as a chain
The forge half of zit#144. A stack is a chain of dependent landings that land bottom-up; quarry renders the chain, refuses accept above the bottom, and flags a segment whose base was rejected. No new index and no new artifact: the edge is already implied by a landing's target, so a stack is a reading of landings the way a landing is a reading of forum posts. closed check-in: 041ca46258 user: dmestas tags: strata-rfc | |
| 16:32 | RFC 0005: record what implementing the derived events taught check-in: 17317e830f user: dmestas tags: trunk | |
| 16:32 |
Raise the derived events from the fold
checkin.created, branch.created and tag.* come off the artifact; branch.moved comes from the computed branch after RecomputeBranches, because only a branch's first check-in carries a sym- tag. Raising is not idempotent while folding is, so the fold asks the index which hashes are new before writing them. A rebuild raises nothing. check-in: a1b816cd96 user: dmestas tags: trunk | |