Loader Assign Work And Clock Out — Legacy Procedure Path¶
Purpose¶
- Status:
SUPERSEDED / PATH RETAINED FOR LINK COMPATIBILITY- Current procedure:CTC_LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_ADDENDUM.md- Current source authority:LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.md- Current evidence ledger:PROGRESS.mdThe previ
Who does this¶
Whoever owns this job.
Before you start¶
- You have the right account (see Permissions and Access).
- The record and date you are working on are correct.
-
Words you do not know are in the Glossary.
-
Status:
SUPERSEDED / PATH RETAINED FOR LINK COMPATIBILITY - Current procedure:
CTC_LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_ADDENDUM.md - Current source authority:
LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.md - Current evidence ledger:
PROGRESS.md
The previous procedure was written around the typed ASSIGNMENT_DATA design. Current source also contains an active route-owned QUEUE_WORK_ASSIGNMENT representation with detail stored in FINAL_DRAFT.
Therefore this path no longer owns current operator instructions.
Use the current addendum for:
- Office create/list/cancel;
- Loader Start/Complete;
- Clock Out safety;
- missing-response recovery;
- queue conflict escalation;
- notification and external-time separation.
The old detailed content remains available in Git history as design and candidate evidence.
current source contract: dual / evidence required
current Wiki: not independently read
Phase implementation: user hold
Do not execute historical Stage instructions or infer current fields from the old filename.
---¶
Source:
docs/runbooks/CTC_ASSIGN_WORK_AND_CLOCK_OUT_FUTURE_OPERATOR_RUNBOOK.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.