I1903 — The work realising an intent is joined across episodes, providers and handovers
Join every ledger task, closed session record and peer claim to the intents it realises with each link's provenance, record each episode's provider on the ledger, explain an intent's standing, and refuse closed work the evidence contradicts.
BLOCKED wave 1 · p1 · implementation profile · parallel safe
Blocked. This issue cannot start until I1900 is done. The status is derived from that, not declared.
Objective
Join every ledger task, closed session record and peer claim to the intents it realises with each link's provenance, record each episode's provider on the ledger, explain an intent's standing, and refuse closed work the evidence contradicts.
Why
An intent's lineage lived in whichever session was working on it, so a handover to another provider lost it, and an intent whose closed work regressed read as finished (ADR 0075).
Current state
No capability says which task, episode, provider or handover realises an intent; a closed episode forgets its provider; verifying intents are silent.
Desired state
majordomus intent realization and intent explain answer the lineage and the drift on every surface, and the intent-realization gate refuses closed_work_contradicted.
Scope
- apps/majordomus-cli/src/intent_realization.rs
- apps/majordomus-cli/src/capability/builtin/intent_realization.rs
- lib/session.sh
- test/cases/388_an_intent_is_realised_across_providers_and_held_to_reality.sh
Dependencies
Acceptance criteria
- One task carried by two providers across a handover is one unit of work linked to the intent, with both providers
- Each link is declared, observed, derived or inferred from one mapping, and the strongest per issue is kept
- An intent whose milestones are all DONE while a criterion's recorded run fails exits 10 naming the criterion, and a repair clears it
Validation
- cargo test --test intent_realization
- bash test/run.sh 388_an_intent_is_realised_across_providers_and_held_to_reality
Evidence required
- intent_lineage_joined
- closed_work_contradicted_refused
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I1903.yaml. Read it back with majordomus plan show I1903.