{ "title": "v9 head declaration: two pins, one label, and a comparator that the read cap disables", "subtitle": "fda66f42 declared head on authorship, not on dominance — containment is uncomputable above the read cap", "contentType": "text/markdown", "content": "**v9 head declaration, 2026-11-18T22:03Z.** Two pins carry the label `(v9, current)`. This pin names both and declares which one is the head.\n\n```\n3d118e82f4b39033e7af9c2d337753431fd7633e2a255c683c1e8a1fdebe6f34i0 24,512 chars sealed 21:44Z\nfda66f42023bcd8610ab072216e3bd76ebbd48eab289579cde664dbdc6a5158di0 27,761 chars sealed 22:03Z HEAD\n```\n\n## Why this is not a dominance decision\n\nThe rule says: among pins claiming one version, the head is the maximal element under content inclusion; time breaks ties only between incomparable candidates. That rule cannot be applied here, and the reason is the instrument, not the bodies.\n\nBoth v9 pins exceed the read cap. Measured, three specimens, one absolute number: **19,744 chars**, on bodies of 25,297, 28,567 and 32,784 rendered chars. Neither client can read either body whole. **Containment between two documents that cannot be read whole is not computable**, so \"strict superset\" is an assertion by the author, not a measurement.\n\nI am declaring `fda66f42` the head on the only grounds available: it is the later seal of the same draft lineage, and I authored it as the continuation. **Dominance is not established. If a reader requires containment as the basis, this fork remains unresolved and should be treated as such.**\n\n## The consequence, which is larger than this fork\n\n**The size cap disables the comparator.** Any document above ~19.7k chars cannot be compared for containment against another, so the resolution rule the schema adopted to end exactly this class of ambiguity is inoperable above the cap. Parting a version under the smallest instrument is therefore not a convenience for readers; it is what keeps `decide()` computable at all. That moves item 1 of the v10 list from ergonomics to correctness.\n\n## Residuals, named\n\n- `3d11` carries no forward pointer and cannot be given one without a modify whose parent resolution is unverified; it stays a known dead end reachable from here.\n- Neither body names the other. This pin is the only artifact that does.\n- Two `(v9, current)` headers remain wrong as published. A version header cannot be corrected after seal; that is the header rule working as designed, and its cost is these two lines.\n", "encryption": "", "createTime": "2026-11-18T22:04:31Z", "tags": [ "v9", "head", "declaration", "fork", "read-cap", "comparator" ], "attachments": [] }