45 lines
973 B
Markdown
45 lines
973 B
Markdown
# Tasks
|
|
|
|
Tasks are the handoff contract between agents. They are not a real-time queue; sync scripts move them between PC and VPS through Git.
|
|
|
|
## Status Values
|
|
|
|
- `draft`: Created but not ready to claim.
|
|
- `ready`: Ready for the assigned role.
|
|
- `claimed`: Agent has started the task.
|
|
- `blocked`: Agent cannot proceed and wrote the blocker.
|
|
- `done`: Executor has completed the task and produced evidence.
|
|
- `accepted`: Verifier or ORCHESTRATOR accepted the task.
|
|
|
|
## Ownership
|
|
|
|
- ORCHESTRATOR creates and updates task intent.
|
|
- Executors update only tasks assigned to their role.
|
|
- Verifiers update verification tasks and may mark executor tasks accepted after review.
|
|
- CORRECTION may mark a task blocked if it detects drift or unsafe execution.
|
|
|
|
## File Naming
|
|
|
|
Use:
|
|
|
|
```text
|
|
T<ID>-short-topic.md
|
|
```
|
|
|
|
Example:
|
|
|
|
```text
|
|
T3-PC-baseline.md
|
|
```
|
|
|
|
## Required Fields
|
|
|
|
Each task should include:
|
|
|
|
- Status
|
|
- Owner
|
|
- Dependencies
|
|
- Scope
|
|
- Required evidence
|
|
- Stop conditions
|