Skip to content

I1121 — Every surface shows the integration from the one model

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.

BLOCKED wave 6 · p1 · implementation profile · parallel safe

Part of two-folder-integration — A repository that adopts Majordomus gains two directories and two lines, and can give them back.

Blocked. This issue cannot start until I1112 is done. The status is derived from that, not declared.

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.

Current state

The capability registry already projects declared operations into every surface. The integration state is not among them.

Desired state

One declaration exposes the integration reads, and every surface derives from it as it does for everything else.

Scope

  • apps/majordomus-cli/src/capability/builtin

Out of scope

  • A mutating integration operation exposed to unauthenticated HTTP or to a browser
  • A hand-edited API document, route table or documentation list

Dependencies

What waits on this

Acceptance criteria

  • 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 --check
  • cargo test --workspace --all-features

Evidence required

  • surfaces_derived
  • no_mutation_untrusted

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

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/I1121.yaml. Read it back with majordomus plan show I1121.