Skip to content

This is an internal working record, not an everyday instruction. It was written while the system was being rebuilt, for whoever maintains it. If you are here to do today's work, use the everyday documents instead: Procedures · Processes · Runbooks · The working day, step by step

CTC Loader Work Assignment — Current Source Addendum

  • Status: CURRENT SOURCE-RECONCILED OPERATOR ADDENDUM / FIELD EVIDENCE REQUIRED
  • Current source authority: LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.md
  • Parent procedure: CTC_INBOUND_ASSIGNMENT_LOADER_WORKFORCE_RUNBOOK.md
  • Legacy detailed procedure: CTC_ASSIGN_WORK_AND_CLOCK_OUT_FUTURE_OPERATOR_RUNBOOK.md — historical design and partial procedure input; current source authority controls conflicts
  • Evidence: RBR-AWCO-002

1. Current Safety Position

Current source contains active Work Assignment routes plus a separate typed helper representation. Until current callers and rows are verified, operators and support must use the visible current UI and authoritative queue readback rather than assuming all older typed-helper guarantees are active.

current visible assignment
+ current queue readback
+ current Staff Time readback
= operator basis

Do not use old implementation-stage instructions to create or repair current rows.

2. Office — Create Work Assignment

  1. Verify the intended Loader is currently working.
  2. Verify Current and Next queue state.
  3. Verify no active Clock Out assignment is already visible.
  4. Select Cleaning, Mechanical, Other Work, or Clock Out.
  5. Complete the current fields shown by the page.
  6. Submit once.
  7. Review the result per Loader.
  8. Refresh the Office assignment list and Loader queue.
  9. Verify the new row appears once with the intended type/status/order.
assignment created
!= Telegram delivered

If Telegram fails, recover the notification on the existing assignment. Do not create another assignment.

3. Missing Create Response

Do not submit again immediately.

Reread:

Office assignment list
Loader Current/Next queue
current Staff Time state
active Clock Out state
  • one matching assignment exists: treat create as committed;
  • no matching assignment and queue unchanged: controlled retry may be possible;
  • multiple/mixed/ambiguous rows: stop and escalate.

Current active create does not expose a reliable operator request-token lookup in the route contract.

4. Loader — Start And Detail

Before Start, the Loader should see only the current concealed next-assignment presentation supported by the page.

The Loader must not:

  • select another Loader;
  • bypass current queue order;
  • Start during a blocking Break/Clocked-Out condition;
  • rely on Telegram as Start evidence;
  • see protected assignment detail before Start.

After Start:

  1. reread Current Assignment;
  2. verify full detail belongs to the same assignment ID;
  3. verify Staff Time/Job Start evidence;
  4. perform only the displayed assigned work.

5. Complete Work

  1. Confirm the current assignment ID/type.
  2. Complete once.
  3. Reread:
  4. assignment status;
  5. Job End evidence;
  6. Loader Current/Next queue;
  7. Idle/Clock state.

If the response is missing, reread before another Complete. A completed row must not receive another Job End event.

6. Clock Out Assignment

Clock Out remains terminal in the intended Loader queue.

Current support must verify the terminal guard against actual current rows because source representations differ.

Do not add Work or Break behind an active Clock Out merely because one screen does not display the guard.

Required boundaries:

Cleaning Complete != Clocked Out
Final Break Started != Clocked Out
local Clock Out committed != external time service synchronized

Once the queued Clock Out workflow is active, do not use a separate general Clock Out action unless the current page explicitly routes it through the same workflow.

7. Queue Conflict

Examples:

  • Work appears behind Clock Out;
  • two active/current assignments;
  • Current and Office list disagree;
  • typed-helper and route-owned rows display differently;
  • Break can be created after terminal Clock Out;
  • duplicate Start/Complete events.

Procedure:

  1. stop create/start/complete actions;
  2. record exact Loader and planner IDs;
  3. reread Office list, personal Current/Next, Staff Time, and active Break;
  4. do not reorder/delete raw planner rows;
  5. escalate using RBR-AWCO-002 fields.

8. Cancel

Cancel only a current queued assignment through the current UI/action and reread queue order afterward.

Do not use Cancel as:

  • completed-work reversal;
  • Staff Time event deletion;
  • provider-message withdrawal;
  • physical-work rollback.

Current persisted status spelling and consumer normalization require evidence. Use the current UI status rather than editing status text directly.

9. Provider Recovery

Telegram

assignment exists + message failed
-> keep assignment
-> recover message only

External time service

local Clock Out exists + provider failed
-> keep local events
-> reconcile provider only

Never repeat the local business command solely to recover a provider effect.

10. Escalation Packet

environment/source SHA
tenant
operator/role
Loader user ID/name
planner assignment ID
current type/status/order
current persistence markers visible to support
Office list result
Loader Current/Next result
Staff Time/Break/Clock state
Telegram disposition
external time disposition
exact error/timeout
whether any action was repeated

11. Current Evidence State

Current active routes: SOURCE-LOCATED
Typed helper: SOURCE-LOCATED
Current DB row distribution: NOT_RUN
Current caller authority: NOT_COMPLETE
Role/browser/provider evidence: NOT_RUN
Current Wiki: NOT_READ
Field accepted: NO

This addendum does not authorize source or database correction.

---

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