Concept Explainer · The Persistent Primitive
The Persistent Primitive, explained
A concise reference for readers who want the core idea without reading the full paper.
What is the Persistent Primitive?
An architectural claim, not a metaphysical or legal one: the element by reference to which continuity has value when the surrounding technical components are substituted. Models can change, providers can fail or merge, applications can be replaced — the natural person remains the enduring referent whose prior commitments, corrections, preferences, and working history give the continuity its purpose.
Why not the provider account, or the cryptographic key?
A provider account is architecturally unstable: it can be suspended, closed, merged, or tied to a product that disappears. A cryptographic key is essential for authentication but is not identical to legal capacity or authority — keys can be rotated, lost, or compromised, and a valid signature proves a key authorized an action, not that the signer had legal authority over every underlying record.
What are the ten continuity-governance requirements?
Visibility and inspectability; provenance and epistemic status; temporal validity and supersession; correction without historical erasure; human authority and consent; purpose and scope limitation; portability and rehydration; interoperability without governance substitution; revocation and boundary control; and protection of human capacity — derived from four premises: persistence, consequentiality, heterogeneity, and a human-governance objective.
What is actually claimed?
- That these ten requirements follow from a small set of premises about consequential persistent state, rather than being an arbitrary feature wishlist.
- That credible prior or contemporary work demonstrates each requirement is technically or institutionally plausible (the “shelf test”) — passing that test does not mean a mature integrated system exists.
- That the natural person should be the primary design locus for the living, capacitated case, specifically.
What remains unproven?
- Whether the ten requirements are jointly sufficient, tested together in a deployed system.
- How often, or how severely, accumulated relationship state actually becomes consequential in practice — the cited studies are small and do not establish prevalence.
- What governs continuity across incapacity, death, or institutional succession — explicitly out of scope.
Where can readers go deeper?
The canonical paper record · Research brief · The continuity-pipeline map · Authority Does Not Travel (Paper 3, picks up where this leaves off) · Human Authority
Preble, Micheal Charles. “The Persistent Primitive: Configuring Human-Governed Continuity for Persistent Human–AI Interaction” Available at SSRN 7328783, 2026.