The technical layer: start here

From the white paper: section 1 points readers here for current capabilities and the roadmap. This is that live version: it carries the current maturity inventory, the technical detail behind each capability, and the roadmap as it stands.

Fifteen pages sit behind this one, each covering one part of the system. The inventory below gives the current state of the capabilities the white paper describes, current as of 1 October 2026; each row links to the page that covers it. Three labels are used throughout: Live runs today for real institutional users; In build exists and runs, but its trust anchor is a test network, a sandbox or a pilot setting, or its release has not shipped; Research has no shipped code, so pilot it before you rely on it. A capability that is being upgraded appears here as two rows: the rail that runs today, listed Live, and the replacement being brought up beside it, listed In build or Research.

• Holder wallet, iOS and Android Live
  Launched, inherited with the platform Civitas operates; keys and credentials on the device; passcode with optional fingerprint; no user accounts; 24-word recovery phrase
• Issuer and verifier platform Live
  platform.civitasid.org; no-code credential design, issuance, verification, webhooks; carries the Civitas ID brand
• Selective disclosure with consent on the device Live
  The holder presents only the requested attributes, and consents per presentation
• Proof of a fact without the value ("over 18") Live
  On the current credential rail; the wallet validates before sending
• Credential revocation Live
  End to end on the current rail; verifiers receive proof of non-revocation
• Wallet recovery Live
  Recovery phrase plus encrypted backup, both needed; no custodian holds keys. Backup is off until the holder turns it on; offering it after the first credential is decided and not yet built
• White-labeled sub-networks Live
  Sub-network operators run their own branded environment on the platform
• Civitas-branded wallet release In build
  White-label build exists, and a beta build has reached external testers, among them the participants of the first user acceptance test on 25 Sep 2026; no store release and no partner deployment yet
• Trust registry on Stellar In build
  Runs on the test network, wired to the production platform; no mainnet date
• Registry check without live chain access In build
  Wallet verifications carry a registry verdict on the interactions a service attaches the check to; the registry check passes with all non-local network access blocked, while the credential proof check on the current rail still reads its own ledger
• Schema publication In build
  Credential schemas are published off-chain as signed, attested resources under the publisher's own identifier, immutable by construction; published from the Service Dashboard; the owner reviews, repairs and signs the list of published schemas
• DID logs and the log witness In build
  Each institution signs its own key-history log, kept off-chain; a no-administrator contract on the test network records which log version each institution stands behind; every service with an active registry entry runs on its own witnessed log, and a witness counts only when the registry and the institution's own log name the same account; every new service starts with a log, and a dashboard's publishing key cannot change it
• Suspend, revoke, reactivate In build
  Proven end to end; governance-class actions need a two-of-three quorum, rehearsed ahead of the key ceremony that places the keys with three separate holders
• Registry status drives catalog visibility In build
  A suspended issuer disappears from the wallet catalog and from every public service listing
• Issuer onboarding with a Stellar account In build
  Guided application; approval registers the issuer on the test-network registry
• Self-hostable trust-layer services In build
  Three services run on the Civitas platform today: one writes registry entries, one publishes signed copies of the registry, one checks credentials against them; they install from scratch on the test network from their integration guide; open-source release planned for the first half of 2027
• Document-based identity verification In build
  Built into wallet onboarding through a commercial provider; the provider account runs in sandbox; the current integration does not yet cover the refugee identity card issued in Kenya, a second provider for Kenya is being integrated, and coverage in other countries is unconfirmed
• Per-country administrator and trust list Research
  The design gives each deployment its own administrator; not built
• Migration to open credential standards Research
  No standards-compliant release shipped; first releases targeted early 2027
• Standards-based status-list revocation Research
  Target for the new formats; no code
• Newer zero-knowledge proof systems Research
  Two candidate approaches, neither chosen; the choice waits for a benchmark on low-cost devices that has not been run
• Biometric key recovery Research
  An optional second route to the same key, enrolled at wallet setup, so it changes onboarding and not only recovery; error rates on the target devices are unknown and the recovery phrase stays as the fallback
• Wallet redesign for low literacy and low-cost phones Research
  Specified; no screens built
• Goal-path engine Research
  The wallet already points a person to the service that issues a missing credential; the engine that sequences a whole path is targeted for 2027
• Wallet assistant Research
  No assistant code exists in any layer today; pilot-ready target 2027 to early 2028
• Resource Center Research
  Service directory and guidance content connected to the wallet; on the roadmap
• Cross-network recognition Research
  Verification across networks works cryptographically; automated acceptance is a governance and standards track
• Proof-gated disbursement on chain Research
  Feasible on Stellar; the proof circuit is not built

Status, 2026-10-01: this inventory is maintained against the delivery record and is updated when capabilities ship, not when plans change.