A gap that leaves a criterion unanswered is refused, and an issue serving an intent that started without a critique or while a blocking finding is open fails intent validation
Planning starts from two records a worker writes: a gap, which answers every criterion of the intent with what was observed at a commit, and a critique, the adversarial pass over the plan with each finding resolved. A gap that skips a criterion is refused. Work under an intent that is ACTIVE, VERIFY or DONE while the intent has no critique is executing_without_critique, and while a blocking finding is open, executing_with_open_blocker.
declared status○declared status: guaranteedDeclared deterministic and blocking, implemented, and naming the behavioural test that is to prove it. Whether a recorded run supports it is the evidence verdict, shown beside it.
recorded evidence!recorded evidence: staleDeclared guaranteed, and not supported by a recorded run: the test is named, and no passing run of the current inputs is recorded. how evidence is recorded
The refusal is `majordomus intent validate` and the intent-check gate, after the start. `plan start` itself succeeds; refusing the start is intent-refused-at-plan-start, which is planned. Majordomus writes neither record. A worker observes and criticises, and the repository refuses what does not hold together.
Planning starts from two records a worker writes: a gap, which answers every criterion of the intent with what was observed at a commit, and a critique, the adversarial pass over the plan with each finding resolved. A gap that skips a criterion is refused. Work under an intent that is ACTIVE, VERIFY or DONE while the intent has no critique is executing_without_critique, and while a blocking finding is open, executing_with_open_blocker.
apps/majordomus-cli/src/intent_review.rs validates both records against the intent and the plan, and the findings join majordomus intent validate, which the intent-check gate runs. The judgment is made after the start: an issue that plan start has already moved is what fails.
plan start does not refuse the start; refusing it there is intent-refused-at-plan-start, which is planned. Majordomus writes neither the gap nor the critique and runs no opposition pass of its own.
What a worker observed and what a review found are lost with the session that produced them unless they are records. Holding started work to them is what makes the review a precondition someone can check rather than a habit.
A gap that leaves a criterion unanswered is refused, and an issue serving an intent that started without a critique or while a blocking finding is open fails intent validation