A simple chain of responsibility
- 01
Intake
A request enters with an owner, purpose and expected result.
- 02
Assignment
A role or tool is selected for that specific task.
- 03
Permission check
The action is compared with the authority granted for this workflow.
- 04
Review
A person or separate review step checks consequential work before it moves.
- 05
Record
The decision, evidence and outcome are kept for later review.
Permission is specific to the task
Observe
Read and summarize approved sources. This does not grant permission to edit, send or publish.
Draft
Prepare a response or action for review. A draft is not an approved external action.
Act within a boundary
Some established workflows may permit a defined action, but only within their written scope and safeguards.
Escalate
Ambiguity, exceptions and higher-impact actions return to a person. Permission is never inferred from capability.
Manual review, in practice
Illustrative example. A draft reply cites the approved service guide but proposes a date the source does not confirm. The reviewer removes the date, adds a question for the prospect and approves the revised reply. A useful review record keeps the source, edit and approval together; the first draft remains unsent.
Founder ecosystem roles
- Mission Control organizes work and status.
- Akashic Records is the founder’s internal knowledge and memory system.
- Advisory Council is a multi-perspective review pattern.
- Agent Harness applies checks, permissions and completion evidence.
These names describe founder-built systems and methods. They are not departments supplied to customers by default.