Specialist assignment panel · Dispatch
Route / Dispatch
Repair work orders, specialist assignments, owner approvals, validation, and closure.
Reason: 2 protected actions held by Guardian.
Active cases
0
Urgent
0
Critical or high
Desk theme
Specialist dispatch desk and repair-routing center
Owner action
Decide 6 Guardian gate(s) waiting on you.
Worker action
No work order is routed to this ward.
Pulse snapshot · portfolio-snapshot · Stale · 2026-08-06 17:30 UTC — 7 patient(s) have no live feed; those rows read Not connected on purpose.
Guardian Blocked2 protected actions held by Guardian.Little Buddy — what happens in Dispatch?
Repair jobs are written here with exactly who does what and where.
Work orders are written here with the exact files a worker may touch.
There is no proof that any worker actually started, because the run feed is not attached.
Authorize a read-only BuildCommand feed to get start proof.
Started
Assignment is not proof of work. With no run feed attached, every order below shows a null start proof.
No work orders at this stage.
Started records for the Route / Dispatch: Repair work orders, specialist assignments, owner approvals, validation, and closure.
Connection state: Stale — read-only snapshot, no live adapter attached.
Owner action: Decide 6 Guardian gate(s) waiting on you.
Worker action: No work order is routed to this ward.
Blocks progress: Yes — a Guardian hold is open.
Pulse snapshot · portfolio-snapshot · Stale · 2026-08-06 17:30 UTC — 7 patient(s) have no live feed; those rows read Not connected on purpose.
Read-only view. Pulse never publishes, deploys, migrates or clears a Guardian gate.