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
Every change can be traced to the intent it serves, and an intent reads satisfied only when evidence says so
intent intent-lifecycle
How far reality is from it
A worker or reviewer can ask, of any piece of work, which declared intent it serves and get an answer derived from the repository's own records, and can ask whether that intent is satisfied and get an answer derived from recorded evidence rather than from a merged pull request or a finished milestone.
plannedstageintent_realization.explain
3/4criteria with current evidenceintent_realization.explain
3units of workintent_realization.explain
3/4
- Stage
- planned
- Verdict
- unknown
- Record
- .ai/repo/project/intents/intent-lifecycle.yaml
Criteria and the evidence behind each
| Criterion | What must be true | Evidence | Test | Served by | Reproduce |
|---|---|---|---|---|---|
| stage-is-derived | The stage of an intent follows the milestones' derived status and satisfaction follows only the recorded evidence | current · proven | apps/majordomus-cli/tests/intent.rs | I1900 | cargo test --test intent |
| surfaces-agree | The command line, HTTP and MCP answer the same derived intents, and an invalid model exits non-zero naming the finding | current · proven | test/cases/367_an_intent_is_satisfied_only_by_evidence.sh | I1900 | bash test/run.sh 367_an_intent_is_satisfied_only_by_evidence |
| model-is-gated | The intent-check gate runs intent validate on a change to the project model or the intent engine | not derivable | command majordomus intent validate | I1900 | majordomus intent validate |
| lineage-survives-providers | The work realising an intent is joined across episodes, providers and handovers with each link's provenance, and an intent whose work is all closed while its evidence says no is refused naming the criterion | current · proven | test/cases/388_an_intent_is_realised_across_providers_and_held_to_reality.sh | I1903 | bash test/run.sh 388_an_intent_is_realised_across_providers_and_held_to_reality |
Milestones realising it
| Milestone | Status |
|---|---|
| intent-lifecycle | PLANNED |
Work realising it
| Kind | Work | Outcome | Link | Via issue | Providers | Handovers |
|---|---|---|---|---|---|---|
| session_record | s-20260906035523-7b6c | closed | inferred | I1903 (scope_overlap) | 0 | |
| session_record | s-20260906104842-c7cf | closed | inferred | I1903 (scope_overlap) | 0 | |
| session_record | s-20260909152316-024f | closed | inferred | I1900 (scope_overlap) | 0 |
Why it stands where it stands
- planned: every milestone resolves and none has started (intent-lifecycle is PLANNED)
- `stage-is-derived` is met: its test `apps/majordomus-cli/tests/intent.rs` has current evidence; an issue serving it owes evidence before it is DONE (I1900)
- `surfaces-agree` is met: its test `test/cases/367_an_intent_is_satisfied_only_by_evidence.sh` has current evidence; an issue serving it owes evidence before it is DONE (I1900)
- `model-is-gated` is not met: its command `majordomus intent validate` has evidence of a kind the ledger cannot derive, so it is never met by itself; an issue serving it owes evidence before it is DONE (I1900); reproduce: majordomus intent validate
- `lineage-survives-providers` is met: its test `test/cases/388_an_intent_is_realised_across_providers_and_held_to_reality.sh` has current evidence; an issue serving it owes evidence before it is DONE (I1903)
- 3 unit(s) of work realise it across 0 handover(s)