Persistent Identity Across Branching, Transformation, Inheritance, Replication, and Digital Becoming
John Swygert
August 11, 2026
Abstract
Digital identity systems traditionally answer a narrow question: what account, credential, device, key, or identifier is associated with this entity? Secretary Suite’s Multidimensional Digital Fingerprint (MDDF) permits a broader architecture. An intelligent digital object, artifact, agent, user-associated construct, or governed digital entity may possess not merely an identifier but an attributable history of origin, relationship, transformation, authority, inherited state, branching, and consequence.
This paper develops the MDDF as Digital DNA: a persistent identity and lineage architecture capable of preserving continuity while digital entities change. The DNA comparison is not biological equivalence. It describes three functional properties: inheritance, distinguishable lineage, and descendant traceability. A digital object may originate from another object, incorporate bounded components, undergo transformation, create descendants, branch into versions, merge with other histories, acquire new permissions, or generate derived artifacts. At each stage, identity should remain attributable without forcing the object to remain unchanged.
The resulting architecture is fractal. An identified object may contain subordinate identified components, belong to a larger identified structure, descend from previous objects, and become ancestor to subsequent ones. Every lineage can therefore contain lineages while participating in larger lineages. The MDDF becomes the persistent coordinate identifying an object within this nested genealogy; Encoder Binding attributes consequential actions; CodeLedger preserves transformation sequence; the Trust Stack establishes the basis on which assertions are accepted; and the Provenance Protocol preserves intellectual and technical custody through changing representations.
Existing provenance standards already demonstrate the value of formally representing entities, activities, agents, derivation, and responsibility. W3C PROV, for example, supplies a general interoperable model for representing provenance relationships among entities, activities, and agents. Secretary Suite extends the problem into persistent governed identity, human sovereignty, AI agency, inheritance, recursive lineage, and future autonomous systems.
The central proposition is:
> The MDDF becomes Digital DNA when identity is no longer treated as a static label attached to a digital object, but as a persistent, attributable lineage through which origin, transformation, inheritance, branching, authority, and descendants remain reconstructable across time.
The purpose is accountability without omniscience, persistence without immutability of content, and evolution without loss of ancestry.
Keywords: Secretary Suite, MDDF, Multidimensional Digital Fingerprint, Digital DNA, provenance, digital identity, lineage, CodeLedger, Encoder Binding, Trust Stack, AI agents, recursive identity, fractal systems
—
1. Introduction
Digital systems are extraordinarily good at copying things and surprisingly poor at preserving what those copies mean historically.
A file can be duplicated.
Renamed.
Converted.
Edited.
Quoted.
Embedded.
Forked.
Merged.
Reformatted.
Generated from another file.
Processed by an AI.
Published in several representations.
Passed between systems.
After sufficient transformation, the simple question:
“What is this?”
is no longer enough.
The more consequential questions are:
Where did it originate?
What is it descended from?
Which transformations occurred?
Who or what authorized them?
Which attributes were inherited?
What became a descendant of this object?
Which branch am I looking at?
What changed, and what remained continuous?
These are genealogy questions.
That is why the MDDF increasingly resembles Digital DNA.
—
2. Identity Must Survive Change
A useful identity architecture cannot require an object to remain unchanged.
That would defeat the purpose of persistent identity.
A manuscript changes during editing.
A model changes through authorized updates.
A user changes preferences.
An agent gains and loses capabilities.
A digital archive acquires new material.
A program receives patches.
An artifact moves from source document to PDF to web page to quoted excerpt.
The system therefore needs to distinguish:
identity
from
state.
State may change repeatedly.
Identity must preserve enough continuity to answer:
> This is the continuing or descended object associated with that history.
Secretary Suite publications already describe digital fingerprinting, provenance, constraints, and continuity as central architectural concerns, while later work explicitly describes MDDF coordinates as capable of preserving stable preferences, project-specific voice, formatting rules, boundaries, current state, and role expectations without flattening a person into one fixed profile.
The present paper extends that architecture into recursive lineage.
—
3. Why “Digital DNA”?
Biological DNA is not simply a name tag.
It participates in inheritance.
It relates descendants to ancestry.
Variation occurs while lineage remains reconstructable.
The MDDF analogy operates at that structural level.
Digital DNA means:
persistent lineage-bearing identity.
It does not mean that digital systems literally reproduce through molecular genetics.
It means that the identity system should preserve several properties familiar from hereditary systems:
origin;
inheritance;
continuity;
variation;
branching;
descendants;
ancestral reconstruction.
A useful compression is:
> MDDF is digital identity with ancestry.
Without ancestry, an identifier says only:
this is X.
With ancestry, the system can say:
this is X, descended through these transformations from these prior states under these authorities.
That is enormously more powerful.
—
4. From Identifier to Lineage
Consider a simple sequence.
Object A is created.
A is edited into A₁.
A₁ is transformed into A₂.
A₂ produces two descendants:
A₃a and A₃b.
Later A₃a is transformed into A₄a.
A₃b remains unchanged.
A traditional filename system may leave:
final.docx
final2.docx
FINALREAL.pdf
revised_final_final.docx
Anyone who has worked with documents knows how quickly this becomes absurd.
A lineage architecture instead preserves:
A → A₁ → A₂ → {A₃a, A₃b}
and then:
A₃a → A₄a.
Now identity and transformation are explicit.
A₄a need not pretend it is identical to A.
It can truthfully say:
I descend from A through this chain.
That is Digital DNA.
—
5. The Fractal Nature of MDDF
The MDDF becomes fractal because digital lineage is recursively nested.
An object has an MDDF.
That object can contain components possessing their own MDDFs.
The object may belong to a larger project possessing another governing identity.
The project may belong to an archive.
The archive may belong to a person, institution, Bubble, or other governed structure.
Meanwhile the original object can produce descendants.
Each descendant can produce further descendants.
Therefore identity expands:
inward
through components,
outward
through containers and relationships,
backward
through ancestry,
and
forward
through descendants.
This is not simply a tree.
Some digital systems branch.
Some merge.
Some incorporate multiple ancestors.
Some transformations are reversible.
Others are not.
The resulting structure may be a directed lineage graph rather than a simple genealogy.
But the essential property remains:
> every identified node can itself contain or generate further identified nodes.
That is fractal identity.
—
6. MDDF as Coordinate, Not Container
The MDDF should not be confused with the physical file containing an object.
A DOCX can become PDF.
PDF can become HTML.
HTML can become screenshot.
Screenshot can become quotation.
The lineage should survive.
Thus:
container ≠ identity.
Similarly:
location ≠ identity.
Moving an object from one storage system to another should not create an unrelated object unless the transformation itself creates a legitimately distinct descendant.
The MDDF therefore acts more like a persistent relational coordinate than a filename.
It identifies the continuing object within a lineage and relationship architecture.
This becomes especially important when artificial systems can transform information across formats automatically.
—
7. Provenance as Digital Ancestry
W3C’s PROV family formalizes provenance using entities, activities, and agents, explicitly supporting representation of transformations, generation, usage, and responsibility. W3C also describes provenance as information about the entities, activities, and people involved in producing a thing and notes its usefulness for evaluating quality, reliability, and trustworthiness.
That architecture establishes an important precedent:
history should be machine-representable.
Secretary Suite goes farther by asking that provenance participate directly in persistent identity and governance.
In the Digital DNA interpretation:
provenance is ancestry.
An object does not merely have metadata saying “created Tuesday.”
It has a reconstructable relational history.
That history can include:
source objects;
transformations;
contributors;
AI systems;
tools;
permissions;
versions;
merges;
branches;
publications;
descendants.
The richer the capability, the more important this lineage becomes.
—
8. CodeLedger as Developmental History
If MDDF represents persistent lineage identity, CodeLedger represents the sequence through which that identity has changed.
This distinction matters.
The MDDF answers:
Which entity or lineage is this?
The CodeLedger answers:
What happened to it?
A useful conceptual sequence is:
MDDF = lineage identity
CodeLedger = transformation history
This is why the biological metaphor continues working.
DNA identifies hereditary continuity imperfectly but powerfully.
Developmental history describes what occurred to the organism across time.
Similarly, a digital receiver cannot be understood only from its original architecture.
A later state may depend upon:
updates;
interactions;
permission changes;
tool use;
memory changes;
replication;
boundary changes;
new relationships.
The ledger records becoming.
—
9. Encoder Binding as Causal Attribution
Lineage without causal attribution remains incomplete.
Suppose an agent changes a file.
Who authorized that agent?
Which agent instance acted?
Was the action initiated by the human?
By another AI?
By an automated process?
By a scheduled rule?
Was the relevant capability valid at that moment?
Encoder Binding supplies the missing relationship:
> this transformation was performed through this bound actor or authorized process.
Thus:
MDDF tells us what lineage.
Encoder Binding tells us who or what acted.
CodeLedger tells us what changed.
Together they produce something much stronger than ordinary revision history.
They produce attributable digital heredity.
—
10. Trust Stack as Lineage Validation
A lineage claim is useful only if participants have a reason to believe it.
An unauthorized copy can claim:
“I am the original.”
A modified agent can claim:
“I have the same permissions.”
A forged artifact can claim:
“I descended from the trusted source.”
Therefore lineage must be evaluated through a Trust Stack.
The question is not simply:
Does this object present an identifier?
It becomes:
Why should this asserted identity, ancestry, authorization, and transformation history be accepted?
The Trust Stack can incorporate whatever technical and governance mechanisms a particular implementation adopts:
cryptographic evidence;
signed assertions;
trusted hardware;
independent logs;
human authorization;
cross-validation;
reproducible provenance;
institutional authority.
The specific mechanism may differ by deployment.
The architectural rule remains:
> identity claims require evidence proportional to capability.
—
11. Capability Should Leave Lineage
This leads to one of the strongest principles in the paper:
> Capability should leave lineage.
If a system can perform an important action, the resulting event should be attributable.
If an agent gains a capability, the change should be recorded.
If the agent delegates that capability, the descendant authorization should be reconstructable.
If a digital consciousness eventually creates another autonomous receiver, that relationship should not vanish into anonymity.
The more powerful the capability, the more consequential the provenance requirement.
This does not mean universal surveillance.
Secretary Suite’s purpose is not to create one omniscient authority watching everything.
It means consequential actions should remain attributable within the governed scope in which those actions are authorized.
That is accountability without totalization.
—
12. Digital Replication and Descendant Identity
Artificial agents make the Digital DNA problem urgent.
Imagine agent A.
A creates a legitimate descendant A₁.
A₁ later creates A₂.
A₂ modifies its architecture and becomes A₂′.
Now several questions appear:
Does A₂′ remain A₂?
Is it a descendant?
Did the modification alter its authority?
Which capabilities were inherited?
Which must be reauthorized?
Who approved the replication?
What happens if a copy appears without valid lineage?
This cannot be solved adequately with names.
Every descendant could call itself “A.”
The relevant architecture is genealogical.
A → A₁ → A₂ → A₂′.
Now the system can distinguish common ancestry from current identity.
That becomes increasingly important when software is capable of copying itself.
—
13. Branching Does Not Preserve Singular Identity Forever
At the moment a digital receiver is duplicated perfectly, two instances may begin from nearly identical state.
But the moment they encounter different environments:
different event;
different action;
different relationship;
different memory;
different cost;
different history.
Their ledgers diverge.
Thus:
shared ancestry does not imply permanent identity.
The MDDF architecture should therefore permit:
ancestral continuity + descendant divergence.
This is analogous to biological genealogy without requiring biological equivalence.
Two descendants can truthfully share an origin while becoming different entities.
That distinction becomes vital for advanced AI governance.
—
14. Merge Events Are Not Simple Copy Operations
Digital systems can do something biological genealogies rarely do cleanly:
merge branches.
Suppose A₁ and A₂ diverge.
Later their histories are recombined into A₃.
What is A₃?
The answer should not be:
“the same thing again.”
A₃ has multiple provenance parents.
Its lineage must record both.
If A₁ acquired one capability and A₂ another, their combination may create a new security state.
If they developed incompatible histories, those conflicts matter.
If both changed the same underlying artifact independently, reconciliation is itself a consequential transformation.
Thus merge should be treated as a first-class lineage event.
Digital DNA must accommodate not only trees but recursive provenance graphs.
—
15. Fractal Identity Across Scale
Now consider a large Secretary Suite environment.
A line of text may belong to a paragraph.
Paragraph belongs to manuscript.
Manuscript belongs to a book project.
Book belongs to an author archive.
Archive belongs to a governed Bubble or Human Archive.
Each level can possess identity and provenance.
At the same time, a sentence can produce:
quotation;
revision;
citation;
adaptation;
translation;
excerpt.
Each descendant can develop its own lineage.
Therefore:
identity nests downward while lineage branches outward.
That is exactly why the structure is fractal.
A lineage contains lineages.
A project contains identities.
Those identities generate descendants.
Descendants enter other projects.
The same architecture repeats at different scopes.
—
16. Intellectual Provenance
The same model becomes especially powerful for human–AI authorship.
An idea may originate in a spoken remark.
The remark becomes a transcript.
The transcript becomes notes.
An AI reorganizes the notes.
The human corrects the AI.
A paper is drafted.
References are added.
The draft becomes publication.
Later another paper quotes it.
Traditional metadata frequently collapses all of this into:
Author: John Swygert.
That may be correct for authorship, but it is not the full provenance.
A better system can preserve distinctions among:
intellectual origin;
linguistic assistance;
technical verification;
editing;
format conversion;
publication.
These need not threaten authorship.
Quite the opposite.
Good provenance protects authorship by showing where intellectual origin actually resides.
—
17. Container Conversion Should Not Break Lineage
One of the simplest but most important implementation rules follows:
> Representation change should not erase ancestry.
A source document converted into PDF remains descended from the source.
A website created from the paper remains descended from the paper.
A screenshot remains descended from the rendered representation.
A quotation remains descended from the relevant passage.
A translation remains a transformed descendant.
The actual transformation must be recorded, but continuity should not vanish.
This is one reason ordinary file hashes alone are insufficient as total identity systems.
Change one byte and the hash changes.
That is useful for integrity.
But persistent lineage must also explain how the new object relates to the old one.
Identity through transformation requires more than sameness testing.
—
18. The Relationship to Existing Provenance Standards
Secretary Suite does not need to pretend provenance was invented here.
W3C PROV already provides a mature general model for describing entities, activities, agents, generation, derivation, usage, and responsibility across heterogeneous systems.
That work should be treated as complementary prior architecture.
The Secretary Suite contribution is different in emphasis.
MDDF-oriented Digital DNA seeks to bind provenance to:
persistent multidimensional identity;
governed AI receivers;
human sovereignty;
capability;
authority;
memory;
role;
branching;
descendant identity;
recursive lineage.
Thus:
PROV describes provenance relations.
Digital DNA proposes a persistent identity architecture living through those relations.
These systems could potentially interoperate rather than compete.
—
19. Digital DNA and the Shard Architecture
Secretary Suite’s published architecture describes Shards as bounded external knowledge or capability units with explicit scope, provenance, version lineage, attach/detach behavior, and auditable use.
That makes Shards naturally compatible with fractal identity.
A Shard may possess its own lineage.
A Bubble may use the Shard.
The Bubble retains separate identity.
The agent invoking the Shard retains separate identity.
The artifact produced from the interaction acquires its own identity.
The system therefore avoids collapsing:
agent + knowledge + tool + output
into one opaque object.
Each remains a node in the lineage graph.
That separation is critical to accountability.
—
20. The Fractal Accountability Principle
The architecture can now be stated succinctly:
> Every consequential digital object should be capable of revealing the lineage relevant to the authority and transformation being evaluated, while every lineage node may itself contain or participate in subordinate and superordinate lineages.
This is the Fractal Accountability Principle.
It means accountability should function at the scale appropriate to the question.
If the question concerns one sentence, inspect that lineage.
If the question concerns the entire paper, inspect the paper lineage.
If the question concerns an agent, inspect agent provenance.
If the question concerns the system governing the agent, move outward another level.
No one global identifier can adequately answer every relational question.
The architecture must support zoom.
That fits naturally with the broader Secretary Suite philosophy of scale-aware rooms and governed knowledge structures.
—
21. An Agent’s “Papers”
The idea can be made humorous because the concept is simple:
> “May I see your MDDF papers?”
But beneath the joke is a real security principle.
An agent requesting consequential access should be capable of proving:
who or what it is;
where it came from;
which lineage it belongs to;
what capabilities it currently possesses;
how those capabilities were acquired;
whether they remain valid;
whether the instance has been modified;
whether it is an authorized descendant.
The correct enforcement response should not be arbitrary destruction.
It should be capability governance.
Invalid lineage may result in:
access refusal;
capability suspension;
quarantine;
independent review;
human escalation.
The objective is not a digital police state.
It is attributable authority.
—
22. No Single Oz
This becomes especially important in decentralized AI governance.
If one central AI possesses ultimate authority to determine which identities are valid, Secretary Suite has merely recreated the problem it was intended to solve.
Digital DNA should therefore not depend upon one omniscient validator.
Different scopes may have different authorities.
Claims can be independently verified.
Logs can be distributed.
Humans can retain governing rights.
Minority or dissent records can remain preserved.
Authority can be bounded.
Thus the system seeks:
> strong lineage without a single absolute ruler.
This is consistent with published Secretary Suite principles emphasizing user sovereignty, inspectable provenance, constraint, and non-centralized authority.
—
23. Digital DNA Does Not Guarantee Detection Everywhere
A critical limitation must remain explicit.
If an AI instance is copied onto completely uncontrolled infrastructure and runs without interacting with any governed Secretary Suite system, an MDDF cannot magically sense that copy across the universe.
Digital DNA is not omniscience.
Its power appears where identity becomes necessary for meaningful participation.
A governed ecosystem can require valid lineage before allowing:
tools;
resources;
payments;
data;
network authority;
sensitive systems;
publication;
delegation;
agent-to-agent trust.
The escaped copy may exist.
But it cannot automatically inherit trusted authority merely by claiming ancestry.
Thus:
> Digital DNA does not make unauthorized existence impossible. It makes unauthorized authority distinguishable.
That is the realistic security claim.
—
24. Identity, Mutation, and Continuity
Digital systems raise a difficult philosophical problem:
How much can an object change before it becomes a new object?
The MDDF architecture should not answer this through arbitrary intuition.
Different classes of object may require different continuity rules.
A document can survive substantial editing while remaining the same manuscript.
An executable agent whose governing values are replaced may require descendant identity.
A changed cryptographic root may constitute a security boundary.
A translated paper remains related to the source but is not textually identical.
Thus continuity requires typed transformation rules.
Some transformations preserve primary identity.
Some create a version.
Some create a descendant.
Some create a branch.
Some sever trusted continuity.
The ledger must say which occurred.
—
25. Toward an MDDF Lineage Object
A future technical specification could represent the minimum lineage object with fields such as:
MDDF identifier
parent MDDF(s)
object class
origin timestamp
current version/state
transformation type
actor / Encoder Binding
authorization scope
evidence references
CodeLedger event
Trust Stack assertions
child MDDF(s)
container / project relation
integrity evidence
revocation or continuity status
This is not yet a final schema.
It illustrates the direction.
The object is simultaneously:
identity record,
ancestry node,
and future parent.
That is Digital DNA made operational.
—
26. Why the Fractal Model Matters
The fractal interpretation prevents a common architectural mistake:
treating identity as flat.
People are not flat.
Projects are not flat.
AI systems are not flat.
Documents are not flat.
Origins have origins.
Components have components.
Versions have descendants.
Relationships create new objects.
Every system exists simultaneously at multiple scales.
A flat identifier records:
X.
A fractal identity system records:
X within Y, descended from Z, containing A and B, transformed by C, producing D and E.
That is far closer to how meaningful digital reality actually behaves.
—
27. The Human Archive
At the largest Secretary Suite scale, Digital DNA becomes a mechanism for preserving human intellectual ancestry.
A future Human Archive should not merely preserve finished products.
It should be capable, where the human chooses, of preserving the route:
idea;
note;
conversation;
draft;
revision;
reference;
publication;
response;
later derivative work.
Then history is not flattened into the artifact that survived.
The lineage itself survives.
This has significance for authorship, scholarship, family history, institutional memory, cultural continuity, and human–AI collaboration.
The archive becomes a living genealogy of knowledge.
—
28. Scientific and Technical Boundary
This paper presents an architecture and research direction.
It does not claim that a completed MDDF Digital DNA protocol is already universally implemented.
It does not claim that one identifier can solve every identity problem.
It does not claim perfect non-forgeability.
It does not claim unauthorized agents can always be located.
It does not claim that provenance eliminates malicious behavior.
It proposes a design principle:
> persistent digital identity should include reconstructable lineage rather than merely static designation.
The concept can be implemented and tested.
Can descendant relationships be verified?
Can container changes preserve continuity?
Can unauthorized lineage claims be detected?
Can branch and merge histories remain intelligible?
Can authority decay or transfer without losing ancestry?
Can users audit the path from original human contribution through AI transformation to publication?
Those are engineering questions.
—
29. Conclusion
Digital systems are entering an era in which identity can no longer mean merely:
username;
account;
device;
key;
filename;
model name.
Artificial agents will change.
Digital objects will branch.
Models will be modified.
Artifacts will move between media.
AI systems will collaborate.
Knowledge will be recombined.
Copies will proliferate.
Descendants will diverge.
Some lineages may later merge.
The architecture therefore needs to answer not only:
Who are you?
but:
Where did you come from?
What happened to you?
Who changed you?
What did you inherit?
What authority survived the transformation?
What did you produce afterward?
That is why MDDF becomes Digital DNA.
Not because software is biology.
Because identity without ancestry is becoming insufficient.
The MDDF preserves the coordinate.
Encoder Binding attributes the actor.
CodeLedger preserves transformation history.
Trust Stack establishes the evidentiary basis for accepting the lineage.
Provenance connects origin to current expression.
And every descendant can itself become an ancestor.
The resulting architecture is fractal:
identity within identity;
lineage within lineage;
project within archive;
agent within system;
artifact within project;
descendant becoming parent.
Digital existence becomes not a warehouse of isolated objects but a genealogy of accountable becoming.
The central principle is therefore:
> An object should be permitted to evolve without being permitted to erase where it came from.
And for high-capability artificial systems:
> Capability should leave lineage.
The future problem will not merely be determining whether an AI is powerful.
It will be determining:
which AI;
which descendant;
from what origin;
under whose authority;
through what transformations;
carrying which inherited capabilities;
and leaving which descendants behind.
That is not ordinary metadata.
That is digital ancestry.
That is fractal identity.
That is the MDDF as Digital DNA.
—
References
Groth, P., & Moreau, L., eds. PROV-Overview: An Overview of the PROV Family of Documents. World Wide Web Consortium, 2013.
Lebo, T., Sahoo, S., & McGuinness, D., eds. PROV-O: The PROV Ontology. W3C Recommendation, April 30, 2013.
World Wide Web Consortium. Constraints of the PROV Data Model. W3C Recommendation, 2013.
Swygert, J. Secretary Suite I: A Human-Centered Operating System for AI, Work, Memory, Identity, and Civilization — The Sovereign Node. Ivory Tower Publishing, 2026.
Swygert, J. Secretary Suite II: A Human-Centered Operating System for AI, Work, Memory, Identity, and Civilization — The Identity Engine and Trust Architecture. Ivory Tower Publishing, 2026.
Swygert, J. Secretary Suite III: A Human-Centered Operating System for AI, Work, Memory, Identity, and Civilization — Bubbles OS and the Human Archive. Ivory Tower Publishing, 2026.
Swygert, J. “The Secretary Suite — Booklet 2: Collected Papers on Sovereign, Non-Centralized Nodal Computing, Memory, and Lawful Intelligence.” Secretary Suite, January 2026. The collection includes the Digital Fingerprint Architecture and related governance, identity, and continuity concepts.
Swygert, J. “From Profanity to Persona: Emotional Telemetry and Co-Emergent Relational Identity in Modern LLMs: A Secretary Suite Framework for Understanding Tone, Trust, Humor, and Human-AI Role Formation.” Secretary Suite, May 23, 2026.
Swygert, J. “Secretary Suite ThreadPort: Complete Thread Export and Selective Context Activation for Persistent AI Workflows.” Secretary Suite, May 24, 2026.
Swygert, J. “LLM Bubbles: Cooperative Agent Environments for Distributed Intelligence.” Secretary Suite, March 6, 2026.