The blank and optional capabilities
A common organizational core, specialized behavior and explicit integration boundaries.
The minimum organizational blank
The local blank records purpose and mandate, a manager, on-demand agents, tasks, artifacts, review and acceptance, durable state, owner communication and recovery. Python and SQLite retain organizational records; the authorized AI client performs model work and native delegation.
Implemented mechanisms and their boundaries
| Mechanism | Current scope |
|---|---|
| Task authority | Grants check the common local file API; native tools retain client/OS permissions. |
| Action history | Local task, participant, call and outcome records; reconcile uncertain effects before retry. |
| Audit | Versioned findings and evidence; broader continuous audit is task-dependent. |
| Wake delivery | Stored messages, events and deadlines; optional service launcher. |
| External execution | Requires a connector and reconciliation; a local record does not execute an external action. |
| Outgoing notifications | Optional channels above durable delivery, not built-in universal integrations. |
| Decision quality | Reasons, expectations and outcomes can be recorded; extended analytics is separate work. |
Keep client tools and organization separate
Skills describe procedures; MCP exposes connected tools; native client tools execute within client permissions; the organizational runtime records transitions. Global client configuration, accounts and skills do not automatically enter a downloaded blank. Choose only the integrations needed by the mandate and verify real calls.
Sources & context
Reference edition 0.1 · 2026-10-15. Read the editorial method.