Unclassified
12 · Identity & Authority View
IW One Auth — organizational identity, user identity, AI identity, agent identity, roles, authority, tenancy, permissions, approvals, and delegation.
Identity Answers Who Is Acting
Every action in SpineWorkspace is identity-bound. No anonymous Work, no ambient capability access.
IW One Auth
├── Organizational identity (tenant)
├── User identity (human)
├── Twin identity (twin:{userId})
├── Agent identity (agent:{agentId})
└── Roles → Authority → Permissions → Approvals → Delegation
Tenancy is the isolation boundary. Business Context Spine, projections, capabilities, and memory are all tenant-scoped. Cross-tenant access is a governance decision, not a default.
Identity Types
| Identity | Example | Scoped to | Memory it carries |
|---|---|---|---|
| Organization / Tenant | tenant:{orgId} | Organization | Organizational Memory (THE memory) |
| User | user:{userId} | Tenant + roles | Personal Contextual Memory (serves BC) |
| Twin | twin:{userId} | Same tenant as its human | AI Continuity Memory (serves BC) |
| Spine Agent | agent:{agentId} | Tenant + Work + role | Agent Continuity (serves BC) |
Twin identity derives from its human. Agent identity derives from the Work and the organizational role it represents.
Authority vs Permission vs Approval
- Authority — what this identity may do in this Business Context (derived from role + policy + Work context).
- Permission — the enforceable gate that checks authority at capability resolution time.
- Approval — a human or delegated authorization that satisfies a governance policy for a specific plan.
- Delegation — scoped, auditable grant of authority (e.g., "approve renewals under $X in this Work").
Identity → Authority (who/what may act)
→ Capability (what can be done)
→ Policy (under what constraints)
→ Approval (who said yes, with what evidence)
→ Authorization (governance verdict → Hermes may execute)
Tenancy & Isolation
- One Spine per tenant. One projection per participant per Work.
- No capability or memory leaks across tenants. The operational sandbox is per-tenant and per-Work-context.
- Delegation never crosses tenant boundary without explicit governed action.
Where to Go Next
<CardGroup cols={2}>Policy → plan → approval → authorization — the verdict Hermes obeys.
How each identity connects to ecosystems via One Auth scopes.
Secrets, audit, provenance, isolation, fail-closed behavior.