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
I1902
The gap and the critique of an intent are typed records the plan is held to
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
2- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1901 | I1901 is not DONE |
| milestone | intent-planning | the milestone intent-planning waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Add the gap and critique kinds, their schemas, and intent_review::review, so intent validate refuses an incomplete gap and execution on an uncritiqued plan.
- Why
- What a worker observed was missing and what a review of the plan overlooked lived only in a session's scroll, so planning started from a prompt and a missed requirement surfaced after the work.
- Now
- No gap or critique record exists.
- Wanted
- A gap answers every criterion with observations; a critique's findings are resolved open, planned into an issue serving the intent, or rejected with a reason; started work on an uncritiqued plan or with an open blocker is refused.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A gap leaving a criterion unanswered fails intent validate as gap_criterion_unanswered
- A condition asserted with no observation fails as condition_without_observation
- Started work on an intent with no critique fails as executing_without_critique, and with an open blocking finding as executing_with_open_blocker
- Validation
cargo test --lib intent_reviewbash test/run.sh 386_a_plan_is_held_to_its_intent- Evidence required
an_incomplete_gap_is_refusedexecution_waits_for_the_critique- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/intent_review.rsshare/schemas/majordomus/gapshare/schemas/majordomus/critiqueshare/kinds.yaml.ai/repo/knowledge/sources.yamlshare/skeleton/ai/repo/knowledge/sources.yamltest/cases/386_a_plan_is_held_to_its_intent.sh- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-15
- Updated
- 2026-09-15
- 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.