feat: a workflow-planning surface that maps an intent to the call sequence #845

New issue

Open

opened 2026-10-20 16:50:56 +00:00 by hexajon · 0 comments

hexajon commented

2026-10-20 16:50:56 +00:00

Owner

What happens

Assembling a multi-step task still costs per-step discovery. "Attach a remote to an existing repo" is one intent, but a caller finds and orders several calls by trial. #747 attacks this by making each first call succeed. A planning surface attacks the other half: when a task genuinely needs several ordered calls, name them up front.

Proposal

Expose a planning surface on the MCP layer: given a stated intent, it returns the exact ordered call sequence. The caller states the intent and gets the steps, instead of discovering them one failed call at a time. This complements #747 rather than replacing it. #747 removes the single-call friction; this removes the multi-call assembly friction.

Acceptance criteria

A planning surface on the MCP layer takes a stated intent and returns the ordered call sequence for it.
The "attach a remote to an existing repo" intent returns a correct, runnable sequence.
The surface reads the operation registry (ADR 0008), so it cannot drift from the live actions.

#747 (make the first call succeed), ADR 0001 (conventions live in the MCP layer), ADR 0008 (the operation registry is the source such a surface would read).

## What happens Assembling a multi-step task still costs per-step discovery. "Attach a remote to an existing repo" is one intent, but a caller finds and orders several calls by trial. #747 attacks this by making each first call succeed. A planning surface attacks the other half: when a task genuinely needs several ordered calls, name them up front. ## Proposal Expose a planning surface on the MCP layer: given a stated intent, it returns the exact ordered call sequence. The caller states the intent and gets the steps, instead of discovering them one failed call at a time. This complements #747 rather than replacing it. #747 removes the single-call friction; this removes the multi-call assembly friction. ## Acceptance criteria - A planning surface on the MCP layer takes a stated intent and returns the ordered call sequence for it. - The "attach a remote to an existing repo" intent returns a correct, runnable sequence. - The surface reads the operation registry (ADR 0008), so it cannot drift from the live actions. ## Related - #747 (make the first call succeed), ADR 0001 (conventions live in the MCP layer), ADR 0008 (the operation registry is the source such a surface would read).

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sixfold-space/madtea#845

No description provided.

Rows
Columns