Skip to content

Post-Baseline Operational Source Delta Register

  • Status: CURRENT SOURCE-DELTA REGISTER
  • Current head at review: qa/master@b09c339ec1a7305554af16bd55bc4be1685719b5
  • Durable rule: DOCUMENT_STATUS_BASELINE_AND_PRECEDENCE_RULES.md
  • Context: Appendix O
  • Purpose: connect accepted Operational Delivery commits to affected Process, Runbook, Wiki and reconstruction packets
  • Does not own: Product decisions, Phase activation, Process lifecycle, Runtime acceptance or Wiki publication

1. Classification

Each source delta is classified by its most consequential impact.

PRESENTATION ONLY
READ MODEL CHANGE
INTERFACE CHANGE
AUTHORIZATION CHANGE
STATE / DATA CHANGE
TRANSACTION / EFFECT CHANGE
PROCESS CHANGE

Disposition:

NO SEMANTIC IMPACT
ADDENDUM SUFFICIENT
FULL REVALIDATION REQUIRED
PACKET REVISION REQUIRED
HISTORICAL PACKAGE RETIREMENT REQUIRED
UNKNOWN

2. Current Delta Summary

Delta ID Commit Operational change Primary families Impact Disposition
DELTA-20260807-001 8e6614514b6e330f7efca60da68a162bb1de50db Empty Return Street Turn modal and current workflow entry Yard/Driver, Booking, Equipment/Container, MK order-first interface/process/UI packet revalidation required
DELTA-20260807-002 31ce25831025f567353a180871b0700ef9b7cb00 Guarded Street Turn revert with selected export load and import-load restoration Yard/Driver, Booking, BMS transaction compatibility, Equipment Load state/transaction/recovery packet revision required
DELTA-20260807-003 ca0d354ac2a4e71f9a070d8a762abbab289bebf1 Current Loader work-assignment queue Inbound/Loader/Workforce, Assign Work/Clock Out state/data/interface/process full revalidation + historical package retirement
DELTA-20260807-004 b09c339ec1a7305554af16bd55bc4be1685719b5 Final Loading Review shipper references and comparison presentation Final Loading Review read model/UI addendum sufficient

The register is not exhaustive history. It begins with commits that landed after the main reconstruction packets were authored and materially affect their status.

3. DELTA-20260807-001 — Empty Return Street Turn

Commit

8e6614514b6e330f7efca60da68a162bb1de50db
feat(tms): add empty return street turn modal

Current result

The Import Dispatch Empty Return Queue gained a bounded Street Turn action that can select an export Booking for compatible empty-return containers.

The current operation crosses these owners:

Import Dispatch / Empty Return source
-> Equipment / Equipment Load
-> Booking selection
-> Street Turn mutation
-> Export Dashboard / Dispatch projection

Affected documentation families

  • Yard Dispatch / Driver handoff;
  • MK Order-First Core Booking and outbound bridge;
  • Equipment/container source authority;
  • Import/Export dispatch Runbook and Wiki;
  • cross-process handoff/identity matrix;
  • migration caller map.

Required packet review

  • current entry and eligible role;
  • exact selected Equipment Load identity;
  • Booking eligibility and expiry;
  • size/shipping-line compatibility;
  • partial multi-container behavior;
  • resulting Equipment/Load state;
  • unknown-result reread;
  • downstream Delivery/Transload blockers;
  • current/future UI entry and support IDs.

Current disposition

SOURCE PRESENT
CURRENT SOURCE-RECONCILED FAMILY PACKETS PREDATE THIS DELTA
REVALIDATION REQUIRED

Do not infer that existing Yard/Booking packets already describe the new action completely.

4. DELTA-20260807-002 — Street Turn Revert Guard

Commit

31ce25831025f567353a180871b0700ef9b7cb00
fix(tms): guard street turn revert

Current source behavior

Current revert now requires both:

EQUIPMENT_ID
EQUIPMENT_LOAD_ID

It checks, among other current predicates:

  • selected load belongs to the equipment and tenant;
  • generated export load is EMPTY and not soft-deleted;
  • equipment Street Turn state is AVAILABLE;
  • equipment has a pickup BOL lineage;
  • selected generated export load has no Delivery or Transload history;
  • an earlier returned import load exists for the same equipment.

Within the current transaction the operation:

soft-deletes selected generated export load
-> clears pickup Booking references and Street Turn state
-> restores immediately preceding returned import load to EMPTY
-> returns both load IDs for sync

Process impact

This is not a generic “revert container” action. It is a bounded compensation for a specific unprogressed Street Turn pairing.

Required semantic name:

RevertStreetTurnPairing

not:

RevertExportContainer

Documentation impact

Review/update:

  • Yard/Driver policy and recovery matrix;
  • Equipment/Container lifecycle;
  • Booking/Outbound bridge;
  • Operational Runbook and errors-recovery projection;
  • state/transaction/compensation diagrams;
  • target semantic command and stable errors.

Remaining unknowns

  • exact target-role evidence;
  • behavior when multiple earlier returned import loads are candidates;
  • durable reason/audit requirement;
  • current field acceptance;
  • whether all callers pass EQUIPMENT_LOAD_ID;
  • support procedure after response loss.

Current disposition

STATE / TRANSACTION / RECOVERY CHANGE
PACKET REVISION REQUIRED
PHASE IMPLEMENTATION HOLD

