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. The 2026-07-15 parent-path package adds the public research route, signed claims and evidence for the working map, a new IPFS publication, a new Arweave Turbo publication, and a new OpenTimestamps proof. It strengthens continuity without claiming that CivitasX has 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.

The parent-path package is published to IPFS and Arweave Turbo. Its key Arweave files have been hash-verified through both Turbo and arweave.net. The new OpenTimestamps proof has calendar attestations and is waiting for Bitcoin confirmation, while the prior proof remains Bitcoin-confirmed.

What remains incomplete is deeper resilience: durable naming, confirmation of the new timestamp, local Bitcoin Core full-node verification, and real multi-custodian migration.

In short: this package is a stronger continuity candidate, 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 PASS The parent-path package includes a signed lockfile, IPFS Pinata and Arweave Turbo publications, a new OpenTimestamps proof, and an immutable history snapshot. Key Arweave files are verified through both Turbo and arweave.net. The prior package remains verified and retains a Bitcoin-confirmed timestamp.
Level 4: Disaster Recovery and Auxiliary Names PARTIAL A public-artifact recovery rehearsal passed using Cloudflare public routes and the GitHub public archive tag. Durable auxiliary naming remains incomplete.
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 INCLUDED SIGNED This refreshed carrier-ledger package includes a signed organchor.lock.json publication ledger.
Carrier receipts PRESENT WITH IPFS AND ARWEAVE The signed ledger records the 2026-07-15 parent-path package on IPFS Pinata and Arweave Turbo, plus a new OpenTimestamps calendar proof. The new proof is pending Bitcoin confirmation; the prior proof remains Bitcoin-confirmed.
Content-addressed mirror PUBLISHED IPFS A real IPFS Pinata CID is recorded for the parent-path verification package: bafybeie7gdli6pislictn6qobwdkhkazdtbvwsjvtn5ijatjedb3626l4u. This improves carrier redundancy but does not make IPFS or Pinata the identity root.
Arweave transaction PUBLISHED TURBO The parent-path verification package was uploaded through Arweave Turbo: 45 files, directory hash sha256:dcb05c435e4d0d30d6090cc747e7f924ff3c8928cc27889f49efdbc626ebd790. Key files are hash-verified through both Turbo and arweave.net.
Public-artifact recovery PASSED PUBLIC REHEARSAL A public-artifact recovery rehearsal passed using Cloudflare public routes and the GitHub public archive tag; it verified public route bytes, JSON parseability, manifest artifacts, and 4 public signatures.
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

  1. Harden the canonical domain and durable naming strategy.
  2. Upgrade and verify the 2026-07-15 OpenTimestamps proof after Bitcoin confirmation; optionally repeat verification against a local Bitcoin Core node.
  3. Prepare threshold custody only when real independent long-term custodians exist.

What This Does Not Claim

Related Files