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

I1903

The work realising an intent is joined across episodes, providers and handovers

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
intent-lifecycle
Milestone status
PLANNED
Wave
1
Waiting on
I1900
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI1900I1900 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1903

majordomus plan verify I1903

majordomus plan done I1903

What it is

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).
Now
No capability says which task, episode, provider or handover realises an intent; a closed episode forgets its provider; verifying intents are silent.
Wanted
majordomus intent realization and intent explain answer the lineage and the drift on every surface, and the intent-realization gate refuses closed_work_contradicted.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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_realizationbash test/run.sh 388_an_intent_is_realised_across_providers_and_held_to_reality
Evidence required
intent_lineage_joinedclosed_work_contradicted_refused
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/intent_realization.rsapps/majordomus-cli/src/capability/builtin/intent_realization.rslib/session.shtest/cases/388_an_intent_is_realised_across_providers_and_held_to_reality.sh
Not
unknown: the record declares no `non_scope`
Depends on
I1900
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-17
Updated
2026-09-17
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.