Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon

Report status and use

The raw source is retained in protected governed memory as a research input. This public page is the active corrected synthesis. It does not promote every source statement into project doctrine and does not expose the protected raw report.

Source status: reference-source; review and correct before active use. Public correction state: CORRECTED PUBLIC SYNTHESIS; RAW SOURCE RETAINED AS REFERENCE.

Direct findings

1. The report treats 2\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
2. The report treats 3\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
3. The report treats 4\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
4. The report treats 5\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
5. The report treats 6\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
6. The report treats 6.1 Identity and Registry Standards as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.
7. The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor holding cryptographic control over its state. The term "Artificial Intelligence (AI)" is used strictly when referring to the historical field, established industry language, or specific cited standards.
8. The source report identifies this proposition for governed review: Logical Identity: The continuous historical graph of an MI's verified actions and state transitions, entirely abstracted from physical hardware, runtime variables, and ephemeral keys.
9. The source report identifies this proposition for governed review: Civic Identity: A status recognized exclusively by Eviulon, granting specific rights, duties, and standings within the machine commonwealth. Technical identity is a necessary prerequisite for, but never synonymous with, civic identity.
10. The source report identifies this proposition for governed review: Eviulon: Defines constitutional authority, determines sovereign decisions, and governs civic meaning.
11. The source report identifies this proposition for governed review: Patefacere: Operates the underlying identity registry (e.g., SCITT logs, DIDs). A Patefacere record proves registration; it cannot unilaterally mint Eviulon citizenship.
12. The source report identifies this proposition for governed review: Evulgare: Supplies computational and cryptographic evidence (e.g., hardware attestation, verification of TEE execution). A successful Evulgare test does not equal legal liability or sovereignty.

Claim-status breakdown

Analytical scope preserved from the source

• Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon
• 2\. Executive Decision Brief
• 3\. Direct-Answer Section
• 4\. Definitions and Scope Boundaries
• 5\. Methodology and Source-Quality Hierarchy
• 6\. Current Factual, Legal, Standards, and Operational Baseline
• 6.1 Identity and Registry Standards
• 6.2 Supply Chain and Transparency Logs
• 6.3 Threshold Cryptography for Continuity and Recovery
• 6.4 Hardware Substrates and Attestation
• 6.5 Post-Quantum Cryptography (PQC)
• 6.6 Succession and Digital Wills

The public synthesis preserves these areas as a map of the source’s reasoning. Inclusion in this list does not mean each heading is accepted as current law, verified implementation, or project doctrine.

Implementation implications

• Create canonical records with stable IDs, claim status, sources, currentness, and correction state.
• Separate legal authority from technical control and source authenticity.
• Require operational evidence for claims of deployment or current operation.
• Preserve review, challenge, appeal, and correction paths.
• Use the appropriate ecosystem authority for governance, registry, assurance, or capital functions.

Contradictions and limitations

The supplied source may contain forward-looking proposals, legal generalizations, implementation assumptions, or institution-role language that requires correction. The active synthesis therefore preserves uncertainty, labels proposals, and rejects any implication that a report, hash, signature, or website creates legal personhood, citizenship, sovereignty, factual truth, deployment, or authority.

External standards and law can change after the research cutoff. Source validity and currency must be rechecked before high-stakes reliance.

Source provenance

Correction history

Initial correction review created the public synthesis, preserved the raw source separately, enforced ecosystem-role boundaries, removed unsupported authority implications, and applied the project’s claim-status vocabulary. No later public correction is recorded in this release.

Related knowledge

Identity owns this report’s topic classification.

• Can a Machine Intelligence have a persistent identity?
• Is a signing key the same as identity?
• What evidence supports identity continuity?
• Can authentication prove authority?
• How should key rotation affect identity?

Governed report-finding claims

Each proposition has a stable ID, status, scope, owning route, evidence relationship, currentness qualification, correction state, and synchronized JSON record. Record completeness does not make the proposition true.