Loader Assign Work And Clock Out — Current Source Authority¶
- Status:
CURRENT COMPATIBILITY NAVIGATION - Current authority:
LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_REVALIDATION_2026-08-10.md - Detailed source inputs:
LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.mdLOADER_WORK_ASSIGNMENT_CURRENT_CALLER_AND_GUARD_INVENTORY_2026-08-08.md- Current evidence ledger:
PROGRESS.md - Current operator addendum:
CTC_LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_ADDENDUM.md - Current Wiki addendum:
LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_ADDENDUM.md
This stable path remains for existing consumers.
The reviewed current source contains two distinct representations:
active Route/UI application
= QUEUE_WORK_ASSIGNMENT + COMMODITY_NAME + FINAL_DRAFT
separate typed helper
= ASSIGNMENT_DATA + requestToken + typed locks/guards
The 2026-08-10 revalidation confirms that the relevant Runtime/UI blobs have not changed since the 2026-08-08 source review. The typed terminal/general Clock Out guards still do not prove visibility of route-owned Clock Out rows, and Final Break identity remains divergent.
current source: SOURCE-RECONCILED / DUAL
current DB/runtime/role/provider/Wiki evidence: NOT RUN
canonical target contract: NOT SELECTED
M3: NO
M4: NO
Phase impact: NONE
Use historical rebuild packets only as dated design/evidence input. They do not override the current source successor.
---¶
Source:
docs/reconstruction/LOADER_ASSIGN_WORK_AND_CLOCK_OUT_SOURCE_AUTHORITY.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.