Explicit provider selection, policy-bound execution, parallel orchestration, and raw-answer evidence
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
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
Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export