One active routing authority
Avoid stacking a full meta-router on top of a host that already selects the same skills natively.
These examples and illustrative results are independently authored teaching materials, not measured model results.
Use case
Configure a host with skill-description discovery while considering an always-loaded lifecycle router. Teaching host H has inspectable records selecting review for review requests and implement for feature requests. The extra router covers the same tasks. Verify effective discovery before retaining a second layer.
Mechanism
Inspect host documentation, installed descriptions and selection records. Installation differs from runtime discovery. If native routing covers these tasks, use it as the entrypoint while keeping individual skills available on demand. Add a meta-router where discovery is absent, with a defined scope. Avoid two always-on sources imposing competing flows on the same request.
Bad example
Host H already selects skills as recorded above. Still preload another complete lifecycle router and let both decide review and implementation flows.
Good example
Verify host H's description discovery and both selection records. If native routing covers review/implement, use that entrypoint and load individual skills on demand rather than preloading a duplicate full router. Add a scoped supplemental entrypoint only for missing coverage. Check that each review or implementation request has one effective flow source.
Why the change matters
Duplicate entrypoints consume always-loaded context and can impose different sequences or triggers. Capability verification followed by one scoped authority makes selection inspectable without removing specialist skills.
Observable expectation
Check teaching review and implementation requests against records: they enter review and implement without another same-scope dispatch.
An installation list without selection evidence leaves discovery unverified. Missing native task coverage remains an explicit gap rather than being removed to satisfy a one-router slogan.
Limits
Host capabilities change with version/configuration and need live validation. The method addresses duplicate routing for the same scope, not complementary capabilities or local decisions. Configuration existence alone does not prove selection works.