A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
intent-bound-work
A task is bound to the intent it serves
5issuesdevtask.milestone
0readydevtask.milestone
4blockeddevtask.milestone
0activedevtask.milestone
0completedevtask.milestone
The milestone
devtask.milestone- Title
- A task is bound to the intent it serves
- Outcome
- `start` names an issue, an intent or a declared exemption, asks the binding capability what the task serves, and refuses a refused binding where the policy requires binding. The task record carries what was named and the revision it resolved at. `context` briefs the worker from the binding, `handover` pins the revision, and `handover --resolve` reports drift.
- Status
- BLOCKED
- Rank
2- Depends on
- Waiting on
- Holds back
- none
- Record
.ai/repo/project/milestones/intent-bound-work.yaml- Its issues
- Every issue of this milestone
Where the work is
- Ready
- —
- Blocked
- Waiting
- Active
- —
- In review
- —
- Completion blocked
- —
- Complete
- —
- Cancelled
- —
What holds the most back
What may run at the same time
Nothing here can be started now.
Every issue
| Readiness | Status | Issue | Title | Wave | Priority | Waiting on | Holds back |
|---|---|---|---|---|---|---|---|
| waiting | BLOCKED | I2000 | What a piece of work serves is one derivation, with a revision | 0 | p1 | 4 | |
| blocked | BLOCKED | I2001 | start asks what the task serves and refuses a refused binding where the policy requires it | 1 | p1 | 2 | |
| blocked | BLOCKED | I2002 | The context of a bound task says what the intent asks of this work | 2 | p1 | 0 | |
| blocked | BLOCKED | I2003 | A handover pins the binding it was written under, and resolving it reports drift | 2 | p1 | 0 | |
| blocked | BLOCKED | I2004 | plan start refuses an issue whose binding is refused, in both engines | 1 | p1 | 0 |
Findings
Nothing is wrong with these records.