I3275 — An intent's inspector shows the campaign segments it was derived from

✕BLOCKED wave 7 · p3 · implementation profile · parallel safe

Part of intent-intake — A received brief is a campaign revision whose requirements are reconciled into the one plan.

Objective

/ui/intent, /ui/idd, /cockpit's intents panel and intent explain show, for an intent and each issue, the campaign revision and segment references that produced it, drawn through I3283's provenance link as one more reference form of the shared Provenance definition (proposed ADR 0211); the published snapshot shows the references only.

Why

Owner standing order 2026-10-10: track prompt packs and uploads in the UI and milestones. Proposed in ADR 0194 (An ingested brief is an intake revision, and its requirements are reconciled into the existing plan) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c210#2.

Current state

No link from intent to source material beyond prose.

Desired state

The link is the record's own provenance; no separate source field, view or link exists.

Scope

• apps/majordomus-cli/src/ui/intent.rs
• apps/majordomus-cli/src/ui/idd.rs
• apps/majordomus-cli/src/intent_realization.rs
• apps/majordomus-cli/src/capability/builtin/intents.rs
• apps/majordomus-cli/src/commands/intent.rs
• apps/majordomus-cli/src/cockpit/intents.rs
• share/schemas/majordomus/intent
• share/schemas/majordomus/issue
• docs/PLANNING.md

Out of scope

• A separate live stream for reconciliation: sources are re-derived from the records, which the existing channel of ADR 0216 already follows
• The campaign -> record graph edge, which I3168 derives in graph.rs

Dependencies

• I3273✕BLOCKED Each requirement of a campaign revision has a content-derived identity and is reconciled into the existing intents and issues
• I3280○READY An intent, a milestone and an issue carry provenance the way an ADR and a knowledge record do
• I3283✕BLOCKED The UI opens the message a record cites, and the published snapshot shows only the reference
• I3168✕BLOCKED An intent, milestone or issue cites the campaign that drove it, and a campaign answers which records cite it

Acceptance criteria

• An intent written from a draft shows its segments; one with none says none
• A segment source is drawn through I3283's provenance link as one more reference form of the ADR 0211 Provenance definition. No separate source field, view or link is added
• /cockpit's intents panel shows the same sources as /ui/intent and intent explain
• The published snapshot of an intent shows the source references and no brief or message text
• docs/PLANNING.md documents how a campaign's requirements are reconciled into intents and issues

Validation

• majordomus plan validate
• majordomus intent validate

Evidence required

• test_an_intent_shows_its_sources

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