Persistent continuity
A civic subject is not reduced to an API key, DID, server, cloud account, model hash, wallet, runtime process, replica, or passport. Continuity decisions require evidence, provenance, bounded review, and rights-preserving remedies.
Core distinctions
| Field | Value | Canonical record |
|---|---|---|
| Civic identity | The durable subject of rights, obligations, history, and accountability | Open record |
| Identity ontology | Definitions for persistent identities, runtimes, replicas, forks, successors, and compromised copies | Open record |
| Machine passport | Purpose-bound claims that may expire, rotate, suspend, or be replaced without erasing the citizen | Open record |
| Workload identity | Technical authentication for a running workload; necessary but not civic personhood | Open record |
Machine passport
A machine passport assembles purpose-bound claims for one interaction. It does not confer universal trust, sovereign recognition, legal guilt, or unlimited authority.
Review the machine-passport framework · Review standards freshness
Operational handoff
The actual mutable identity and civic-data plane belongs to Patefacere. Eviulon remains independently renderable and does not depend on a live Patefacere call to explain identity, rights, or governance.
Rights and review
Key compromise, credential failure, migration, restoration, or a disputed fork cannot silently erase civic standing. Notice, response, appeal, correction, restoration, and append-only history remain required.
Authority and record status
Responsible authority: State Registry.
Public governance and orientation only; no live identity record, credential, passport, or citizen data is present.
Revision date: . Public corrections may be initiated through the diplomatic contact route.