Operations, Transload And Assignment — Current Source Reconciliation

• Status: SOURCE_RECONCILED CURRENT ADAPTER / TARGET APPROVAL BLOCKED
• Parent Task: NS0-003
• Reviewed source revision: qa/master@1529bce22ae39c7c2c11e1b9b07e457e1e4c4355
• Profiles: ctc-execution; selected Office-confirmed concepts may compose into mk-order
• Restriction delta: RD-000 / NONE
• Effects: source/document/catalog reconstruction only; Runtime, DB, route, writer, provider, Wiki and physical effects NONE

1. Reconciliation Result

The current T_TRANSLOAD family is not one target aggregate. It combines several operational concerns:

appointment / service intake context
+ physical fulfillment/work record
+ planning and assignment linkage
+ check-in / dock / staging state
+ Loader execution values
+ completion and correction values
+ warehouse / equipment / document mirrors

The target must preserve separate ownership:

Appointment Availability
!= Fulfillment / Service Request
!= Transload Plan
!= Assignment
!= Field Execution
!= Office Confirmation
!= Inventory Consequence
!= Settlement Consequence

No target state, required field, role restriction or transition is approved by this reconstruction.

2. Current Source Family

Primary current sources:

app/systems/TMS/transload/api_routes.php
app/systems/TMS/transload/request_api_helper.php
app/systems/TMS/transload/request_create_helper.php
app/systems/TMS/transload/assignment_plan_helper.php
app/systems/TMS/transload/assignment_work_helper.php
app/systems/TMS/transload/mobile_execution_helper.php
app/systems/TMS/transload/mobile_stage_helper.php
app/systems/TMS/transload/runtime_planner_helper.php
app/systems/TMS/staff-time/**
frontend/pages/system/TMS/transload/inbound-planning.php
frontend/pages/system/TMS/transload/inbound-loader.php
frontend/pages/system/TMS/transload/loader-timeline.php

Current principal records:

Record	Current responsibility
T_TRANSLOAD	operational appointment/work context, runtime state and result compatibility record
T_LOADING_PLANNER	plan, Loader assignment, queue and runtime projection
T_STAFF_TIME_EVENT	Clock, Break and job-time ledger
T_FILE	photo/document evidence
T_OPERATION_EVENT	supporting notification/event projection, not approval or completion
T_YARD_DISPATCH_QUEUE / T_YARD_LOCATION	related Yard work and physical occupancy, owned outside Operations

3. Current Commands And State Facts

Source-confirmed action families include:

CHECK_IN
STAGING
DOCK_IN
CANCEL_DOCK_IN
DOCK_IN_AFTER_CLEAR
PLAN_PREVIEW
PLAN_APPLY
ASSIGN_SUBMIT
START_TRANSLOADING
START_UNLOADING
COMPLETE_TRANSLOADING
COMPLETE_UNLOADING
COMPLETE_UNLOADING_SPARE
COMPLETE_SPARE
UNDO
UPDATE_DOC_SUBMITTED
UPDATE_DRIVER_CONTACTED

These actions do not establish one universal state machine. Current state is distributed across:

T_TRANSLOAD.STATUS
T_LOADING_PLANNER.JOB_STATUS
timestamps
equipment/load links
warehouse/yard location
staff-time events
files and completion projections

Non-implications:

Planner saved          != assignment accepted
Loader assigned        != work started
Work started           != field completion
Field completion       != Office confirmation
Execution completed    != inventory reconciled
Execution completed    != provider notification delivered
Undo response          != every child effect compensated

4. Planning And Assignment

Current planning uses T_LOADING_PLANNER for both planning facts and runtime/assignment mirrors. The target should separate:

TransloadPlan
Assignment
ExecutionEvidence
CorrectionEvidence

Current assignment has a confirmed representation conflict.

Active route/UI representation:

SPECIAL_INSTRUCTION = QUEUE_WORK_ASSIGNMENT
COMMODITY_NAME       = assignment type
FINAL_DRAFT          = route detail JSON

Typed helper representation:

ASSIGNMENT_DATA JSON
requestToken
typed validation / notification / terminal guards

Disposition:

current representation     = DUAL / DIVERGENT
either family caller-zero  = NOT PROVEN
target representation      = OPEN_DECISION

A target implementation must not copy both as permanent authorities or delete either family without caller/data evidence.

5. Field Execution And Completion

Current Loader execution performs bounded database transactions and may update:

T_TRANSLOAD runtime/result fields
T_LOADING_PLANNER job fields
T_EQUIPMENT / T_EQUIPMENT_LOAD
T_STAFF_TIME_EVENT
Inventory/Yard bridges
transition evidence
post-commit messaging/effect responses

Primary completion and optional effects must be separated:

primary MySQL operation commit
-> authoritative owning-record reread
-> durable effect intent
-> provider/file/message retry and reconciliation

Provider or operation-event failure must not be treated as proof that the physical operation failed when the owning rows committed.

6. Undo And Recovery

Current Undo has selected compensation logic, but it is not a universal reversal of:

inventory lot/ledger
equipment load state
yard occupancy/queue
files
provider messages
accounting/time effects

Target commands must name the exact recovery boundary.

Candidate target command set:

PlanTransload
AssignExecutionWork
AcceptAssignment
StartFieldExecution
CompleteFieldExecution
ConfirmOfficeExecution
CorrectExecution
UndoExecutionAttempt
ReconcileExecution

No candidate command is TARGET_APPROVED.

7. CTC / MK Composition

Concern	CTC current/default candidate	MK target candidate	Classification
capture actor	Loader realtime	Office confirm/common	typed policy
plan	core	conditional	capability
assignment	detailed	optional	capability
warehouse/custody	common	owned receipt	persisted facts + policy
service evidence	core	optional	capability
fake Loader actor	prohibited	prohibited	invariant

Suggested policy:

transload.capture_mode
= LOADER_REALTIME | OFFICE_CONFIRM | OFFICE_ONLY

8. Authoritative Readback

After a mutation, the owning result must be reread from the exact record family:

plan/assignment -> active T_LOADING_PLANNER row
execution       -> exact T_TRANSLOAD + planner + staff-event facts
file evidence   -> T_FILE metadata/object readback
yard effect     -> T_YARD_LOCATION + queue
inventory effect-> lot/ledger/placement owner
provider effect -> provider-attempt/reconciliation evidence

A toast, Telegram ACK or read-model card is not authoritative result evidence.

9. Current Gaps

• exact live schema/index/status distributions were not read;
• current CTC/MK role and route allow/deny behavior was not executed;
• target plan/assignment/execution state owners are not approved;
• Office confirmation semantics remain incomplete;
• dual assignment representation needs live row/caller evidence;
• field photo/weight/quantity requiredness is not inferred;
• Undo and terminal correction need cross-owner policy;
• Work, Break, Idle and Clock Out ownership needs an accepted workforce boundary.

10. Page And Wiki Boundary

This packet changes no Runtime screen.

page-specific browser script = NOT_APPLICABLE
runtime screenshot            = NOT_APPLICABLE
in-app User Wiki              = NOT_APPLICABLE
page CHANGELOG                = NOT_APPLICABLE

Future Operations pages must map their page contract, executable browser script, evidence manifest, User Wiki article and append-only page history before completion.

---

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