Safeguard Work-Order Agent Ecosystem

Routing Policy

← Back to outcome

Routing Policy

The routing policy is business configuration, intentionally expressed as inspectable tables (not a model) so operations can read, audit, and change it. Implemented in src/agents/router.mjs.

Category → queue / crew / base SLA

CategoryQueueCrew typeBase SLA (h)
HVACTRADE_HVACHVAC_TECH24
PLUMBINGTRADE_PLUMBINGPLUMBER24
ELECTRICALTRADE_ELECTRICALELECTRICIAN16
ROOFINGTRADE_ROOFINGROOFER48
LANDSCAPINGTRADE_GROUNDSGROUNDSKEEPER72
SECURITYTRADE_SECURITYSECURITY_TECH12
GENERAL_MAINTENANCEGENERAL_QUEUEHANDYMAN48

Priority → SLA cap

PrioritySLA cap (h)Vendor tierEscalated
P12IN_HOUSE_RAPIDyes
P28IN_HOUSE_RAPIDno
P3— (category base)STANDARD_VENDORno
P4— (category base)STANDARD_VENDORno

Effective SLA = min(priorityCap, categoryBase).

Zone → region

ZonesRegion
N1, N2, N3NORTH
S1, S2, S3SOUTH
E1, E2, E3EAST
W1, W2, W3WEST

Unknown zone → UNASSIGNED (validator routes to human review).

Change process

  1. Edit the table constants in src/agents/router.mjs (ROUTING,

PRIORITY_SLA) and this document together.

  1. Run node verify.mjs — the routing checks must stay green.
  2. Re-run the Proof Layer before any delivery/publication.