Module routes 

ORCH-15 (observed tier): the routing noun — which profile / agent a surface tuple resolves to.

• Hermes — gateway.profile_routes in HERMES_HOME/config.yaml: a list of {platform, guild_id?, chat_id?, thread_id?, profile} entries, most specific wins (thread 8 > chat 4 > guild 2 > platform 0), the default profile otherwise (docs/HERMES-IDEAL-SUPPORT-DESIGN.md §1).
• OpenClaw — bindings[] in openclaw.json: {agentId, match{channel, accountId, peer{kind,id}, guildId, teamId, roles}}, evaluated exact peer → parent peer → wildcard peer → guild+roles → guild → team → account → channel → default agent (§1b).

Read-only. Editing a route stays the harness’s own config edit.

Structs

RouteMatch

The match side of a route, in the shared-noun vocabulary.

RouteRow

One routing entry.

Enums

RouteError

Why a listing was refused.

Constants

ROUTES_SCHEMA

Wire schema of harness.v1.routes.list.

ROUTE_HARNESSES

Harnesses with a routing concept.

Functions

list_routes

List routes, optionally for one harness and/or one target.