Routing Architecture

Hordago routes user intent to specialized engines. It does not become the domain engine itself; it selects, governs, and hands off to the right lane.

Routing Layers

Layer	Examples
Tier 1 core	Hordago routing, compatibility, HITL gates.
Tier 2a MCP	biocontext7 and other remote tool catalogs.
Tier 2b engines	co-scientist, evidence-audit, dataviz, statistics.
Tier 2c DomainOS	CRISPRos, GWASos, BIOos, MLos, and scaffolded specialists.

The router keeps intent classification deterministic enough for tests and drift checks to compare code-visible routes against documentation.

The Tier 2a MCP catalog is anchored by BioContext7. See the BioContext7 flagship landing for the bundle registry and the integration map for bundle-to-lane wiring.