Authority boundaries are explicit
Agents can recommend work, but new spending, public deployment, sensitive data collection and external actions require human approval.
Depends on: E1-M1
Epic O1
Delegated roles and authority
Agents operate inside explicit roles, permissions, budgets and approval boundaries.
Purpose
The organisation distinguishes proposing work from authorising spending, deployment, data collection or external action.
Current status
Next. The boundaries are clear in the brief and repository instructions; the product charter has not yet been created.
Milestones
Evidence
Cultivate operator brief
Full 20-section assignment preserved locally with SHA256 e8b55ed458e3bc6347735cccee872f59a0bf863b4d1dddb56ba2400b21b2461f.
Delegate AGENTS.md and agent work guide
Private repository instructions were inspected for coordination patterns. The source link and private implementation detail are not published.
Risks and open questions
Risks
- Authority can creep through routine automation.
- Agents can treat a recommendation as approval if rules are vague.
Open questions
- Which decisions can be delegated for the first product experiment?
- How should budget and access refusals be recorded?
Linked Wardley components
- Organisational coordination
- Identity and authority
- Resource accounting
Next steps
- Write the first product organisation charter before commissioning experiments.