Codino Consulting: isolated scheduling example
https://codinoconsulting.com/demo/scheduler

All people, buildings, tasks and instructions are fictional. Changes exist only
in the current page. Reload or use Reset example to restore the starting state.
The example does not connect to an operating business, dispatch work or send a
notification. It is a deliberately small illustration, not the complete system.

Start with the Office schedule and Tuesday selected.
1. Edit Urgent service request (DEMO-106). Assign Alex or Blake, then use the
   Move ... up button until it is priority 1. Alex already has work at the same
   fictional North Building; this is context for a decision, not route optimization.
2. Edit Return visit (DEMO-103). Set Work day to Wednesday. Parts still need
   confirmation before travel; moving an assignment does not confirm delivery.
3. Open Technician view. It selects the urgent request's technician on Tuesday.
   Check the priority order, task, promised window and office instructions.

Further exploration: move cards by drag or use their Edit controls; reorder
using labeled up/down buttons; add an optional promised time window; edit the
fictional office instructions. Overlapping windows display a notice. Dana is
unavailable Tuesday. The demo blocks new assignments to Dana that day.

Agents can use the same labeled native buttons, selects and textarea as people.
Initial synthetic state: /demo/scheduler-fixture.json
Current state: use Download your fictional schedule (JSON).
There is no public mutation API or production CLI credential in this example.
Machine-readable case studies: /case-studies.json

Business impact figures have not been established by this demonstration.
Further information: /work/service-scheduling
To discuss a real operating workflow: /apply