Use this ledger to track every claim before it enters public RFC prose. A claim may describe behavior, a definition, an example-backed invariant, or an explicit workflow design decision. Do not treat prior drafts or memory as evidence.
Status legend
Status
Meaning
May appear in public RFC text?
candidate
Captured but not yet grounded.
No
accepted
Grounded and reviewed for use.
Yes
blocked
Needs escalation, more source reading, or conflict resolution.
No
rejected
Disproven, stale, duplicate, or out of scope.
No
superseded
Replaced by a newer claim row.
No
Claim ledger
Claim ID
Artifact
Section
Class
Statement
Evidence Refs
Capability Refs
Status
Reviewer
Notes
CLM-0001
<draft-or-packet>
<section>
source-grounded
<one claim>
SRC-0001
CAP-0001
candidate
<owner>
<notes>
Claim classes
source-grounded — directly supported by source or observed bytes.
graph-supported — located through graph analysis and then confirmed against source.
inferred — synthesized from multiple grounded facts; requires reviewer approval.
design-decision — chosen by the workflow; not presented as discovered implementation fact.
open-question — unresolved; block public normative use.
Evidence index
Evidence ID
Claim ID
Relation
Source ID / Path
Range / Locator
Notes
SRC-0001
CLM-0001
supports
<path-or-source-id>
<line-range-or-node>
<brief note>
Promotion checks
Check
Required Result
Actual Result
Notes
Every public claim maps to an accepted row.
Yes
<pass/fail>
<notes>
Every normative claim has evidence or an explicit design-decision reference.
Yes
<pass/fail>
<notes>
blocked, rejected, and superseded claims are absent from public prose.