Every persisted founder/operator action must include a verified actor identity.
Never persist real control actions from anonymous or unknown actors.TheoB should never trust a control action from a ghost.
An identity readiness layer that defines actor identity, role authority, session integrity, consent capture, delegation boundaries, and MFA requirements before real audit persistence is allowed.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
No ghost operators. No anonymous authority.
Authenticated Founder Identity Readiness Layer defines the identity rules that must exist before any real founder action, audit receipt, or persistence event can be trusted. Until actor identity, role authority, consent, session safety, and delegation boundaries are ready, persistence remains blocked.
Founder identity is intentionally not ready until authenticated actor, role classification, founder authority, session integrity, consent capture, MFA boundaries, delegation, and identity provider selection are finalized.
Each actor must have a role such as founder, operator, reviewer, system, or observer.
Permissions must come from role boundaries, not vibes.Founder-level actions must prove the actor has founder authority before confirmation.
Do not allow non-founder roles to authorize safe mode, autonomy pause, or persistence activation.Persisted actions must include a safe session reference without exposing cookies or tokens.
Use redacted session IDs or hashes only. Never store raw session secrets.Critical persisted actions must record explicit human confirmation.
No inferred consent for critical control actions.Identity records must avoid storing sensitive raw identity payloads.
Persist actor IDs, roles, and safe labels only; avoid raw auth payloads.Each audit record must bind actor identity to receipt ID, action, timestamp, and mutation status.
No orphaned receipts without accountable actor linkage.Critical actions should require stronger verification before persistence or execution.
Safe mode activation, autonomy pause, or real persistence activation should require elevated confirmation.If operators are allowed, their scope must be explicit and revocable.
Delegated users cannot silently inherit founder authority.Choose the identity source later: Vercel auth, Clerk, Auth.js, Google OAuth, custom admin auth, or another provider.
Do not attach real identity until roles, redaction, and audit linkage are defined.