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

Work starts bound to the intent it serves, and a worker resumes knowing whether that intent moved

intent intent-bound-work

How far reality is from it

A task that starts names the work it executes — an issue, an intent, or an exemption the policy declares — and the repository resolves from that, once, which intent and which criteria the task serves; where the policy requires it, a task whose binding is refused does not start. The worker is briefed with what the intent asks of this work, and a handover carries the revision of the intent it was written under, so the next worker is told when the intent, its criteria, its critique or the standing of its evidence changed in between.

plannedstageintent_realization.explain
5/5criteria with current evidenceintent_realization.explain
9units of workintent_realization.explain
5/5
Stage
planned
Verdict
satisfied
Record
.ai/repo/project/intents/intent-bound-work.yaml

Criteria and the evidence behind each

CriterionWhat must be trueEvidenceTestServed byReproduce
binding-is-resolvedWork named by an issue, by an intent or by its paths resolves to the intents and criteria it serves with the revision it was resolved at, and paths that reach more than one intent without naming an issue are refused as ambiguouscurrent · provenapps/majordomus-cli/tests/intent_binding.rsI2000cargo test --test intent_binding
exemption-is-typedWork under no intent proceeds only as derived maintenance or under an exemption class the policy declares, given with a reason; an undeclared class or a missing reason is refusedcurrent · provenapps/majordomus-cli/tests/intent_binding.rsI2000cargo test --test intent_binding
start-is-gatedWhere the policy requires binding, start refuses a task whose binding is refused and records what an accepted one named, and plan start refuses an issue whose binding is refused in both plan engines, through the built executable; where it does not, both behave as beforecurrent · proventest/cases/960_a_task_starts_bound_to_what_it_serves.shI2001 I2004bash test/run.sh 960_a_task_starts_bound_to_what_it_serves
worker-is-briefedThe context of a bound task carries the statement, the invariants, the criteria served with the state of their evidence, and the critique and gap of each intent the task serves, read from the bindingcurrent · proventest/cases/960_a_task_starts_bound_to_what_it_serves.shI2002bash test/run.sh 960_a_task_starts_bound_to_what_it_serves
resume-detects-driftA handover written under a bound task carries the binding's revision, and resolving it says whether the intent, its criteria, its critique or its evidence standing changed sincecurrent · proventest/cases/961_a_resumed_task_is_told_its_intent_moved.shI2003bash test/run.sh 961_a_resumed_task_is_told_its_intent_moved

Milestones realising it

MilestoneStatus
intent-bound-workBLOCKED

Work realising it

KindWorkOutcomeLinkVia issueProvidersHandovers
session_records-20260906035523-7b6cclosedinferredI2000 (scope_overlap), I2001 (scope_overlap), I2003 (scope_overlap)0
session_records-20260906053339-ec22closedinferredI2001 (scope_overlap)3
session_records-20260906054911-cbb8closedinferredI2001 (scope_overlap)1
session_records-20260906055206-8ececlosedinferredI2001 (scope_overlap)1
session_records-20260906104842-c7cfclosedinferredI2000 (scope_overlap), I2001 (scope_overlap), I2003 (scope_overlap)0
session_records-20260909152316-024fclosedinferredI2000 (scope_overlap), I2001 (scope_overlap), I2004 (scope_overlap)0
session_records-20260910205542-e2a6interruptedinferredI2000 (scope_overlap), I2001 (scope_overlap)0
session_records-20260910210510-8f20interruptedinferredI2000 (scope_overlap), I2001 (scope_overlap)0
session_records-20261009091659-3ee5interruptedinferredI2001 (scope_overlap)0

Why it stands where it stands

  • planned: every milestone resolves and none has started (intent-bound-work is BLOCKED)
  • `binding-is-resolved` is met: its test `apps/majordomus-cli/tests/intent_binding.rs` has current evidence; an issue serving it owes evidence before it is DONE (I2000)
  • `exemption-is-typed` is met: its test `apps/majordomus-cli/tests/intent_binding.rs` has current evidence; an issue serving it owes evidence before it is DONE (I2000)
  • `start-is-gated` is met: its test `test/cases/960_a_task_starts_bound_to_what_it_serves.sh` has current evidence; an issue serving it owes evidence before it is DONE (I2001, I2004)
  • `worker-is-briefed` is met: its test `test/cases/960_a_task_starts_bound_to_what_it_serves.sh` has current evidence; an issue serving it owes evidence before it is DONE (I2002)
  • `resume-detects-drift` is met: its test `test/cases/961_a_resumed_task_is_told_its_intent_moved.sh` has current evidence; an issue serving it owes evidence before it is DONE (I2003)
  • 9 unit(s) of work realise it across 5 handover(s)
  • evidence_ahead_of_plan: the verdict is satisfied — every criterion has current evidence — and the stage is planned (intent-bound-work is BLOCKED): the evidence settles the intent before the plan closes it

Findings

evidence_ahead_of_plan — intent-bound-work: the verdict is satisfied — every criterion has current evidence — and the stage is planned (intent-bound-work is BLOCKED): the evidence settles the intent before the plan closes it