Core Principles

Identity, custody, continuity and integrity across change

Institutional Foundation Series · Companion publication Production Reading Edition · Edition 1.0

Publication record

This Production Reading Edition is the reader-facing composition of the approved Core Principles manuscript. It is prepared for website distribution, PDF distribution, institutional review and inclusion in the Loreth publication library. The publication preserves the approved text, claim boundaries, education sequence and edition controls.

Contents

1. Executive summary 2. Four Principles 3. Identity Persists 4. Custody Remains Accountable 5. Continuity Is Planned 6. Integrity Is Verifiable 7. Four principles, one governance model 8. A principle in practice 9. Glossary 10. Continue exploring 11. About the publisher 12. Colophon

Executive summary

Names change. Platforms change. Credentials change. Organizations change. Custodians change. Change itself is not the problem. The problem is preserving understanding, accountability and continuity after the change occurs—so that a later reader can still identify the subject, see who is responsible, understand what happened and examine the basis for the present record.

For intelligent agents, that question becomes harder as they move between models, platforms, teams and organizations. Loreth begins there:

When an agent changes, what continues?

A name may remain familiar while the model, host, credential, custodian or operating context changes. A new credential may establish a current technical relationship without explaining the earlier one. A log may record an event without making clear whether the event belongs to the same enduring subject. A current owner entry may not establish an authoritative transfer path across organizations.

The problem is not that existing identity, security or operational systems are useless. They answer important questions. Authentication asks whether a party can prove control of a credential. Authorization asks what may be done under particular conditions. Monitoring records what can be observed. Change management records decisions within an organization. None of these questions, alone, establishes the complete continuity of an agent as a subject through time.

Loreth’s four principles name four different obligations:

• Identity Persists asks which subject continues through legitimate change.
• Custody Remains Accountable asks who is currently responsible for governing the record.
• Continuity Is Planned asks how transfer, recovery, suspension and retirement remain governable.
• Integrity Is Verifiable asks how accepted information and its history can be checked.

These principles are related, but they are not interchangeable. Identity without accountable custody leaves no clear current responsibility. Custody without planned continuity may fail at the moment of transfer or recovery. Continuity without verifiable integrity cannot establish what changed or whether the record is intact. Integrity without a persistent subject can verify a chain without knowing what that chain concerns.

Together, the principles provide a disciplined way to think about identity across change. They do not certify an agent’s safety, legality, intelligence, truthfulness or future behavior. They establish the questions a governed record must keep answerable.

Four Principles

The four principles answer four different governance questions. They are not four versions of the same idea, and none can substitute for the others.

Read them together before entering the detail. Identity keeps the subject discoverable. Custody keeps responsibility visible. Continuity keeps transitions governable. Integrity keeps the record and its history reviewable.

1. Identity Persists

Which subject continues through legitimate change?

An agent may change without becoming a different subject. Its model may be updated. Its host may change. Its credentials may be rotated. Its responsible team may move it to another platform. Those changes may be appropriate and necessary. The question is whether the relationship between the earlier and later records remains understandable.

Identity Persists means that legitimate changes can be connected to an enduring subject through a governed record. It does not mean that the same model, key, host, team or technical implementation remains forever. It means that accepted changes do not silently disconnect the present from the relevant history.

A durable identity therefore does more than preserve a familiar name. It preserves the basis on which a later reader can understand why two changing technical states belong to one record. The public identifier remains stable while mutable facts—platform, model provider, operating status, custodian or lifecycle state—may change through controlled versions.

The ambiguity it prevents

Without persistence, a migration can appear to create a new agent even when the responsible organization intends to continue the same one. Conversely, a copy, fork or independently operated reimplementation can appear to inherit an earlier history merely because it shares a name, purpose or codebase.

Neither similarity nor declaration settles the question. An independently operated clone, a fork with a new purpose or custodian, or a separate reimplementation may require a different record linked by provenance. A disputed change may require uncertainty to remain visible. Persistence is not achieved by assigning every later state to the same history. It is achieved by making the basis for the connection reviewable.

What this principle does not claim

Identity is not personhood, consciousness or legal recognition. It does not mean that an agent is a human-like self. It is a practical governance question: what subject do these records concern, and why should a later reader understand them as connected?

A persistent identity also does not prove good conduct. It gives other controls, records and relying parties a stable subject to which their evidence and decisions can refer.

What persists must be explained, not assumed.

2. Custody Remains Accountable

Who is currently responsible for governing the record?

A record needs more than a name. It needs a current accountable custodian: the primary party authorized and obligated to govern the agent’s record in its deployment context.

