Skip to content
Cockpit0.29.0
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

I2002

The context of a bound task says what the intent asks of this work

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
intent-bound-work
Milestone status
BLOCKED
Wave
2
Waiting on
I2001milestone:intent-bound-work
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI2001I2001 is not DONE
milestoneintent-bound-workthe milestone intent-bound-work waits on an outcome of its own

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2002

majordomus plan verify I2002

majordomus plan done I2002

What it is

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.
Now
majordomus context has no intent section; intent preflight renders the same facts for a reader who asks.
Wanted
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.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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_servesbash test/run.sh 23_context
Evidence required
context_carries_the_intent_section
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
lib/context.shlib/intent_binding.shtest/cases/960_a_task_starts_bound_to_what_it_serves.sh
Not
unknown: the record declares no `non_scope`
Depends on
I2001
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-07
Updated
2026-10-07
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.