Skip to content
zit Changes To Home
Login

Changes To Home

Next Previous

Changes to "Home" between 2026-09-11 19:40:25 and 2026-09-11 20:46:09

︙
36
37
38
39
40
41
42













43
44
45
46

47
48
49
50
51





52
53
54
55
56
57
58

36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

59





60
61
62
63
64
65
66
67
68
69
70
71








+
+
+
+
+
+
+
+
+
+
+
+
+



-
+
-
-
-
-
-
+
+
+
+
+








  repository that turns them on is no longer readable by stock Fossil, and
  sync refuses to hand such artifacts to a peer that would misread them.
* **Sparse cones** — partial worktrees (`open --cone`, `cone`).
* **Indexer feeds** — `frames` and `crosslink` stream raw artifacts and
  derived per-check-in records from a cursor, for a forge or search index.
* **Store care** — `verify`, `pack`, `purge`, `shun`, and a local rebuild
  `checkpoint` that keeps cache-cold opens fast on large histories.
* **Sync at Fossil's scale** — clusters are indexed, announced bounded,
  and minted at Fossil's own thresholds, so a no-op pull of a
  million-artifact repository sends kilobytes, not the whole inventory;
  clone streams to disk as it arrives.
* **A write plane for forges** — the machine verbs `wiki`, `ticket`,
  `forum`, `technote`, and `attach` author Fossil's collaboration
  artifacts, `landing` proposes and lands a branch as an ordinary forum
  thread, and `attach list` reads attachments back. Each is one line of
  stdout, exact exit codes, and works against a bare store with `-R` —
  the seam [quarry](https://github.com/danmestas/quarry) writes through.
* **Signed check-ins** — `commit --sign` clearsigns the manifest through
  Fossil's own `pgp-command` contract, and the signature survives pack,
  verify, and sync byte-exact.

## What it leaves to Fossil

By decision, not omission. The collaboration artifacts — wiki, tickets,
By decision, not omission. zit authors and syncs the collaboration
forum, technotes, attachments — are stored and synced by hash but never
interpreted, and the web UI goes with them (`zit ui` hands off to a forge that
serves the repository). There is no unversioned-file
store; a peer's unversioned files are declined visibly. zit never signs a
manifest and never creates a SHA-1 repository, though it reads both.
artifacts but renders none of them: the web UI belongs to a forge
(`zit ui` hands off to one that serves the repository), and wiki, tickets,
forum threads, and technotes are read there rather than here. There is no
unversioned-file store; a peer's unversioned files are declined visibly.
zit never creates a SHA-1 repository, though it reads one.

## The specifications

The drafts under [docs/rfcs](dir?ci=trunk&name=docs/rfcs) are the sole
authority. Expected values in tests come from the spec text and its worked
examples, never from observing another implementation; where the code
follows Fossil's implemented behaviour against the published text, the
︙
82
83
84
85
86
87
88

89
90

95
96
97
98
99
100
101
102
103
104








+




## Finding your way

* [Timeline](timeline) — current activity and history
* [Source tree](dir?ci=trunk) — browse the code at trunk
* [README](doc/trunk/README.md) — design notes, scope, and build steps
* [Release notes](dir?ci=trunk&name=docs&re=RELEASE-NOTES) — every release, oldest to newest
* [Technotes](technote) — engineering notes on how and why things changed
* [docs/rfcs](dir?ci=trunk&name=docs/rfcs) — the six frozen drafts
* [GitHub mirror](https://github.com/danmestas/zit) — issues and CI