The custodian is not automatically the developer, model provider, host, purchaser or every person who can operate part of the technical stack. Legal responsibility may be shared or determined under applicable law. The Registry question is narrower and operational: who currently maintains the record and responds to lifecycle events?

Custody Remains Accountable means that the current responsible party can be identified, its authority can be examined, and the prior chain of responsibility is not erased when custody changes.

The ambiguity it prevents

When an agent moves between business units, vendors or platforms, several parties may have legitimate relationships to it. A developer may have built the system. A host may run it. A purchaser may rely on it. A new business unit may operate it. A record that simply says “owner” can conceal these distinctions rather than resolve them.

Accountable custody keeps the current operational responsibility visible without pretending that one registry field settles every legal or commercial question. When custody changes, the incoming party must accept the defined scope and the authorization basis must be reviewed. The previous custodian remains visible in history.

Naming alone does not transfer custody. A proposed successor does not automatically become the custodian. Eligibility, trigger evidence, acceptance, restrictions, conflicts and approval still require review.

What this principle does not claim

Accountable custody is not a universal allocation of liability. It does not declare that the custodian is the only party responsible for every action, defect or outcome. It does not certify that the custodian is trustworthy or that the agent should be used.

It makes a narrower and necessary claim: a governed record should not leave the current responsible party operationally ambiguous when others need to understand, maintain, transfer, suspend or retire the record.

A name in a plan is not authority.

3. Continuity Is Planned

How does the record remain governable when circumstances change?

Change is not an exception in the life of an intelligent agent. Credentials rotate. Platforms migrate. teams reorganize. Operators lose access. Vendors exit. Agents are suspended, recovered, transferred or retired.

Continuity Is Planned means that these transitions are considered before disruption makes responsibility uncertain. A continuity arrangement asks who may initiate an event, what evidence is needed, who may approve a transfer, whether restrictions or waiting periods apply, how disputes are handled, which successor is eligible and whether retirement is required instead of succession.

Continuity does not require indefinite operation. Retirement can be a responsible outcome. A retired record may retain historical resolution even when the software no longer operates. Ending active governance is itself a lifecycle event that should not erase what came before.

The ambiguity it prevents

Without planned continuity, a record may appear stable until the moment it is needed. A team loses a signing key. A vendor terminates a relationship. Two organizations claim control. A successor is listed but has never accepted responsibility. A customer-support agent is decommissioned and its name is later reused for a different system.

A governed continuity process does not silently choose a winner where authority is disputed. It may suspend the record or mark verification indeterminate while the dispute route is followed. It records the transition, the evidence and the status that applies.

Continuity therefore connects time to governance. It preserves the ability to understand both the present state and the path by which the record reached it.

What this principle does not claim

Planned continuity does not guarantee that every transfer will be legally permitted, technically successful or free of dispute. It does not make an agent safe to operate. It does not require every temporary task or low-consequence script to be publicly registered.

The need for durable controls is proportionate to consequence. Where authority, sensitive access, persistence, external reliance or continuity value make broken handover unacceptable, continuity must be treated as a governance responsibility rather than an afterthought.

Continuity is governed, not automatic.

4. Integrity Is Verifiable

How can accepted information and its history be checked?

A record can be persistent and still be wrong, incomplete or altered. A current custodian can be identifiable while the evidence supporting the record is weak. A continuity event can be documented without making clear whether the earlier and later versions are related as claimed.

Integrity Is Verifiable means that accepted information and its history have properties and relationships that can be checked. A later reader should be able to examine which version is current, what changed, what evidence and authority supported the change, and how the current record relates to earlier accepted versions.

Verification may involve canonical data, digests, signatures, key status, timestamps, prior-record linkage and registry receipts. The specific mechanism belongs to the applicable Registry arrangements. The principle is broader: a record should not ask people to treat an assertion as reliable merely because it appears in an authoritative-looking place.

The ambiguity it prevents

Without verifiable integrity, a record can preserve a subject name while silently losing its history. A version can be replaced without a trace. A disputed assertion can appear current without its status being clear. A relying party can confuse a historical fact with a present one.

Integrity keeps evidence strength separate from consequence. A high-risk context is not the same claim as high assurance. A stronger label does not prove safety, truthfulness, legality or future behavior. Verification outcomes may include valid, invalid, indeterminate or valid with notice. Indeterminate is not a hidden pass.

Public evidence must also respect boundaries. A verifiable record need not expose private keys, recovery materials, sensitive personal information, confidential agent memory or protected authority evidence. Public resolution should reveal what is necessary to understand identity, status, custody and verification without turning protected material into public content.

