Skip to content

Current Source Contract Correction Addendum — 2026-08-08

1. Supersession Scope

This addendum supersedes only the following stale conclusions in earlier cross-family documentation:

all Phase Transformation Tasks are currently active/in progress
Assign Work/Clock Out current adapter is fully represented by ASSIGNMENT_DATA
historical source/schema readback proves the later current route contract
Loader evidence package needs only field stabilization, not source-contract reconciliation

All other detailed business/platform packets remain useful within their named source baselines and evidence limits.

2. Current Phase Status Correction

The user placed Phase work on hold.

All Phase Transformation implementation
= USER HOLD

Operational Delivery
= may continue when separately requested

Cloud documentation/source reconciliation
= may continue
= no Phase progress

The Roadmap must reflect this current instruction. A historical IN PROGRESS, SPEC READY, candidate branch or detailed prompt does not reactivate a Phase.

3. Current Loader Source Contract Correction

3.1 Current source lineage

Historical accepted scoped implementation lineage:

478cf9f47
ASSIGNMENT_DATA JSON contract
historical source/schema readback recorded at 782ccd00e

Later current operational implementation:

ca0d354ac2a4e71f9a070d8a762abbab289bebf1
feat(tms): add loader work assignment queue

Current qa/master includes both lineages.

3.2 Current active route contract

Current registered route family includes:

POST   /api/tms/transloads/work-assignments
GET    /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
DELETE /api/tms/transloads/work-assignments/{id}
POST   /api/tms/transloads/work-assignments/{id}/advance-clock-out
POST   /api/tms/transloads/work-assignments/{id}/clock-out

The active route implementation stores work in T_LOADING_PLANNER using:

SPECIAL_INSTRUCTION = QUEUE_WORK_ASSIGNMENT
COMMODITY_NAME       = CLEANING / MECHANICAL / OTHER_WORK / CLOCK_OUT
FINAL_DRAFT          = JSON detail
LOADER_NAME          = one Loader ID string
JOB_STATUS           = SCHEDULED / STARTED / FINISHED / CANCELLED
LOADER_QUEUE_ORDER   = shared queue order

3.3 Historical typed helper remains present

Current source also includes assignment_work_helper.php, which uses:

ASSIGNMENT_DATA JSON
requestToken
strict normalized allowlists
per-Loader advisory lock
idempotent existing-result lookup
Telegram attempt state

This helper is included by the active route file, but the active /work-assignments route family does not use the helper's primary create/read contract.

3.4 Shared guard mismatch

A shared terminal Clock Out guard checks:

JSON_EXTRACT(ASSIGNMENT_DATA, '$.type') = 'CLOCK_OUT'

The active later route stores Clock Out type through:

COMMODITY_NAME = 'CLOCK_OUT'
FINAL_DRAFT JSON

Therefore current source contains a dual contract and guard-visibility mismatch.

Correct current classification:

CURRENT SOURCE PRESENT
DUAL PERSISTENCE/HELPER CONTRACT
APPROVED-HISTORICAL-CONTRACT / CURRENT-ACTIVE-ROUTE DIVERGENCE
SOURCE-LEVEL INTEGRITY QUESTION
RUNTIME / ROLE / PROVIDER / WIKI EVIDENCE REQUIRED

This finding does not claim a Production incident without controlled Runtime evidence. It does block describing the active adapter as fully reconciled or M3/M4.

4. Current Loader Evidence Package Correction

The earlier RBR-AWCO-001 package remains useful for historical business/field scenarios, but it is incomplete for the current active adapter.

Current package:

RBR-AWCO-002 — Current Dual-Contract Reconciliation

Required evidence:

Source/schema

  • exact current route/helper caller map;
  • current DB identity;
  • ASSIGNMENT_DATA column and row inventory;
  • QUEUE_WORK_ASSIGNMENT/FINAL_DRAFT row inventory;
  • overlap/mixed rows;
  • current indexes/JSON validity;
  • current transition-audit participation.

Integrity

  • active create duplicate/response-loss behavior;
  • same-Loader concurrent create/start;
  • Load/Break/Work shared queue order;
  • terminal Clock Out visibility across both representations;
  • one active job;
  • cancel/state spelling compatibility;
  • Staff Time event uniqueness and rollback.

