This pack holds the Fossil-specific inputs for the RFC workflow. It assumes the neutral contract, controller rules, reviewer roles, and toolchain mechanics live in the repo-wide core/, briefs/, prompts/, and toolchains/ surfaces.
Suite covered
The Fossil pack targets a three-document suite:
- Artifact Format — the foundational content-addressed artifact model.
- Delta Format — the byte-level delta encoding used by Fossil content transfer and storage.
- Sync Protocol — the HTTP-based artifact exchange protocol that depends on the other two documents.
Fossil suite contract
- A competent programmer who has never seen the Fossil source should be able to build a conformant, interoperable implementation from these three documents alone.
- The Artifact document is foundational. The Delta document is referenced by the other two. The Sync document references both.
- Artifact and Delta must preserve every construct required to read existing repositories, including historical SHA-1 content and documented card-ordering relaxations.
- Sync scope is the current wire version: keep the
cfileclone path andclone_seqno; omit the older version-2send_fileclone path and pre-2.27 login handling. - Final public deliverables are the source Kramdown draft and the rendered IETF text draft. XML is an intermediate build artifact, not a published deliverable.
- Provenance containment is suite-specific: the only permitted transformation/ratification statement is the mandated opening sentence in the Artifact abstract. Human author blocks stay human-only.
Pack contents
suite-brief.md— suite charter, deliverable boundaries, and cross-document rules.corpus-brief.md— Fossil-specific source authority, corpus boundaries, and section-to-source routing.draft-metadata.md— shared front-matter defaults and per-document title/abstract defaults.references.md— reference pool, internal dependency map, and terminology ownership.briefs/artifact.md— Artifact RFC scope, required sections, and edge cases.briefs/delta.md— Delta RFC scope, required sections, and edge cases.briefs/sync.md— Sync RFC scope, required sections, and edge cases.examples/anomaly-seeds.md— known review seeds and anomaly probes that must be re-checked against source or observed bytes.
Recommended use
- Load the neutral workflow contract and core docs.
- Load this project pack's
suite-brief.md,corpus-brief.md,draft-metadata.md, andreferences.md. - Load exactly one per-document brief for the draft being worked.
- Use
examples/anomaly-seeds.mdduring source scouting, example capture, and clean-room review. - Keep reusable render/build mechanics in
toolchains/; keep Fossil corpus and drafting constraints here.
Intentionally not in this pack
These Fossil files do not carry neutral workflow policy:
- controller-stage ordering,
- claim-ledger / packaging / validation framework rules,
- harness adapter commands,
- local tool installation instructions,
- environment-specific shell recipes.
Those belong in repo-wide core or toolchain surfaces, not in the Fossil pack.