# Fossil Draft Metadata Defaults
## Shared defaults for all three drafts
Use these defaults unless the suite owner explicitly changes them:
- **Submission type:** `IETF`
- **Category / intended status:** Proposed Standard (`std`)
- **Public deliverables:** source Kramdown `.md` plus rendered IETF `.txt`
- **Intermediate only:** `.xml` is a build artifact, not a public suite deliverable
- **Reference pool:** draw from `references.md` and keep per-document citations narrow
## Provenance and authorship boundary
- The author block is human-only.
- The artifact document alone carries the mandated transformation/ratification provenance sentence, and it belongs in the abstract opening sentence rather than in the author block.
- Do not add process, audit, or derivation wording to the Delta or Sync front matter.
## Human authorship default
The original pack expected the suite to present human authors representing:
- Fossil contributors,
- libfossil contributors,
- Dan Shearer as editor/reviewer.
If an implementation uses explicit YAML author entries, keep them human-only and keep the provenance sentence out of author metadata.
## Per-document titles and abstract anchors
### Artifact
- **Title:** `The Fossil Distributed Version Control System: Artifact Format`
- **Abstract anchor:** one paragraph describing Fossil global state as a content-addressed set of artifacts and stating that the document specifies artifact naming, card syntax, structural artifact types, and checksum computations.
- **Required opening sentence:**
`This document is a largely automated transformation of existing implementation texts, pending ratification by the Fossil and libfossil contributors identified in the Author list before adoption as a working group document. Once adopted it is maintained through the IETF process.`
### Delta
- **Title:** `The Fossil Delta Format`
- **Abstract anchor:** one paragraph stating that Fossil represents an artifact as a delta against a source artifact and that the document specifies the delta encoding.
### Sync
- **Title:** `The Fossil Distributed Version Control System: Sync Protocol`
- **Abstract anchor:** one paragraph stating that the protocol synchronises content-addressed artifacts between two repositories over HTTP and that the document specifies transport, card vocabulary, authentication, and current-wire-version synchronisation strategy.
## What stays outside this file
The following are intentionally not restated here:
- blank-line and kramdown parser mechanics,
- BCP 14 boilerplate mechanics,
- local install commands,
- refcache/network build behavior.
Those belong in neutral toolchain guidance, not the Fossil project pack.