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

The plan of an intent is checked against it before execution, from a recorded gap and a recorded critique

intent intent-planning

How far reality is from it

Before work on an intent starts, a reader can ask which issue carries each of its criteria, why any issue exists, what a worker observed was missing and what an adversarial review of the plan found — and get answers derived from typed records the repository keeps, with the plan refused when a criterion has no work, work has no purpose, a gap leaves a criterion unanswered, or execution began before the plan was critiqued.

plannedstageintent_realization.explain
4/4criteria with current evidenceintent_realization.explain
3units of workintent_realization.explain
4/4
Stage
planned
Verdict
satisfied
Record
.ai/repo/project/intents/intent-planning.yaml

Criteria and the evidence behind each

CriterionWhat must be trueEvidenceTestServed byReproduce
criteria-are-coveredA criterion no live issue serves, unless the recorded gap observed it satisfied, is refused by intent validatecurrent · provenapps/majordomus-cli/tests/intent_plan.rsI1901cargo test --test intent_plan
work-has-a-purposeEvery issue answers why it exists — the intent criteria it serves, or maintenance under no intent — and an issue under an intent that serves nothing is refusedcurrent · provenapps/majordomus-cli/tests/intent_plan.rsI1901cargo test --test intent_plan
gap-is-recordedA gap that leaves a criterion unanswered or asserts a state with no observation is refused through the built executablecurrent · proventest/cases/386_a_plan_is_held_to_its_intent.shI1902bash test/run.sh 386_a_plan_is_held_to_its_intent
critique-precedes-executionWork serving an intent that has started while the intent has no critique, or has an open blocking finding, is refused through the built executablecurrent · proventest/cases/386_a_plan_is_held_to_its_intent.shI1902bash test/run.sh 386_a_plan_is_held_to_its_intent

Milestones realising it

MilestoneStatus
intent-planningBLOCKED

Work realising it

KindWorkOutcomeLinkVia issueProvidersHandovers
session_records-20260906035523-7b6cclosedinferredI1902 (scope_overlap)0
session_records-20260906104842-c7cfclosedinferredI1901 (scope_overlap), I1902 (scope_overlap)0
session_records-20260909152316-024fclosedinferredI1901 (scope_overlap)0

Why it stands where it stands

  • planned: every milestone resolves and none has started (intent-planning is BLOCKED)
  • `criteria-are-covered` is met: its test `apps/majordomus-cli/tests/intent_plan.rs` has current evidence; an issue serving it owes evidence before it is DONE (I1901)
  • `work-has-a-purpose` is met: its test `apps/majordomus-cli/tests/intent_plan.rs` has current evidence; an issue serving it owes evidence before it is DONE (I1901)
  • `gap-is-recorded` is met: its test `test/cases/386_a_plan_is_held_to_its_intent.sh` has current evidence; an issue serving it owes evidence before it is DONE (I1902)
  • `critique-precedes-execution` is met: its test `test/cases/386_a_plan_is_held_to_its_intent.sh` has current evidence; an issue serving it owes evidence before it is DONE (I1902)
  • 3 unit(s) of work realise it across 0 handover(s)
  • evidence_ahead_of_plan: the verdict is satisfied — every criterion has current evidence — and the stage is planned (intent-planning is BLOCKED): the evidence settles the intent before the plan closes it

Findings

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