9d24dc5c41
Session 4 step 18 — agent role/reports-to hierarchy with tree/validate/ add/remove/list commands, circular chain detection via python3. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
28 lines
1,006 B
Markdown
28 lines
1,006 B
Markdown
# Organization: {{ORG_NAME}}
|
|
|
|
## Agents
|
|
|
|
| Agent | Role | Reports To | Status | Budget |
|
|
|-------|------|------------|--------|--------|
|
|
| {{AGENT_1}} | {{ROLE_1}} | (board) | active | {{BUDGET_1}} |
|
|
| {{AGENT_2}} | {{ROLE_2}} | {{AGENT_1}} | active | {{BUDGET_2}} |
|
|
| {{AGENT_3}} | {{ROLE_3}} | {{AGENT_1}} | active | {{BUDGET_3}} |
|
|
|
|
## Delegation Rules
|
|
|
|
- Board (human) → top-level agents: task assignment, goal setting
|
|
- Manager agents → direct reports: task decomposition, delegation
|
|
- Cross-team requests: route through common ancestor in org chart
|
|
- Escalation: up the reporting chain to the first agent with authority
|
|
|
|
## Human Override
|
|
|
|
The human operator is the "board of directors" with override authority
|
|
on all decisions. Any agent can be paused, redirected, or terminated
|
|
by the human at any time.
|
|
|
|
## Notes
|
|
|
|
Use `(board)` as the Reports To value for top-level agents that report
|
|
directly to the human operator. All other agents must reference a valid
|
|
agent name in the Reports To column.
|