Research Map · The Persistent Primitive
The human-governed continuity pipeline
This is the paper's own Figure 1, reproduced as a five-step sequence rather than redrawn into a different shape.
The pipeline
- 01Canonical continuity state
The provider-independent representation of consequential relationship state.
- 02Governance / policy boundary
Determines authorized purpose, recipient, scope, temporal validity, and applicable constraints.
- 03Derived authorized view
Contains only the state necessary for the task — not the entire underlying store.
- 04Interoperability / transport
Mechanisms such as A2A carry the authorized view onward, after the governance decision, not instead of it.
- 05Receiving model or agent
Uses only the authorized derived view; the canonical store is never replicated indiscriminately.
Reading the map
Canonical continuity state is not replicated indiscriminately into every consumer. Governance first determines the authorized purpose, recipient, scope, temporal validity, and applicable constraints; only then does the system produce a derived view containing just the state necessary for the task. Transport mechanisms carry that view onward — they do not replace the governance decision.
This pipeline describes structural persistence and governed reuse, not the empirical question of whether a distinct, irreducible relationship-level (“dyadic”) state exists — that question belongs to Operant Dyad and its carrier-localization research, not to this paper.
Citation
Preble, Micheal Charles. “The Persistent Primitive: Configuring Human-Governed Continuity for Persistent Human–AI Interaction” Available at SSRN 7328783, 2026.