This is an internal working record, not an everyday instruction. It was written while the system was being rebuilt, for whoever maintains it. If you are here to do today's work, use the everyday documents instead: Procedures · Processes · Runbooks · The working day, step by step
Yard Dispatch, Closing And Driver Parity / Cutover Matrix¶
- Status:
P6/P12 MIGRATION ACCEPTANCE INPUT / NOT ACTIVATED - Source:
YARD_DISPATCH_CLOSING_DRIVER_RECONCILIATION.md - Migration packet:
YARD_DISPATCH_MIGRATION_PACKET.md - Source baseline:
4fc2f5a893765fbb95e0a2bdcb971322b0ec9fc0 - Effect boundary: documentation only
1. Yard Read Parity¶
| Dimension | Required old/new comparison |
|---|---|
| queue identity | same stable queue ID/entity/purpose and no display-text identity |
| active status | Queued/Scheduled/Claimed set and terminal rows |
| source/target | planned source, current physical source and planned target agree |
| actual location | exact spot distinct from Area/Stack instruction |
| assigned/claimed Driver | planned assignee versus active claimant represented separately |
| ordering | same active queue order and tie-break behavior |
| occupied/available/block | same T_YARD_LOCATION result and reason |
| queue-after-clear | same pending origin, blocking location and target |
| delivery correlation | same delivery/equipment/load context without inferred universal link |
| role visibility | Office/Yard Driver/Truck Operator views and expected denials |
| empty/error | no silent empty result or hidden schema/module error |
2. Queue Planning Command Parity¶
Scenarios:
- create one exact move/area/drop/stack instruction;
- update allowed scheduled fields;
- reject duplicate active entity work or return existing logical queue;
- reorder all active items exactly once;
- cancel scheduled work with visible terminal evidence;
- relocate-before-pull-out creation;
- returning-empty reserve/cancel;
- response loss and exact reread;
- foreign tenant and role denial with no mutation;
- server-derived Office capability; request override cannot grant authority.
Every command rereads queue identity, status, order and planned context.
3. Claim / Unclaim Parity¶
| Scenario | Required result |
|---|---|
| intended Yard Driver claims Scheduled item | one Claimed row, actor/time reread |
| another Driver claims concurrently | one winner; conflict/no second active claim |
| Office override claim | explicit capability/reason/audit, selected actor reread |
| wrong source/current location | reject without claim |
| repeated claim by same actor | approved idempotent/no-op or exact conflict contract |
| unclaim | active claim cleared, status Scheduled; planned assignee semantics explicit |
| retained old display name | never interpreted as active claim after unclaim |
| response loss | exact queue reread before repeat |
4. Non-Pull-Out Complete Parity¶
- claimed/authorized actor;
- exact queue/entity/source;
- valid actual target;
- one physical move/vacate;
- original queue becomes Completed;
- Yard location/equipment mirror rereads;
- queue-after-clear auto result, if any, rereads separately;
- operation-event failure does not replay move;
- duplicate/timeout resolves by queue/location reread;
- no second logical movement.
5. Pull Out Closing Parity¶
Required checkpoint evidence:
closing data/ticket identity
queue identity
source/current location
equipment/load identity
actual destination when applicable
closing result
queue completion result
final reconciled disposition
Scenarios:
- closing and queue complete normally;
- closing succeeds, queue fails;
- queue completes, closing result unknown;
- response lost after closing;
- response lost after queue complete;
- duplicate form submit;
- scale-skip allowed and denied;
- wrong bound equipment/container;
- Area/Stack actual spot canceled or invalid;
- role/tenant denial;
- correction after partial result.
No scenario may repeat the closing write before exact closing readback.
6. Queue-After-Clear Parity¶
| Scenario | Required result |
|---|---|
| occupied target creates deferred queue | origin/delivery and waiting queue both reread |
| target clears | exactly one waiting move completes |
| worker/event repeats | idempotent existing completion returned |
| target changes or remains occupied | waiting row stays actionable/blocked, no forced move |
| delivery already complete | no duplicate delivery Finish |
| cancel/correct deferred work | explicit owner and physical verification |
| duplicate Completed rows | one logical move reconciliation and no second physical instruction |
7. Yard Workforce Parity¶
- roster derived from role/capability/config, never personal names;
- intended Yard Driver Clock state;
- 10-minute/Lunch policy and paid/unpaid calculation;
- one local event per command;
- response-loss reread;
- manager/Office action and reason;
- QuickBooks Time success/failure/manual review separately visible;
- no local event replay to retry provider sync.
8. Yard-To-Driver Handoff Parity¶
- exact scheduled Return/Relocate applicability;
- same equipment/load/location identity;
- active Yard queue blocks Start;
- Yard prerequisite completion/readback;
- refreshed Driver card and active Driver Log;
- assigned Truck Operator Start;
- delivery rereads Dispatched;
- no unexplained active queue/occupancy;
- vacate-before-status partial recovery resumes Driver only;
- no universal queue-to-delivery assumption.
Manual dispositions remain projections:
YARD_BLOCKED
READY_FOR_DRIVER
DRIVER_STARTED
PARTIAL_REVIEW
They are not stored target process states unless separately approved.
9. Driver Delivery Parity¶
Identity/list/log¶
- authenticated Driver identity;
- assigned delivery list by default;
- Office-wide view only by capability;
- active Driver Log server enforcement;
- direct caller-selected user/admin values cannot grant access.
Start¶
- intended scheduled assigned delivery;
- active Yard blocker check;
- Yard vacate checkpoint if applicable;
- delivery Dispatched readback;
- response-loss and partial-vacate recovery.
Finish¶
- variant-specific required photo/fields;
- external destination;
- tenant-yard direct empty target;
- occupied target/queue-after-clear;
- parking request/assignment/confirm path;
- delivery and Yard checkpoints separately read;
- no duplicate photo or Yard move after partial failure.
Trouble/Undo¶
- current delivery reset readback;
- equipment/load/Yard/file/provider residuals listed;
- approved compensation only;
- no “full rollback” claim.
10. Provider / Supporting Effect Parity¶
| Effect | Local authority | Required result model |
|---|---|---|
| Yard operation event | queue/location commit | local success + event success/failure |
| Yard Break QBO Time | staff event | local recorded + sync state/manual review |
| Parking Telegram | parking/local state | local checkpoint + notification result; no rollback-by-message unless approved |
| Arrival/location event | delivery/supporting event | separate from delivery completion |
11. Role / Tenant Matrix¶
For each role/profile specify allow/deny for:
- Yard Dispatch view/plan/update/reorder/cancel;
- Yard Instruction view/claim/unclaim/complete;
- Yard Closing;
- Yard Map read/correct;
- Yard Truck Break;
- Driver list/log/fields/Start/Finish;
- parking request/assign/confirm;
- Yard-origin move/vacate;
- provider retry/reconciliation.
Verify menu, page and API together. Expected deny requires no-mutation readback.
12. One-Writer Cutover¶
Every capability cutover records:
old and new owner
cohort/capability selector
single-writer proof
release/schema/config prerequisites
stable input identity
before/after readback
partial-result and rollback path
provider/effect state
caller-zero condition
Recommended order:
read queue/map
-> plan one queue command
-> claim/unclaim
-> non-Pull-Out Complete
-> Pull Out checkpoint/resume
-> queue-after-clear
-> Yard workforce/effects
-> Driver handoff
13. Rollback And Caller-Zero¶
Rollback switches the approved command/UI owner; it does not reverse real physical work.
Reread:
- active/terminal queue;
- Yard occupancy;
- closing data;
- delivery and Driver Log;
- files/photos;
- pending provider/supporting effects.
Before retirement classify all pages, API routes, JS, helpers, cron/timers, tests, Wiki links and approved Runtime traffic as Active/Compatibility/Test/Historical/Unknown/Removed-and-Verified.
---¶
Source:
docs/processes/YARD_DRIVER_PARITY_AND_CUTOVER_MATRIX.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.