I3260 — One intent is carried in a disposable repository from a sentence through a failing criterion to a satisfied verdict, across two providers and a handover

✕BLOCKED wave 3 · p1 · verification profile · parallel safe

Part of the-intent-loop-is-proved-end-to-end — The intent loop is proved end to end, and the plan and the documents say what it does.

Objective

Revive I2545 (origin/chore/seven-owner-packs-are-tracked-and-planned (689021d6ce2, 2026-10-15, never landed)) and extend it: a case creates a fixture repository, proposes an intent from a sentence, drafts and writes its plan (I3252), runs part of the work in one provider session, hands over to a second, sees one criterion fail and the intent stay unsatisfied, drafts the remaining work (I3247), fixes it, and sees the verdict satisfied with the lineage explained, through capabilities only.

Why

The owner's definition of done for IDD v1 (2026-09-16) and the single hard experiment named on 2026-10-08; case 3220 proves the UI loop on one commit, not the failing-criterion replan nor two providers. It also waits on I2812 (case 3220, in the 0.30.0 top, not on master) and I2821 (the opposition revival, local branch, in flight); record them as depends_on once their records land. Sources: chatgpt-majordomus:c129#3, chatgpt-majordomus:c154#37, chatgpt-majordomus:c189#16, chatgpt-majordomus:c196#6, chatgpt-majordomus:c198#11, chatgpt-majordomus:c216#6, chatgpt-majordomus:c221#2, chatgpt-majordomus:c269#5.

Current state

Cases 367, 386, 388, 960, 961 each prove one join; I2812 (case 3220) walks the UI loop in a browser in the 0.30.0 top.

Desired state

One case runs unattended in CI and fails naming the phase that did not happen.

Scope

• .ai/repo/ci/gates.yaml
• docs/PLANNING.md

Dependencies

• I3252✕BLOCKED A draft plan is judged as if it were written, and only a checked draft is written, through one capability
• I3247✕BLOCKED Work is drafted for each criterion nothing serves, under a key derived from the intent, the criterion and the gap, so a second draft drafts the same work
• I3255○READY A command criterion is met only by a recorded passing run of exactly that command at the presented revision

Acceptance criteria

• The case prints admit, draft, execute, handover, fail, replan, fix, satisfied, explained, each with its evidence
• It runs in CI with no manual step

Validation

• majordomus plan validate
• majordomus intent validate

Evidence required

• case_the_loop_is_proved_across_providers

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