Add spec-aware orch tasks and verification gates
This commit is contained in:
@@ -51,6 +51,7 @@ Unless a case says otherwise:
|
||||
- `_shared/README.md`: reusable fixtures, JSON assertions, exit-code rules, and worktree conventions
|
||||
- `workflows/README.md`: cross-command end-to-end scenarios
|
||||
- per-command folders: one leaf-command directory per implemented `orch` command surface
|
||||
- `verify/`: verification-gate command cases
|
||||
|
||||
## Glossary
|
||||
|
||||
@@ -60,6 +61,8 @@ Unless a case says otherwise:
|
||||
- `attempt`: one execution try for a task
|
||||
- `dispatch`: the act of materializing a task into an inbox thread
|
||||
- `workspace`: the branch and worktree assigned to a code-writing attempt
|
||||
- `verification gate`: the check aggregation state between worker `done` and final task completion
|
||||
- `verifying`: the task state used while required checks are still pending or being recorded
|
||||
- `blocked task`: a task whose active attempt requires clarification or another external decision
|
||||
- `council review`: a higher-level workflow built on top of `orch` that dispatches fixed reviewer roles and tallies recommendations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user