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

I1121

Every surface shows the integration from the one model

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
6
Waiting on
I1112
Holds back
I1122
Behind it in all
2
Evidence
0 of 2
In the waySubjectDetail
issueI1112I1112 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 I1121

majordomus plan verify I1121

majordomus plan done I1121

What it is

Objective
Project the integration state — what is adopted, what is owned, what is generated, what would change — through the CLI, the API and its document, MCP, the Cockpit and the documentation, from the one model and with no parallel definition.
Why
The question a person asks about an integration is what it did to my repository, and they will ask it wherever they happen to be. Answering it four ways is how the four answers begin to differ.
Now
The capability registry already projects declared operations into every surface. The integration state is not among them.
Wanted
One declaration exposes the integration reads, and every surface derives from it as it does for everything else.
Done when
unknown: the record declares no `completion`
Risk
Showing what a reconciliation would change means running the plan on a request. Its cost belongs to the budget, and a read that builds a plan has to say so.

Acceptance

  • The integration reads are declared once and appear in the CLI, the API, the API document, MCP, the Cockpit and the generated reference with no second registration
  • No mutating operation is exposed to an untrusted surface; adoption and removal stay with the trusted command line
  • The Cockpit shows what is adopted, what is owned and what a reconciliation would change, from that declaration
  • The published documentation derives its integration reference from the same model, with no retyped value
Validation
majordomus generate --checkcargo test --workspace --all-features
Evidence required
surfaces_derivedno_mutation_untrusted
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/capability/builtin
Not
A mutating integration operation exposed to unauthenticated HTTP or to a browserA hand-edited API document, route table or documentation list
Depends on
I1112
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-06
Updated
2026-09-06
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.