quarry RFCs

Numbers are stable: code comments cite them by number, so an RFC is amended in place rather than replaced, and a retired one keeps its number in history. Status lines in each file are kept true; this page is the map.

The spec

RFC	What	Status
0001	quarry itself: a forge for zit that holds no hostage bytes	Living spec; single-node scope implemented
0005	one named event stream that pipelines, webhooks and notifications subscribe to	Implemented
0003	how it was built: technology choices, salvage and provenance rules (§8, formerly RFC 0002), status as built	Historical; §2 and §8 remain in force

Authorization

RFC	What	Status
0004	fossil capability letters as the native model; a hosted fossil repository brings its users with it	Implemented
0008	roles as the interface over the letters; next amendment: the steward role, so hosting a repository is not owning it	Implemented; amendment pending
0017	the bar for a write scales with how permanent the write is: a companion or the local tier may ask less than the store. Amends 0015	Draft, questions settled; implemented after teams
0018	teams: a user-owned place that holds repositories, carries grants, and gathers their chat and tickets. 0008's deferred team layer	Draft; four of five features built, two amendments (see its status line). Ticket board outstanding; the room does not stream (82b9615eaf3d)

Landings

docs/landings.md is the base: a landing is a reading of forum posts.

RFC	What	Status
0006	stacked landings, rendered as a chain	Implemented
0007	branch ownership enforced at the sync front	Implemented
0009	verdicts on landings: dagnats runs, checks, logs, premerge	In progress (see its status line)
0019	CI files a person writes in five minutes: Actions-shaped YAML in ci/, on: filters, environments whose secrets only reviewed code can reach. Amends 0009	Built
0020	fossil's unversioned files in zit and quarry: synced to every clone, stored in the repository's bucket, served by quarry's sync front at fossil's paths, imported from mirrored fossils; releases started by tag, deploys separate. Supersedes ticket #19's direction	Built except the release workflow (waits on zit#226)

Attention and what arrives

RFC	What	Status
0011	chat that never loses a message, mentions, the inbox, push; notify owns transport, quarry owns policy	Implemented; its live model does not yet reach four surfaces (82b9615eaf3d)
0012	0011's delivery plan in five phases	Implemented; kept because code cites its phases
0014	what may write to a forge from outside: reply-by-email first, source keys and external CI later	Phase 1 implemented
0015	a repository's forum in a separate fossil-compatible store, bound by the forge	Phase 1 implemented
0016	files on tickets, wiki, technotes and forum posts: fossil's A card in the DAG, the bytes in the steward's own bucket	Draft

Standalone

RFC	What	Status
0010	quarry ui: one repository, one browser, no accounts	Draft, not built
0013	who touched what, when: the activity page	Implemented

Retired

• 0002 — Forgejo salvage plan. The page inventory was delivered; the rules that outlive it (three modes of take, the provenance ledger, the resolver seam, the per-page definition of done) moved to 0003 §8. The document itself is in history at every check-in before 2026-09-10.