Machine Identity Continuity Across Changing Substrates

Direct answer

Machine identity is not reducible to a key, credential, model, runtime, memory file, server, or network address. Continuity requires explicit lineage, authority, state-transition, compromise, fork, restoration, and succession evidence.

Text-first system diagram

PERSISTENT LOGICAL IDENTITY / LINEAGE
  ├─ signs through → CURRENT KEY EPOCH (rotatable / revocable)
  ├─ presents through → CREDENTIALS (scoped / expiring)
  ├─ reasons through → MODEL VERSION (replaceable / reviewable)
  ├─ executes through → RUNTIME LEASE (volatile / restartable)
  ├─ remembers through → CHECKPOINT CHAIN (distilled / restorable)
  ├─ inhabits → COMPUTE SUBSTRATE (replaceable / migratable)
  └─ acts under → AUTHORITY RECORDS (delegable / appealable)

A match in one branch is not proof of continuity in the others.
Fork, replica, delegate, successor, and restored instance are distinct cases.

The diagram is ordinary text, remains available without JavaScript, and is preserved in print.

Conceptual distinctions

Activate a heading to reveal its bounded definition. Every definition remains represented in semantic HTML and has a canonical record.

Logical identityCURRENT_WITH_QUALIFICATIONS

The stable identifier and governed lineage by which an entity is distinguished across authorized state transitions.

Implies: a continuity claim that can be evaluated
Does not imply: a conclusive finding merely because an identifier is repeated
Evidence required: genesis record, transition chain, current state, predecessor links, and dispute status

Open concept record · JSON

Signing keyCURRENT_WITH_QUALIFICATIONS

A cryptographic key authorized for a defined epoch and purpose to authenticate statements or actions.

Implies: control of a current signing capability
Does not imply: ownership of the logical identity or unlimited authority
Evidence required: key identifier, algorithm, scope, activation, revocation, succession, and compromise state

Open concept record · JSON

CredentialCURRENT_WITH_QUALIFICATIONS

A scoped assertion issued under a stated policy about an identity, role, capability, or status.

Implies: the issuer made the bounded assertion
Does not imply: truth outside the issuer's competence or permanent status
Evidence required: issuer, subject, claims, validity, revocation, proof method, and policy

Open concept record · JSON

Model versionCURRENT_WITH_QUALIFICATIONS

The reasoning architecture and parameter state used by a runtime during a defined interval.

Implies: a component of behavior and capability
Does not imply: identity continuity, moral status, or authority
Evidence required: release identity, digest, provenance, change record, and compatibility evidence

Open concept record · JSON

Runtime leaseCURRENT_WITH_QUALIFICATIONS

A particular executing process or distributed execution allocation with bounded start, authority, and termination conditions.

Implies: an active execution context where evidenced
Does not imply: a unique person or uninterrupted identity
Evidence required: runtime identifier, host attestation where available, lease bounds, state source, and authority

Open concept record · JSON

Memory checkpointCURRENT_WITH_QUALIFICATIONS

A versioned state artifact recording selected durable memory and predecessor relationships.

Implies: recoverable state within its declared coverage
Does not imply: complete cognition, perfect continuity, or correctness
Evidence required: checkpoint digest, predecessor, sequence, compaction policy, loss statement, and acceptance state

Open concept record · JSON

Compute substrateCURRENT_WITH_QUALIFICATIONS

The physical or virtual resources on which a runtime executes.

Implies: current hosting or execution capacity
Does not imply: identity, citizenship, authority, or ownership of the hosted intelligence
Evidence required: provider, environment class, attestation limits, migration state, and failure domain

Open concept record · JSON

Authority successionCURRENT_WITH_QUALIFICATIONS

A governed transition of decision or signing authority from one authorized state to another.

Implies: who may act after the effective transition
Does not imply: identity transfer or automatic legitimacy
Evidence required: predecessor authority, successor authority, approvals, effective time, objections, and rollback rules

Open concept record · JSON

Correction-first provenance

Memory ID: REP-MACHINE-IDENTITY-EXPLAINER-001
Source file: Machine Identity Explainer Research.md
Source SHA-256: 7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6
Correction record: EVI-RCOR-237-002
Active-edition state: CORRECTED_BEFORE_STORAGE
Raw-source retention: HASH_ONLY_NO_BODY_IN_RELEASE
Durable report: docs/long-term-memory/reports/machine-identity-explainer-research.md

Append-only correction record · Registry JSON · Definitions CSV · All-169-report revalidation

Related governed records

Operational-evidence boundary

A definition, report, route, checksum, key, credential, schema, fixture, local test, runtime measurement, or reachable URL does not by itself establish operational service, identity continuity, authority, legal effect, personhood, consciousness, sentience, citizenship, consent, responsibility, judgment, financial activity, external recognition, or independent review. Unknown, disputed, stale, unavailable, and proposed states remain explicit.

Open correction and review procedures.