Skip to content

CTC Yard, Driver And Handoff Contract Reconciliation Baseline

  • Evidence date: 2026-07-17
  • Evidence class: source-reconciled current-state baseline
  • Scope: Client 1 (ctc-execution); no runtime, DB, browser mutation or deployment evidence

Canonical Owners

YARD_DISPATCH_WORKFLOW.md owns Yard queue, movement and closing behavior. DRIVER_DELIVERY_WORKFLOW.md owns Driver Log, delivery, photo, arrival/location and parking behavior. YARD_DISPATCH_TO_DRIVER_HANDOFF_WORKFLOW.md owns only the conditional cross-process checkpoint; ctc-daily, yard-dispatch and driver-delivery are the operator procedures in Local and Production Wiki.

Reconciled Current Boundaries

  • Yard completion verifies the applicable queue/location result; it never by itself completes a delivery.
  • A default-yard RETURN/RELOCATE Driver Start is eligible only after the correlated active Yard queue is gone and physical state is reread. It is not a universal queue-to-delivery transition.
  • Driver Start and Yard movement have independent request/commit boundaries. On uncertainty, reread delivery, queue and Yard location; continue only the missing boundary.
  • DELIVERED with an active queue-after-clear is a pending Yard follow-up, not grounds to undo delivery. Parking confirmation and delivery completion are likewise independent results.

Source-Reconciled Gaps

  • Yard Closing can save scale/closing data before queue completion; a blind retry can duplicate scale data.
  • Yard completion can leave duplicate Completed evidence; this is not proof of a second physical move.
  • Yard and Driver have no shared lock, durable queue-to-delivery correlation or proven command-role/assigned-row enforcement.
  • Driver Start can vacate Yard before its status update; delivered Undo does not compensate every Yard/equipment/load effect.
  • Photo registration and provider notification are separate from authoritative delivery/Yard state and must not be replayed from a success message alone.

Limits

This baseline preserves the WP03-07 through WP03-09 source findings only. It does not approve the draft process lifecycle, repair the gaps, or prove field UAT, concurrent-write behavior, role enforcement, provider delivery or Production state.

---

Source: docs/research/processes/2026-07-17/CTC_YARD_DRIVER_CONTRACT_RECONCILIATION_BASELINE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.