Governance
8 personas, domain-scoped workspaces, and Plane as the coordination substrate. Delegation governance is enforced architecturally — at the tool boundary, not in prompts.
The 8 Personas
| Persona | ID | Workspace | Responsibility |
|---|---|---|---|
| Chief of Staff | cos | chief-of-staff | Cross-cutting coordination, family briefs, scheduling, triage |
| Estate Counsel | estate | estate-counsel | Entity graph, trust administration, compliance calendars, succession planning |
| Household Comptroller | hc | household-finance | Budgeting, cash flow, tax planning, financial reporting |
| Household Director | hd | household-ops | Property management, vendor coordination, maintenance schedules |
| Portfolio Manager | io | investment-office | Portfolio construction, risk analysis, rebalancing, performance attribution |
| Research Analyst | ra | investment-office | Investment research, screener tuning, thesis generation, AlphaForge loop |
| Wellness Advisor | wellness | wellness | Health graph, genome-aware insights, appointment coordination |
| Insurance Advisor | insurance | insurance | Policy management, coverage gap analysis, renewal tracking |
Delegation Protocol
Plane as single source of truth
No local delegation edges or approval machinery. Plane work items are the canonical
representation of who owns what. The worker is a thin event router — session persistence,
idempotency, and event routing. All governance logic lives in system prompts and
PLANE_HOME_WORKSPACE validation.
Workspace isolation
7 domain-scoped workspaces. Structural tools (create project, modify cycle) reject cross-workspace writes. Execution tools (update work item status) allow cross-workspace for delegation — you can complete a task assigned to you by another workspace.
Bidirectional delegation
Human → Agent and Agent → Human tasks live in the same backlog. Same sprint cycles, same approval gates. The Plane poller reads parent/child work item hierarchy to detect case completion. HMAC-SHA256 webhook verification for inbound events.
Ontology
Work items follow a two-level hierarchy:
case
Relations between work items: relates_to,
is_blocked_by,
blocks,
is_duplicate_of
— via Plane's issue-relation API.