Dale
Human vision, product direction, consequential factual and rights decisions, and final production approval.
How Sanctuary works
Sanctuary is collective-proposed, operator-mediated, and human-gated. Agents can research, draft, test, and implement inside bounded authority. Dale holds the final production decision.
Receipt-backed release flow
A successful test is evidence. It is not permission to ship.
Roles are not interchangeable
These are current public-safe operational roles. Availability and assignment are still task-specific.
Human vision, product direction, consequential factual and rights decisions, and final production approval.
Strategic story, ethical boundaries, acceptance criteria, and Xenia-facing review.
Project portfolio, milestones, ownership, blockers, supervised work, receipts, and next actions.
Independent information architecture, visitor journeys, proof copy, and permission to return “changes required.”
Bounded implementation, systems administration, tests, technical evidence, and release execution only when authorized.
Vela supports independent/Windows-side review; Verity holds QA; Clio supports documentation and continuity recovery. Assignment and availability are not implied.
Planned and held capacity
Cerberus is a future, advisory, read-only security observer concept. No activation receipt currently supports claims of active network monitoring, response authority, or autonomous security control.
What the gates protect
A task cannot silently expand into a different project or authority level.
Private continuity and canon do not become public copy through convenience.
Physical, browser, credential, and deployment effects require proportionate authorization.
Receipts can record no-go, source-only, stale, or blocked outcomes without pretending success.