CompositionArchitectural inferencev1.10.0

The Router as an Unacknowledged Policy Engine

Evidence levelArchitectural inference

A router is not a neutral dispatcher when it determines which capabilities and permissions are combined.

Mechanism

The mechanism is interaction. Components exchange context through hidden state, prompts, outputs, adapters, memory retrieval, tool calls, evaluator prompts, and release rules. Each interaction can change what the next component sees and what the system is allowed to do.

Evaluation implication

The evidence record should include the exact composition manifest. A statement such as “Adapter C passed” is incomplete unless it says which base model, load order, router, prompt package, memory snapshot, evaluator, inference configuration, and deployment environment were used.

Practical control

Use composition-aware test suites, targeted higher-order samples, route-level canaries, independent judges, and rollback packets that include all relevant runtime dependencies.

<!-- expanded-release-content -->

The router decides policy in practice

Evidence levelArchitectural inference

A router is not merely a traffic-management tool. It decides which model, adapter stack, prompt policy, memory context, evaluator, or tool path handles a task. Those decisions can determine what capability exists for a user. A capability may be absent from every individual component as tested and present only because the router assembles a path.

Hidden policy effects

A route can concentrate risky tasks in a specialist that was evaluated under narrower assumptions. It can bypass a safety adapter for latency. It can send edge cases to a fallback model with different refusal behavior. It can change behavior through thresholds that are invisible to end users. If the router learns from success metrics, it can also become a selection mechanism.

Documentation requirement

Router governance should include versioned policies, route logs, negative tests, canary paths, fallback review, permission boundaries, and evidence that each high-risk route was evaluated as a composition. A model card without router context is incomplete for routed systems.