Five Core Principles
A PSDI-conformant system MUST implement all five core principles. These principles are normative and non-negotiable; partial compliance does not constitute PSDI conformance.
Self Separation
Each self-domain operates independently with its own data, context, and permission scope.
Each self-domain MUST operate as an isolated context space. No self-domain SHALL inherit the authority, context, or data of another self-domain without an explicit, logged permission grant. Isolation MUST be enforced at the data layer, not merely at the interface layer.
Without separation, a compromise or misconfiguration in one self-domain propagates to all others. Separation is the foundational security and coherence property of PSDI.
- The Stoa (professional) self cannot read the Anima (emotional) self's context without explicit delegation.
- A third-party application granted access to Lore cannot access Soma data.
- Shared authentication tokens across self-domains
- Implicit context inheritance between selves
- Single database with no row-level isolation between self-domains
Explicit Permission
Every cross-self interaction requires declared, auditable permission.
All cross-self interactions MUST be preceded by an explicit permission declaration specifying: (a) the requesting self, (b) the target self, (c) the specific data or capability requested, (d) the purpose, and (e) the duration. Permission grants MUST be logged and MUST be revocable by the self owner at any time.
Implicit access creates invisible dependency chains that cannot be audited or revoked. Explicit permission makes the permission graph visible and controllable.
- Lyceum requests read access to Lore's knowledge graph for a specific learning session.
- Stoa requests a one-time summary from Anima to inform a professional communication.
- Ambient access to other self-domains without declaration
- Permanent, irrevocable permission grants
- Permission grants without purpose specification
Continuity of Context
A self retains longitudinal memory within its domain across sessions, channels, and time.
Each self-domain MUST maintain a durable context store with defined retention semantics. Context MUST persist across sessions, channels, and time without degradation. The context store MUST be queryable by the self and MUST support longitudinal reasoning over historical context.
A self that forgets is not a self — it is a stateless service. Continuity of context is what distinguishes a persistent digital self from a general-purpose AI assistant.
- Soma remembers a health concern mentioned six months ago and surfaces it when relevant.
- Lore maintains a knowledge graph that grows over years, not sessions.
- Session-scoped context with no persistence
- Context stores with aggressive automatic deletion
- No mechanism for longitudinal reasoning over historical context
Crisis Handoff Standard
When a self cannot respond, control transfers to a designated fallback according to a declared protocol.
Every self-domain MUST declare a crisis handoff protocol specifying: (a) the conditions under which handoff is triggered, (b) the designated fallback self or operator, (c) the data transferred during handoff, and (d) the procedure for resuming normal operation. Silent failure is not acceptable. Handoff events MUST be logged.
Digital selves will inevitably encounter conditions they cannot handle — technical failures, out-of-scope requests, or operator unavailability. A declared handoff protocol ensures continuity and prevents silent degradation.
- When Soma cannot process a medical query, it hands off to a designated human operator.
- When Dimora's home automation self loses connectivity, it activates a safe-mode fallback.
- No documented crisis handoff protocol
- Silent failure with no notification to the self owner
- Handoff to an undeclared or untested fallback
Embodiment Readiness
A PSDI-compliant self must be capable of operating in physical contexts without architectural change.
Every self-domain MUST implement a channel-agnostic context model. The self's core logic and context store MUST be accessible via voice, robotics, and ambient computing interfaces without requiring architectural modification. Implementations MUST document their embodiment interface specification.
The physical-digital boundary is dissolving. A PSDI implementation that is screen-only is not future-proof. Embodiment readiness ensures that personal digital infrastructure can follow the individual into physical space.
- Soma's context is accessible to a voice interface without data migration.
- Dimora's home self can operate via ambient sensors without a screen.
- Context models that assume a screen-based interaction paradigm
- Hard-coded UI assumptions in the self's core logic
- No documented embodiment interface specification
Use the PSDI Compliance Self-Assessment to evaluate your implementation against these principles. For the full normative specification, see PSDI Spec v1.0.