MCO Runtime Architecture Diagram

Explicit Entrypoints

The npm wrapper launches the same Python runtime used by the console script
CLI and optional MCP tools converge on one invocation workflow
MCO never silently chooses the provider team

Policy Before Process

Repository scope and allow-paths are normalized before dispatch
read_only, write, and yolo map to provider-native permissions
Timeout, cancellation, and partial success stay explicit

Opaque Answers, Durable Evidence

Adapters normalize transport without inventing findings or consensus
Each invocation keeps its raw answer and operational status
Markdown artifacts and JSON metadata remain available to humans and CI