Infrastructure · Intelligence
Routing
The layer meant to decide what a task requires, so that you describe the work rather than pick the tool. It is built and tested. The source default is off, and a routing decision is not permission to do anything.
Limited foundation Modes public Routing default off
Development status
Two labels, because they answer different questions: maturity says how far it is built, availability says who can reach it. The authoritative, dated record is build status.
Router and Skills
Maturity Limited foundation Orchestration building
Availability Modes public Routing default off
Sixteen work modes are public and you choose them yourself. Separately, a router is built and tested with its own eval set. The source default is off; current production configuration is not asserted on this page.
How it decides
Deterministic rules first, a model classifier only where the rules are inconclusive, its own eval set and telemetry, and every failure path — timeout, invalid output, telemetry error — failing open to the ordinary response path.
It supports three modes:
- Off — the source default. In this mode it changes nothing about a response.
- Shadow — routes and records a decision without applying any Skill.
- Active — may apply only the approved Skills.
The Skills it can apply
Eight Skill descriptors are registered and enabled in the routing registry — construction invoice audit, document evidence analysis, electrical troubleshooting, HVAC diagnostics, financial analysis, investment research, operational exception analysis and operational financial impact — declaring which others they compose with. Three of them, electrical troubleshooting, HVAC diagnostics and construction invoice audit, are currently approved for application when Router mode is active. The other five are registered but not applied in any mode.
The sixteen work modes in the product are separate: you select them yourself. Skills and work modes →
What a routing decision is not
A routing decision says what a task appears to need. It is not permission to do anything. Broader orchestration — several capabilities contributing to one piece of work — is still being built. Model selection and risk scoring are design, not code.
Telemetry keeps the routing decisions, for evaluating the router. The eval sets and harnesses that measure it are internal, run offline and in continuous integration. Agent evaluation →
Recent
Research · — A skill-routing layer, with its own evaluation set. A routing layer landed in the engine together with an eval set for measuring it. Its source default is off, and in that mode it changes nothing about a response. News →