5. DELTA-20260807-003 — Loader Work Assignment Queue

Commit

ca0d354ac2a4e71f9a070d8a762abbab289bebf1
feat(tms): add loader work assignment queue

Current source result

Current qa/master now contains Office-created non-load work in the existing Loader Planner queue.

Current source markers observed in the commit:

T_LOADING_PLANNER
SPECIAL_INSTRUCTION = QUEUE_WORK_ASSIGNMENT
COMMODITY_NAME = assignment type
FINAL_DRAFT = JSON detail payload
JOB_STATUS = SCHEDULED / STARTED / FINISHED / CANCELLED
LOADER_NAME = one assigned Loader ID string
LOADER_QUEUE_ORDER = shared Loader queue order

Current route family includes:

GET/POST /api/tms/transloads/work-assignments
GET      /api/tms/transloads/work-assignments/current
POST     /api/tms/transloads/work-assignments/{id}/start
POST     /api/tms/transloads/work-assignments/{id}/complete
POST     /api/tms/transloads/work-assignments/{id}/advance-clock-out
POST     /api/tms/transloads/work-assignments/{id}/clock-out

The current Loader endpoint conceals scheduled detail until Start.

Direct divergence from historical approved package

The earlier user-approved implementation package required:

one new nullable T_LOADING_PLANNER.ASSIGNMENT_DATA JSON column
structured assignment data must not use FINAL_DRAFT
request-token idempotency and specified concurrency contract

Current source instead visibly uses:

FINAL_DRAFT JSON
QUEUE_WORK_ASSIGNMENT marker
current route/helper implementation introduced by ca0d354

Therefore:

historical approved decision
!= current implementation detail

This is not resolved by calling both current.

Additional revalidation questions

  • Does current Production schema have ASSIGNMENT_DATA, and is it unused compatibility state?
  • Does current source use a durable request token for create?
  • Does current source provide conditional duplicate handling after response loss?
  • Are Cleaning/Mechanical/Other Work values fully allowlisted server-side?
  • Are all participating Load/Break/Work Start writers serialized consistently?
  • Is Clock Out terminal behavior enforced across all assignment paths?
  • Are Final Break, Staff Time and QuickBooks Time boundaries equivalent to the approved contract?
  • Do Office and Forklift target roles have UI/API parity?
  • What current Wiki content was actually published?

Required documentation corrections

  • rewrite current source authority;
  • rewrite progress/evidence ledger;
  • reclassify old staged plan as historical decision package;
  • retire executable local prompt;
  • update parent coverage matrix;
  • define current-source evidence package;
  • preserve approved business decisions separately from current adapter details.

Current disposition

CURRENT SOURCE PRESENT
APPROVED-CONTRACT / CURRENT-SOURCE DIVERGENCE
FULL REVALIDATION REQUIRED
HISTORICAL EXECUTION PACKAGE RETIREMENT REQUIRED
NO PHASE CORRECTION IMPLEMENTATION WHILE HOLD APPLIES

6. DELTA-20260807-004 — Final Loading Review Reference Refinement

Commit

b09c339ec1a7305554af16bd55bc4be1685719b5
feat(wms): refine final loading review references

Current changes

The queue read model now includes:

T_TRANSLOAD.SHIPPER_QUANTITY
T_TRANSLOAD.SHIPPER_WEIGHT

The current page presentation was refined to show more compact comparison context, including:

  • shipper reference values;
  • revised comparison strip;
  • high-average visual warning;
  • selected-row focus/dimming;
  • refined reference and BAL TRK presentation.

Current semantic disposition

No new persisted review state or review command was identified in this delta.

review state/transaction owner: unchanged
queue read model: changed
visible comparison semantics: changed
operator interpretation: changed

Required documentation updates

  • Final Loading Review Process addendum;
  • operator Runbook comparison explanation;
  • Wiki projection screenshots/status glossary;
  • rebuild read DTO;
  • UI parity/acceptance scenarios;
  • average/high-average policy source and threshold explanation.

Current disposition

READ MODEL / UI DELTA
ADDENDUM SUFFICIENT
RUNTIME / ROLE / FIELD EVIDENCE STILL REQUIRED

7. Cross-Family Freshness Rules

When a later operational commit lands:

  1. register the commit here;
  2. identify source and semantic owners;
  3. classify impact;
  4. update the owning source authority or addendum;
  5. update Runbook/Wiki projection if operator-visible;
  6. update migration assumptions if state/data/interface/effect changed;
  7. keep Phase status unchanged unless the user explicitly reactivates/accepts the Task.

8. Current Safe Actions

While Phase implementation is held:

  • documentation and source reconciliation;
  • current Runbook/Wiki-source updates;
  • bounded Operational Delivery fixes separately requested by the user;
  • future evidence-package definition;
  • no broad structural correction merely because a delta exposed debt.

9. Maintenance Trigger

Update this register whenever a current qa/master commit touches:

  • an owned Process state or command;
  • role/page/API behavior;
  • authoritative data or identity;
  • provider/file/device boundary;
  • current user-visible workflow;
  • migration caller or one-writer assumptions;
  • current source-authority status.

---

Source: docs/reconstruction/POST_BASELINE_OPERATIONAL_SOURCE_DELTA_REGISTER.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.