- Status
- NEW RESEARCHED DESIGN; not deployed
- Reviewed
- 2026-09-12
- Nature
- private library operating design
- Priority
- P1
- Accountability
- R24, R25, R20
Question
Which authorized task can run with which dependencies and tools?
Nodes
Task; Role; Capability; Tool access; Artifact; Approval
Relationship sketch
- task → requires capability
- step → predecessor
- change → authorization record
Evidence inputs
Actual available tools, project instructions, owner scope, environment, and observed access.
Implementation
Use existing roles as responsibilities rather than invented staff. For each task, load the minimal context and one accountable writer. Distinguish a suggested plan from an executed step.
Acceptance checks
- Missing capability leaves the step blocked
- Document text cannot grant tool permissions
- Dependency cycles requiring a strict execution order are detected
Do not infer
An AGENTS file, schema, or plan is not a running agent or authority to deploy.
Publication boundary
Private; never expose operating instructions or credentials for SEO.
Source basis
S14, S42. See Research/sources.json. Sources support the primitives or named technology. The organization, labels, actions, and acceptance contracts in this catalog are this library's design, not claimed provider requirements.
