Stability First
Ratified invariants are immutable. Implementations that pass the conformance suite today will pass it in perpetuity. No retroactive breakage.
Proof-Backed Changes
Every new invariant requires a conformance test vector. Opinion-only changes are rejected regardless of source. The test suite is the source of truth.
Independent Verifiability
ATF-INV-006 is also a governance principle: no change may reduce the protocol's offline verifiability. Receipts must always be verifiable without platform access.
Language Agnosticism
The Python reference implementation is the source of truth for ambiguous cases. All language ports must produce identical output for identical input (FVP-INV-007).
| RFC | Title | Status | References |
|---|---|---|---|
| RFC-ATF-1 | Agent Trust Fabric Delegation Protocol 6 invariants · MAR · PQC · Temporal validity |
PUBLISHED | DOI 10.5281/zenodo.20155016 SSRN 6757339 |
| RFC-ATF-2 | Runtime Governance Continuity Protocol 8 invariants · CES · HALT · RCR chain |
PUBLISHED | SSRN 6763978 |
| RFC-ATF-3 | Evidence Lifecycle, Policy Interoperability & Forensic Verification 26 invariants · GPIL · EAP · OEP · FEA · FVP |
CANDIDATE | Zenodo DOI pending |
- Open a GitHub Issue with title
[RFC] <short title>. Include motivation, invariants proposed, and failure mode addressed. - Community discussion. Objections must include a counter-test-vector. Opinion-only objections are noted but do not block progress.
- Draft period. The Editor opens an RFC document in
/rfcs/. The draft is iterated until feature-complete. - 30-day review. The RFC enters REVIEW status. Substantive changes require a new conformance test vector. The conformance suite is finalized.
- Ratification or closure. The Editor ratifies (invariants become stable) or closes with explanation. Ratification requires at least one passing implementation.
| Profile | Invariants Required | Test Vectors | Badge |
|---|---|---|---|
| ATF-Compliant | ATF-INV-001 through ATF-INV-006 | 15 vectors (8P + 7N) |  |
| ATF-RGC-Compliant | ATF-Compliant + RGC-INV-001 through RGC-INV-008 | + 11 vectors (6P + 5N) |  |
| ATF-FEI-Compliant | ATF-RGC-Compliant + GPIL + EAP + OEP + FEA + FVP invariants | + 8 vectors (4P + 4N) |  |
IMPLEMENTATIONS.md. False claims will be removed. See the full Conformance Program →
Harold Nunes
- RFC lifecycle decisions (ratification, rejection)
- Conformance vector quality and immutability
- IMPLEMENTATIONS.md maintenance
- Security response (acknowledge within 72h)
- Governance model amendments (subject to RFC process)
Report vulnerabilities privately via GitHub Security Advisories. The Editor will acknowledge within 72 hours. Protocol-level vulnerabilities (invariant bypass) are treated as critical and receive a patch-priority RFC. See SECURITY.md for the full policy.