4-Slide Mini Deck · The Persistent Primitive
The Persistent Primitive, in four slides
Micheal Charles Preble · Operant Dyad — Paper 2 · SSRN 7328783
Slide 1 of 4
The Problem
AI systems retaining information about users is usually framed as personalization. That framing does not describe what happens once accumulated relationship state becomes consequential — it exceeds memory retrieval and requires governance.
Slide 2 of 4
The Contribution
Derives ten continuity-governance requirements (R1–R10) from four premises, and argues the natural person — not the provider account or the cryptographic key — should be the primary design locus, because surrounding technical components remain substitutable.
Slide 3 of 4
How It Works · Evidence Status
A “shelf test” convergence review: for each requirement, does credible prior or contemporary work show the mechanism is plausible? Yes at the level of individual mechanisms; no single system integrates all ten.
Evidence status: Requirements framework and convergence analysis; not empirically validated as adopted practice.
Slide 4 of 4
Why It Matters · Limits · Open Questions
A continuity architecture organized around the person, not the account, survives provider substitution without forcing reconstruction from zero.
Limits: does not resolve succession, incapacity, or death. Open: whether the ten requirements are jointly sufficient in a deployed system.
Preble, Micheal Charles. “The Persistent Primitive: Configuring Human-Governed Continuity for Persistent Human–AI Interaction” Available at SSRN 7328783, 2026.