Artifact 6b364a0b562059a51ea89d912f6fb56cc72e9377520f45be7da70e1799e0e2ed:
- File
conformance/rfcs/README.md
— part of check-in
[245a0ed306]
at
2026-10-20 02:08:49
on branch feat/submanifest-reader
— conformance: re-pin the three drafts to their -00 names
zit check-in 68a3f76cb7 renames the artifact-format, repo-state and sync-protocol drafts from -01 to -00 in their headers, cross-references and reference entries, and retitles each Changes appendix "Changes in This Revision". No normative text changed and no section number moved.
The pinned copies take zit's file names, the requirement tables pin the new hashes, and the comments, tests and docs that cited the -01 drafts cite the -00 ones. The refresh script copies every draft under its own name. The sparse-cone copy is re-pinned to d497c2432f, whose text is unchanged. Coverage counts are identical before and after. (user: [email protected], size: 3548) [annotate] [blame] [check-ins using] [more...]
Pinned drafts
The conformance suite reads these documents, never edits them. Each is a
byte-for-byte copy of a file under docs/rfcs/ in the zit repository, taken
from the check-in below. The requirements tables in ../requirements/ pin
each copy by its SHA-256, so a refreshed copy fails the coverage test until
its table has been re-read against it.
The draft text is the authority. Since zit check-in 62a7d1bb3f
(2026-10-20) every erratum is applied in its draft and zit keeps no
erratum files: each draft records its corrections in its own Changes
appendix ("Changes in This Revision").
Since zit check-in 68a3f76cb7 (2026-10-20) the artifact-format,
repo-state and sync-protocol drafts name themselves -00 throughout, in
their headers, their cross-references and their reference entries, and the
copies here carry zit's file names. Against the 62a7d1bb3f text, which
these copies replace, nothing but those names and the wording of the
Changes appendix's heading and introduction differs: no normative text
changed and no section number moved.
| File | zit check-in | zit artifact | SHA-256 |
|---|---|---|---|
draft-fossil-artifact-format-00.txt |
68a3f76cb7 |
aa13f2e42c |
0887d83d3c57c8b1… |
draft-fossil-repo-state-00.txt |
68a3f76cb7 |
140fdf2d3b |
137f0a573498bf27… |
draft-fossil-sync-protocol-00.txt |
68a3f76cb7 |
62e9495f35 |
2195d9a18fe6bfaa… |
draft-fossil-delta-format-00.txt |
62a7d1bb3f |
d8025d6d75 |
6a28ee7e2e146f80… |
draft-fossil-submanifests-00.txt |
62a7d1bb3f |
5379bc614e |
9326a7f95bc33875… |
draft-fossil-sparse-cone-00.txt |
d497c2432f (branch horizon-rfc) |
05f8b59810 |
2494753225ec3b88… |
draft-fossil-horizon-00.txt |
86d4b67372 (branch horizon-rfc) |
56bf5c0553 |
e1e92af6fa1c2acf… |
The delta-format and sub-manifest files are byte-identical at 68a3f76cb7
and 62a7d1bb3f. The delta-format draft is unchanged since 3f86ff4261
(2026-10-17).
The sub-manifest draft (draft-fossil-submanifests-00) is a single
revision. Its copy is the revision dated 19 October 2026, whose Appendix C lists the
corrections it applies to the 27 July 2026 text. Its Appendix A vectors are
byte vectors: ../testdata/submanifest/ holds zit's copies of them, as
authored for zit, taken at check-in 3f86ff4261 and unchanged at
62a7d1bb3f (src/rfc_vectors/), each with two leading # lines that
keep it from reading as a live artifact on disk; the suite drops those
lines.
The sparse-cone and horizon drafts follow zit's horizon-rfc branch, where
the horizon draft lives; that branch merges trunk. The sparse-cone copy is
the 19 October 2026 revision at d497c2432f, the branch's merge of
68a3f76cb7; the text is byte-identical to the one at 0acb5e185c, the
merge of 62a7d1bb3f it replaces. Trunk's copy is the same text less the two corrections the
horizon work added (§3.1 members of other kinds, §6.2 delta bases outside
the keep set), which the branch's Appendix B lists; the copy here
keeps them because the cone serialization and the horizon table depend on
them. The horizon copy stays at 86d4b67372 (2026-10-18); the branch has
since added §6.2.6 (the horizon cursor) and the classification-memoization
SHOULDs of §6.2, which are not yet read into the horizon table. The same
branch adds the pragma names these two drafts define (cone, cone-not,
and the horizon family) to the sync draft's §9 list of extension pragmas;
the sync draft here follows trunk, so that addition is pending.