Reference architecture
Route, observe, learn
task + required capabilities -> capability registry -> candidate tools and providers -> weighted selection and fallback -> execution result -> structured logs and metrics -> optional learning feedback Supporting surfaces: - FastAPI dashboard and SSE - Prometheus, Grafana and Loki - LanceDB vector similarity - Neo4j task/tool relationships - MCP stdio server with bounded tool surface
Synthetic explanation
Compare routing candidates
This browser-only model demonstrates the decision shape. It does not call a provider, MCP server, learning store or private source system.
Generic candidate names are intentional. Provider model names and prices change faster than this architecture, so the current proof does not make volatile model-ranking claims.
Evidence and limitations
Current reconciliation
| Claim | Evidence | Boundary |
|---|---|---|
| Six core and ten extended modules | Current private source tree and README | Reference implementation, not an active production estate service |
| 951 passing tests | Source README claim | Not re-run in this static refresh; a separate inspection counted roughly 1,038 test functions, which is not the same as a passing-run receipt |
| SPINE integration | SPINE contains an MCPOrchestratorExecutor and fallback path | The backend remains optional; the integration does not make this project SPINE's adopted universal router |
| Provider and MCP routing | Implemented source modules and historical demos | Current proof avoids time-sensitive model rankings |
| Production readiness | Not claimed | No multi-tenant authentication or active service deployment was verified |
Lifecycle framing: this remains valuable as a didactic blueprint and runnable reference. Later estate work has absorbed or superseded parts of its original forward purpose, including SPINE-side integration and separate router products.
Open security follow-up: private issue #21 tracks rotation and removal of provider credentials that prior inspection found committed in configuration history. This documentation refresh does not close that issue and does not expose any credential value.