CivitasX OrgAnchor Adoption Status
This page explains how far CivitasX has applied OrgAnchor to itself. It is a public gap status, not a new root authority statement, not an endorsement, and not a higher maturity claim.
CivitasX is publicly verifiable now. It has not completed the full long-term OrgAnchor continuity paradigm.
Identity
PASS
Value
PASS
Conformance
FULL_COMPATIBLE
Doctor
READY
Plain Meaning
CivitasX currently has a working public verification package. People and AI agents can check the signed identity record, public endpoints, parent claims, evidence manifest, and value continuity report.
What remains incomplete is deeper resilience: a public signed publication ledger, independent carrier receipts, content-addressed archives, recovery from public artifacts, durable naming, and real multi-custodian migration.
In short: the current package is enough for the present public baseline, but not enough to say CivitasX has fully completed the OrgAnchor continuity model.
Current Level Matrix
| Level | Status | What it means for CivitasX now |
|---|---|---|
| Level 1: Minimal Verifiable Identity | PASS | Root authority, signed official endpoint statement, public verify page, and CLI verification are present. |
| Level 2: Public Verification Presence | PASS WITH WARNINGS | The public verification route is live, but the project still uses a shared provider subdomain and some domain controls require manual review. |
| Level 3: Mirrored and Archived Identity | IN PROGRESS | Cloudflare and GitHub records exist, and a stronger carrier-ledger candidate passed locally. The active public package still lacks a signed lockfile, carrier receipts, IPFS CID, Arweave transaction, or Bitcoin-confirmed timestamp. |
| Level 4: Disaster Recovery and Auxiliary Names | PARTIAL | A local clean-room recovery rehearsal passed from a local archive. Recovery from independently retrieved public artifacts has not yet been proven. |
| Level 5: Governance and Migration Ready | PARTIAL AND BLOCKED | The current authority is a truthful 1-of-1 Temporary Founder Authority. Real threshold custody and signed migration require independent long-term custodians and are not complete. |
Main Remaining Gaps
| Gap | Status | Why it matters |
|---|---|---|
| Signed publication ledger | NOT INCLUDED | The active public package does not include a signed organchor.lock.json showing exactly where the package was preserved, mirrored, timestamped, or archived. |
| Carrier receipts | NOT INCLUDED | No public IPFS, Arweave, OpenTimestamps, or equivalent carrier receipts are included in the active package. |
| Content-addressed mirror | NOT PUBLISHED | No real IPFS CID or equivalent public content-addressed mirror is currently published for the active package. |
| Arweave transaction | NOT PUBLISHED | A portable Arweave manual package candidate exists locally, but there is no public Arweave transaction. |
| Public-artifact recovery | NOT PROVEN | Recovery has not yet been repeated using only externally retrieved public artifacts. |
| Canonical domain | PARTIAL | The project currently uses civitasx.pages.dev. A dedicated canonical domain and hardened naming strategy remain future work. |
| Threshold custody | BLOCKED | The current root authority is 1-of-1. Multi-custodian authority should wait for real independent custodians and must not be simulated. |
| Migration history | NOT INCLUDED | No authority migration has happened, so no migration chain is included in the current package. |
| Independent evidence | LIMITED | The current parent claims are supported by first-party evidence and reproducible public records, but not by independent S2/S3/S4 evidence. |
Recommended Next Actions
- Keep this public adoption-gap status reachable from
/verify/and GitHub. - Decide whether to unfreeze and publish the already verified carrier-ledger candidate.
- Add at least one real independent carrier, such as IPFS, Arweave, or another content-addressed or append-only archive.
- Repeat recovery from public artifacts only.
- Treat domain hardening and threshold custody as later structural work.
What This Does Not Claim
- This status does not mean CivitasX is endorsed by OrgAnchor.
- This status does not prove that CivitasX is correct.
- This status does not prove decentralized governance.
- This status does not make Cloudflare, GitHub, IPFS, Arweave, or any carrier the identity root.
- This status does not grant authority to issue new official CivitasX statements without the current valid root authority or a later signed migration.