M3a: Freeze REST and MCP machine-interface contracts #45

New issue

Closed

opened 2026-09-06 23:00:05 +00:00 by kilo · 0 comments

kilo commented

2026-09-06 23:00:05 +00:00

Member

Goal

Freeze the REST and MCP interface contracts for Scarcity Router before
implementing either transport.

Why

CLI selection/status semantics are now accepted under M2. M3 adds machine
interfaces, and transport-specific code must not invent or diverge from the
accepted core/application behavior.

Scope

REST endpoint contract
MCP tool contract
shared request/response semantics
error semantics
versioning/compatibility
local service security boundary
interface parity rules
packaging/runtime decision boundary for M3

Acceptance Criteria

canonical REST surface frozen
canonical MCP tool surface frozen
REST and MCP are explicitly thin adapters over the same application/core
no transport-specific selection logic
no-solution vs transport/application failure semantics frozen
local bind/security semantics frozen
JSON/versioning behavior documented
U-008 disposition for M3 explicitly recorded
implementation sequence for M3 frozen
no REST/MCP runtime implemented

Constraints

no product selection semantic changes
no provider changes
no model execution
no prompt proxying
no authentication framework
no dashboard
no M3b implementation in this issue

## Goal Freeze the REST and MCP interface contracts for Scarcity Router before implementing either transport. ## Why CLI selection/status semantics are now accepted under M2. M3 adds machine interfaces, and transport-specific code must not invent or diverge from the accepted core/application behavior. ## Scope - REST endpoint contract - MCP tool contract - shared request/response semantics - error semantics - versioning/compatibility - local service security boundary - interface parity rules - packaging/runtime decision boundary for M3 ## Acceptance Criteria - canonical REST surface frozen - canonical MCP tool surface frozen - REST and MCP are explicitly thin adapters over the same application/core - no transport-specific selection logic - no-solution vs transport/application failure semantics frozen - local bind/security semantics frozen - JSON/versioning behavior documented - U-008 disposition for M3 explicitly recorded - implementation sequence for M3 frozen - no REST/MCP runtime implemented ## Constraints - no product selection semantic changes - no provider changes - no model execution - no prompt proxying - no authentication framework - no dashboard - no M3b implementation in this issue