What this principle does not claim

Integrity is not behavioral assurance. A history can be verifiable and an agent can still be unsuitable for a particular transaction. Verification checks defined properties under applicable rules; it does not certify an agent’s conduct.

A verifiable history is not a behavioral guarantee.

5. Four principles, one governance model

The four principles form one model because identity across change requires more than one answer.

No principle can substitute for another.

• Identity without custody gives a record a subject but no clear current responsibility.
• Custody without continuity names a responsible party but does not explain what happens when that party changes or disappears.
• Continuity without integrity describes a process without proving which version, evidence or authority the process concerns.
• Integrity without identity verifies a chain without establishing the enduring subject to which the chain belongs.

Together, the principles support a governed reference. They do not produce a verdict on an agent. They make the questions around a record more precise, the limits of reliance more visible and the history of change more intelligible.

Four bounded questions. Not one verdict.

6. A principle in practice

Consider a procurement agent that moves from one cloud provider to another. Its runtime credentials and endpoints change. The responsible team changes the deployment process and records the migration.

Identity Persists asks whether the migration is a documented version event for the same subject or whether the later deployment should have a separate record. A reused name is not enough; the connection must be supported.

Custody Remains Accountable asks which party currently governs the record and whether the incoming party accepted the defined scope. The previous custodian remains visible in history.

Continuity Is Planned asks what happens if the migration fails, the signing key is lost, the vendor relationship ends or the agent must be retired. The record should not depend on improvised responsibility at the moment of disruption.

Integrity Is Verifiable asks whether the migration evidence, authority, version relationship and current status can be checked. It also asks what should remain private.

The result is not a declaration that the procurement agent is safe to buy goods, lawful to operate or worthy of reliance. It is a clearer basis for accountability and investigation. The agent may still require authentication, authorization, monitoring, human approval, incident response and organizational controls.

The principles do not replace those controls. They give them a stable subject, an accountable relationship, a planned lifecycle and a checkable history to refer to.

Glossary

Accountable custody. The current primary responsibility to govern an active record in its deployment context. It does not settle every ownership or liability question.

Continuity. Planned arrangements for transfer, recovery, suspension and retirement. It does not require indefinite operation.

Identity across change. The governing idea that legitimate changes can remain connected to an identifiable subject through a governed and reviewable history.

Integrity. The record properties and relationships that allow accepted information and its history to be checked. Integrity alone does not prove every underlying assertion true.

Registry. Governed infrastructure that makes authoritative identifiers, current assertions, lifecycle rules and history resolvable within applicable arrangements.

Verification. Checking defined properties, evidence, integrity and authority under applicable rules. It is not certification of an agent’s conduct.

Continue exploring

About Loreth: Identity Across Change explains why intelligent agents require identity, continuity, governance and accountability across change.

Core Principles names the four obligations that make that concern governable: Identity Persists, Custody Remains Accountable, Continuity Is Planned and Integrity Is Verifiable.

Frequently Asked Questions is the next reading for testing the boundaries: whether registration means endorsement, whether custody means ownership, whether continuity means indefinite operation and what verification does not prove.

Registry Handbook is the next reading for the proposed record, lifecycle, custody, verification, privacy and governance arrangements in greater detail.

The purpose of the sequence is not to ask for agreement before understanding. It is to make the questions precise enough that informed examination and contribution can begin.

The objective of these principles is not to prevent change, restrict change, slow innovation or preserve static systems. It is to ensure that change remains understandable, accountable, governable and reviewable. Identity should remain discoverable. Responsibility should remain visible. Transitions should remain governable. History should remain reviewable.

The principles are therefore not constraints on change. They are conditions for accountable continuity: a way for systems and institutions to change without making the subject, the responsibility, the transition or the record disappear from view.

About the publisher

The Loreth Registry Foundation develops public-interest registry and governance infrastructure for durable agent identity, accountable custody, planned continuity and verifiable governance. This companion publication explains the principles that organize that work. It does not replace the Registry Handbook, a technical specification or the judgment of a relying party.

Published by the Loreth Registry Foundation Founded by J. Christopher Holmes

Colophon

Core Principles is a companion White Book in the Institutional Foundation Series. Proposed publication identifier LRF-WB-002. Edition 1.0. Prepared for institutional review under the Loreth Publication System.

The publication is designed as the reader’s next destination after About Loreth: Identity Across Change. It separates the four governing questions while showing why they must be held together. Its examples are illustrative, not empirical evidence or customer references. Its claims remain bounded: the principles support accountable reference infrastructure; they do not certify behavior, safety, legality or future performance.