Identity

Executive synthesis

Identity is treated as a governed knowledge domain rather than a marketing category. The central analytical focus is identifier continuity, cryptographic control, succession, forks, replicas and legal recognition. A defensible conclusion therefore requires an explicit subject, a named purpose, current source material, and a distinction between what the evidence supports and what remains proposal, inference, or unknown.

The architecture does not permit one property to manufacture another. A valid signature can support payload integrity and key control; it does not by itself prove factual truth, legal identity, personhood, citizenship, or authority. Likewise, a registry record can preserve an institutional decision but cannot create the competence that makes the decision lawful.

The public objective is decision support: identify the relevant category, show current constraints, describe the project’s proposed framework, specify the evidence required, and route governance, registry, assurance, or capital questions to the ecosystem authority that owns them.

Key distinctions

Current state

The current public record supports a structured knowledge model, a static release, and governed source syntheses. It does not establish a universal scientific or legal consensus about Identity. Claims about external deployments, institutions, or legal recognition remain dependent on jurisdiction-specific and system-specific evidence.

Currentness is a separate property. Selected official or first-party sources were revalidated for K03 at 2026-08-15T23:00:00Z. Each source page records its publication status, edition, exact supported propositions, and remaining currentness limits.

Current law or standards

Legal identity is conferred and recognized through applicable institutions and law, not solely through cryptographic proof.

Source language is preserved where statutes and standards use Artificial Intelligence or AI. The project’s preferred term Machine Intelligence does not rewrite external legal text or expand the legal effect of a technical standard.

Project doctrine and future framework

Identity evidence should be cumulative, contestable and purpose-qualified.

Project doctrine is a proposal or interpretive position unless a separate record demonstrates enacted law, authorized implementation, or current operation. The transition from present constraints to a proposed framework should identify competent institutions, implementation controls, due process, correction, appeal, and measurable evidence.

Technical architecture

The implementation model for this domain includes:

• stable subject identifiers.
• key rotation.
• compromise recovery.
• event chains.
• model and memory lineage.
• authorized succession.
• dispute records.

These components should be generated from canonical records so the visible page, machine data, decision history, and correction state cannot silently diverge.

Evidence requirements

• A stable subject, system, claim, or institutional identifier with an explicit scope.
• Authorized source records and a provenance chain showing origin, transformation, and review.
• Separate evidence for authenticity, integrity, relevance, reliability, completeness, currentness, and purpose suitability.
• A record of authority, delegation, decision date, review route, and correction or supersession state.
• Operational evidence when the claim concerns deployment or current operation rather than only a proposal.

Failure modes and adversarial risks

The principal risk is key theft, rollback, cloning, unauthorized forks, false continuity and credential overclaim. Adversaries may exploit semantic ambiguity, stale records, compromised credentials, selective disclosure, copied state, hidden principals, or post-hoc narratives. Controls should assume that a technically valid artifact may still be incomplete, misleading, unauthorized, or unsuitable for the decision being made.

What this topic does not prove

Discussion of Identity does not itself prove consciousness, personhood, citizenship, sovereignty, lawful authority, operational deployment, or factual truth. Those claims require their own definitions, evidence, competent decision-makers, and current status records.

Typed knowledge relations

K03 publishes explicit source, relation, target, rationale, claim status, and supporting-source fields rather than treating every cross-link as equivalent.

• No typed relation directly names this topic in K03; related terms and questions remain linked below.

Inspect the complete relation dataset.

Evidence limitations and contradiction register

Evidence limitations

• A credential is not legal status — Verification does not make the issuer competent, the claim true, the subject consenting or the status legally recognized.
• A model hash is not subject identity — It does not identify one runtime subject, memory history, authority set or continuing actor.

Contradictions or prior conflations

• No topic-specific contradiction record is active in K03.

Related knowledge

Terms

• Identity
• Machine Identity
• Persistent Identity
• Credential
• Workload Identity
• Signing Key
• Cryptographic Identity
• Subject

Questions

• 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?

Reports

• From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon
• Solving the Identity Problem for Machine Citizens: A Framework for Eviuon
• Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification
• Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon
• Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation
• Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust
• Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process

Sources and currentness

• Decentralized Identifiers (DIDs) v1.0 — W3C; DID Core v1.0; W3C Recommendation. Exact claim-support entries: 2. Revalidated 2026-08-14T22:04:09Z.
• Verifiable Credentials Data Model v2.0 — W3C; Verifiable Credentials Data Model v2.0; W3C Recommendation. Exact claim-support entries: 2. Revalidated 2026-08-14T22:04:09Z.
• RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile — IETF; RFC 5280 with update chain; Proposed Standard. Exact claim-support entries: 2. Revalidated 2026-08-14T22:04:09Z.
• PROV-O: The PROV Ontology — W3C; W3C Recommendation 30 April 2013; W3C Recommendation. Exact claim-support entries: 2. Revalidated 2026-08-14T22:04:09Z.

Research cutoff: 2026-08-16. Correction state: K03 public correction, contradiction, supersession, and evidence-limitation registers apply; 0 contradiction record(s) directly name this topic.

Material topic 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.