Authorization/UI

  • Office/Manager create/list/cancel;
  • Forklift own-record current/start/complete;
  • foreign record denial;
  • detail concealment before Start;
  • current clock-advice tooltip behavior from 4493fb8...;
  • mobile/accessibility.

Provider

  • assignment committed / Telegram failed or unknown;
  • notification retry without assignment duplicate;
  • local Clock Out committed / QuickBooks Time failed;
  • no local/provider replay.

Wiki

  • current rows/rendered pages for inbound-planning, loader-yard, roles, errors-recovery, ctc-daily;
  • removal of historical candidate/pre-release wording;
  • current labels/routes/screenshots;
  • target-role review.

Defining this package does not authorize execution.

5. Historical Loader Documentation Correction

The following retain historical value but do not own current implementation:

docs/operations/2026-08-07-loader-assignment-work-and-clock-out-plan.md
docs/operations/loader-assignment-work-clock-out/00-execution-contract.md
docs/operations/loader-assignment-work-clock-out/01-stage-0-baseline.md
...
docs/operations/loader-assignment-work-clock-out/07-stage-6-verification-handoff.md

Required classification:

HISTORICAL USER DECISION
or
HISTORICAL IMPLEMENTATION PACKAGE

The old local implementation prompt must not be executed against current qa/master.

6. Current Final Loading Review Delta

Current source:

b09c339ec1a7305554af16bd55bc4be1685719b5
feat(wms): refine final loading review references

Changes include:

  • shipper quantity/weight reference;
  • revised comparison layout;
  • average/high-average presentation;
  • selected-row focus/dimming;
  • confirmed/reference presentation changes.

Disposition:

review state/transaction owner: no change identified
read model/UI/operator interpretation: changed

Required current evidence:

  • shipper reference provenance/fallback;
  • inbound/final baseline selection;
  • difference/average formula, UOM and rounding;
  • high-average threshold and warning/blocker meaning;
  • target-role/mobile UI;
  • current Wiki screenshots/content.

7. Current Clock Tooltip Delta

Current source:

4493fb8ece1ff4ee5d4d68a2858880eb42020e82
fix(tms): keep clock advice tooltip visible

The CSS selector now applies the tooltip stacking/overflow fix to any assignment group containing the clock control, not only the idle group.

Disposition:

PRESENTATION / ACCESSIBILITY DELTA
NO PROCESS/STATE CHANGE IDENTIFIED

Current Loader screenshots and mobile/keyboard interaction evidence should use this source.

8. Current Source Head

The current long-lived branch head at this correction is:

ce0a2ab6041ecd378500e3261d11b9561e76ef2b

This includes:

  • cross-family documentation commit 1ec9fbc...;
  • tooltip source commit 4493fb8...;
  • their branch synchronization merge.

Historical documentation baselines remain valid as provenance. They are not current-head proof.

9. Current Readiness Correction

Detailed business/platform packets:
PRESENT

Current source freshness:
MIXED / NAMED DELTAS

Loader current adapter M2:
NOT ESTABLISHED UNTIL DUAL-CONTRACT RECONCILIATION

Accepted M3 families:
NONE ESTABLISHED BY THIS CORRECTION

Accepted M4 families:
NONE

Phase implementation:
USER HOLD

10. Safe Current Action

While the Phase hold applies:

  • update source authority, Runbook and Wiki drafts;
  • preserve historical decisions/evidence;
  • do not run the old implementation prompt;
  • do not delete either Loader representation without schema/caller evidence;
  • do not add a third representation;
  • do not start React/Next.js migration;
  • handle separately requested operational defects through the smallest current owner.

11. Required Current Documentation Owners

  • Roadmap: Phase hold;
  • Loader source authority: current dual contract;
  • Loader progress ledger: current reconciliation/evidence state;
  • Loader Runbook/Wiki projection: current-source draft and publication blockers;
  • Final Review source-delta addendum;
  • cross-family review/coverage: current head and corrected family disposition;
  • evidence register: RBR-AWCO-002 supersedes current-adapter assumptions in RBR-AWCO-001;
  • conflict register: current source/historical contract divergence.

12. Maintenance

Update when:

  • current Loader source/schema changes;
  • current evidence package is executed;
  • the user selects the canonical Loader representation;
  • current Final Review formulas/policies are accepted;
  • current Wiki is reviewed/published;
  • a Phase is explicitly reactivated.

---

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