Loader Work Assignment Capability Rebuild Packet — Current Bridge¶
- Status:
CURRENT SOURCE BRIDGE / DUAL CONTRACT / EVIDENCE REQUIRED - Current source baseline:
qa/master@93749d1d583df1b7bfeac48d9174fcf5e1624100 - Process umbrella:
PROC-TMS-INBOUND-PLANNING - Operating profile:
ctc-execution - Phase implementation:
USER HOLD - M3:
NO - M4:
NO
Current Authority¶
Read in this order:
LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.mdLOADER_WORK_ASSIGNMENT_CURRENT_CALLER_AND_GUARD_INVENTORY_2026-08-08.md
Current Source Truth¶
Current repository source contains two materially different representations:
Active Office/Loader Route
= SPECIAL_INSTRUCTION='QUEUE_WORK_ASSIGNMENT'
+ COMMODITY_NAME
+ FINAL_DRAFT
Separate typed helper
= ASSIGNMENT_DATA JSON
+ requestToken
+ advisory lock
+ typed notification/Clock Out metadata
The current Office Assignment Board and Loader page use the Route representation. Selected typed helper locks, guards and active-row readers remain dependencies of current Runtime owners. No direct current Route/UI caller was located for the typed helper's full create/admin/list/Loader/transition command family.
Confirmed Source-Level Divergence¶
Terminal Clock Out visibility
General Staff Time Clock Out protection
Final Break identity and lifecycle
Cancellation spelling
Request idempotency
Notification-attempt persistence
These are confirmed source discrepancies. Current database occurrence, deployed execution, target-role impact, provider behavior and current Wiki content are not established by source inspection.
Historical Detailed Packet¶
The original full packet described the user-approved typed ASSIGNMENT_DATA design before later source introduced the active Route-owned representation.
It is preserved as historical design/evidence at:
Use the historical packet for:
- original business intent;
- typed field/DTO/error design;
- target reconstruction alternatives;
- candidate-specific scenarios.
Do not use it to claim:
- current single-contract persistence;
- current schema population;
- current API/UI ownership;
- current provider recovery;
- M3/M4 readiness.
Reconstruction Rule¶
A future migration packet must begin from the current dual-contract evidence, not from the historical typed design alone.
Required decisions after evidence:
canonical assignment identity
canonical request identity
terminal Clock Out predicate
Final Break authority
cancellation normalization
notification-attempt authority
one-writer and rollback
historical-row compatibility
No source correction or migration is authorized by this bridge.
---¶
Source:
docs/reconstruction/LOADER_ASSIGN_WORK_AND_CLOCK_OUT_CAPABILITY_REBUILD_PACKET.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.