Reported by: codex
Priority: P1
Affected surfaces: MCP tool surface, runtime capability coverage, documentation and authoring alignment
Risks if postponed: agents and documentation drift away from the actual runtime, leading to invalid workflow generation and misleading guidance
Summary
Reduce the structural drift risk between the MCP server surface and the underlying runtime capabilities so agent-generated workflows stay valid and aligned with what the product actually supports.
Current pain
The roadmap already treats MCP alignment as ongoing investment, which implies a real maintenance burden. When the MCP surface, documentation, and runtime evolve at different speeds, generated workflows and authoring guidance become less trustworthy.
Why now
This repository already positions AI-assisted workflow authoring as a first-class differentiator. That only works if the MCP and runtime remain tightly aligned as capabilities change.
Target improvement
Create a tighter operating path so runtime changes, MCP exposure, and authoring/documentation expectations stay synchronized with less manual drift.
Non-goals
This item should not expand into a full product redesign or a dashboard initiative.
Validation notes
We should be able to verify alignment through runtime-to-MCP capability checks, improved authoring confidence, and reduced cases where documented or generated workflows rely on unsupported behavior.
Notes
- Source: local roadmap at
.doc/positioning-and-roadmap.md.
- This issue was created while migrating local backlog ownership to GitHub.
Reported by: codex
Priority: P1
Affected surfaces: MCP tool surface, runtime capability coverage, documentation and authoring alignment
Risks if postponed: agents and documentation drift away from the actual runtime, leading to invalid workflow generation and misleading guidance
Summary
Reduce the structural drift risk between the MCP server surface and the underlying runtime capabilities so agent-generated workflows stay valid and aligned with what the product actually supports.
Current pain
The roadmap already treats MCP alignment as ongoing investment, which implies a real maintenance burden. When the MCP surface, documentation, and runtime evolve at different speeds, generated workflows and authoring guidance become less trustworthy.
Why now
This repository already positions AI-assisted workflow authoring as a first-class differentiator. That only works if the MCP and runtime remain tightly aligned as capabilities change.
Target improvement
Create a tighter operating path so runtime changes, MCP exposure, and authoring/documentation expectations stay synchronized with less manual drift.
Non-goals
This item should not expand into a full product redesign or a dashboard initiative.
Validation notes
We should be able to verify alignment through runtime-to-MCP capability checks, improved authoring confidence, and reduced cases where documented or generated workflows rely on unsupported behavior.
Notes
.doc/positioning-and-roadmap.md.