I2002 — The context of a bound task says what the intent asks of this work
Add an INTENT section to majordomus context for a task that named an issue or an intent: statement, invariants, the criteria served with the state of their evidence, the critique's open blocking findings and the gap's conditions, each read from intents.binding and bounded by the context budget.
BLOCKED wave 2 · p1 · implementation profile · runs alone
Part of intent-bound-work — A task is bound to the intent it serves.
Blocked. This issue cannot start until I2001, milestone:intent-bound-work are done. The status is derived from that, not declared.
Objective
Add an INTENT section to majordomus context for a task that named an issue or an intent: statement, invariants, the criteria served with the state of their evidence, the critique's open blocking findings and the gap's conditions, each read from intents.binding and bounded by the context budget.
Why
A worker is handed the scope of the task and nothing of what the work is for; the criteria live in a record the briefing never opens.
Current state
majordomus context has no intent section; intent preflight renders the same facts for a reader who asks.
Desired state
The section is present for a bound task, absent with a named reason for an unbound one, and says so when the binding cannot be read.
Scope
- lib/context.sh
- lib/intent_binding.sh
- test/cases/960_a_task_starts_bound_to_what_it_serves.sh
Dependencies
Acceptance criteria
- The context of a bound task names the intent, its statement, its invariants and each served criterion with its evidence state
- The context of an exempt task names the class and the reason
- An unreadable binding is reported as unknown, never as no intent
- The section follows PROFILE, has the JSON section id intent, and under budget loses its gap conditions before anything else and is never dropped whole
Validation
- bash test/run.sh 960_a_task_starts_bound_to_what_it_serves
- bash test/run.sh 23_context
Evidence required
- context_carries_the_intent_section
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2002.yaml. Read it back with majordomus plan show I2002.