| Comment: | docs(changelog): the origin classification memo |
|---|---|
| Timelines: | family | ancestors | trunk | feat/horizon-cones |
| Files: | files | file ages | folders |
| SHA3-256: |
abecc56d219899a07706797ace0bef1b |
| User & Date: | [email protected] on 2026-10-22 22:54:56.000 |
| Other Links: | branch diff | manifest | tags |
|
2026-10-22
| ||
| 22:54 | docs(changelog): the origin classification memo leaf check-in: abecc56d21 user: [email protected] tags: feat/horizon-cones, trunk | |
| 22:54 |
fix(sync): label the parents of every held manifest at a structural horizon
A structural clone holds the manifests of the held set and everything they reach through B and S cards (draft-fossil-horizon-00 §5.1), so a delta manifest's baseline below C is held. Its parents were labelled by nobody: boundaryOf took the parents of K's check-ins only. The clone then classified such a parent as transit and requested it, and the origin, which withholds manifests below C, never sent it; the clone stalled with one phantom outstanding. zit's origin has the same gap (sparse.zig 758-783), and zit's author agreed the draft will define a boundary hash as an unheld parent of any manifest the clone holds. boundaryOf now labels the parents of K and of every check-in the reach holds. The regression is the HZ-3.1-4 case for a delta manifest in K whose baseline lies below C: the clone completes, the baseline is held but not a leaf, and K's check-ins derive the dense repository's tags. check-in: f0354673e2 user: [email protected] tags: feat/horizon-cones, trunk | |