Self-attested; pre-build. Registry IDs: JFA/jfa-conformance-suite.py.
Posture: COER is a JFA instance whose economy-education shape bends — public-benefit records and alerting rather than a credit marketplace. The shape may bend; the floors do not: sovereign substrate, the witnessed record, and the covenant bind uniformly, inherited as COER builds, and every binding not yet built is a named interim on a committed path, never an exemption (see OPEN-QUESTIONS #1 for the sequencing):
| ID / discipline | Status |
|---|---|
| GOV-9 living open-questions document | Met — OPEN-QUESTIONS.md ships with this seed |
| GOV-10 copyleft commons | Met — AGPL-3.0 adopted 2026-07-22; LICENSE at root, declared in the spec header (OQ-3 resolved) |
| SUB-1 no hosting chokepoint | Tension, named — multi-tenant SaaS end-state vs. the portability thesis (OQ-2) |
| Record discipline (REC-1 spirit) | Met by design — immutable AuditEvent for every state change; evidence hashing and chain of custody |
| Flag, never finding | Met by design — "AI ranks and flags; humans decide"; unverified content never auto-rebroadcast |
| PII discipline (REC-3 spirit) | Met by design — no PII in logs; no persistent individual tracking; consent, retention tags, purge |
| Legibility | Partial — standards-as-contracts and conformance tests for NERIS/NEMSIS/CAP payloads are in the conventions; decision receipts not yet specified |
Honesty line: every safety-critical claim here is spec text, not tested behavior; nothing is witnessed or independently verified. The spec's own guardrail — no autonomous agent merges in §5/§10 paths — stands.