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

Current Registered Process Matrix¶

Status: CURRENT RECONCILIATION BASELINE / NOT PROCESS-OWNER APPROVED
Owns: one human-readable row for every process in the P6-001 registered baseline plus explicitly identified P6-007 source-reconciled additions pending canonical registry merge
Does not own: exact registry fields, atomic process semantics, current Runtime proof, lifecycle promotion or migration authorization
Portfolio: OPERATING_MODEL_PROCESS_PORTFOLIO_AND_MIGRATION_MAP.md
Registry: process-registry.yaml
Registry delta packet: 2026-08-07 Final Loading Review reconciliation
Task owner: P6-007
Initial inventory source: P6-001
Current source baseline for this reconciliation: 4fc2f5a893765fbb95e0a2bdcb971322b0ec9fc0

1. Baseline Summary¶

The completed P6-001 baseline reported:

registered processes: 40
atomic: 35
composite: 5
CTC profile: 24
MK profile: 15
unassigned/shared applicability: 1
lifecycle: all draft / partial
reviewed: 0
approved: 0
registry unknowns: 138

Evidence-link counts at that baseline were:

source-verified: 39 processes
documented: 22
browser-verified: 9
production-observed: 1

These are dated inventory facts, not proof that current source, target roles or Production remain identical.

Current P6-007 delta¶

Source reconciliation now identifies one additional atomic CTC process:

PROC-WMS-FINAL-LOADING-REVIEW-CTC
lifecycle: draft
traceability: source-reconciled / partial
migration readiness: M2
canonical registry merge: PENDING

After the approved registry merge, expected portfolio counts become:

registered processes: 41
atomic: 36
composite: 5
CTC profile: 25
MK profile: 15
unassigned/shared applicability: 1

No lifecycle is promoted by this matrix.

Initial migration-readiness interpretation¶

Most P6-001 processes qualify only as M1 DOCUMENTED baseline.
Source-verified entries are M2 CANDIDATES, not automatically M2 at the current revision.
PROC-WMS-FINAL-LOADING-REVIEW-CTC is the first P6-007 source-reconciled M2 process slice; it is not M3 or M4.
No entry is promoted to M3, M4 or M5 by this matrix.
PROC-WMS-INVENTORY-LOT-CORRECTION remains M0-M1 because active business applicability and operator entry are unknown.

2. CTC Execution And Daily Control¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Daily control	`PROC-OPS-DAILY-CTC`	composite / operations	CTC daily menus + Operations Manual	No direct write; reconciles child checkpoints	M1; role/API child coverage and Final Review composition update pending
Request to plan	`PROC-TMS-APPOINTMENT-EMAIL-TO-SCHEDULED-CTC`	atomic / `tms.transload`	Email Approval, Appointment	Mail request/item and scheduled `T_TRANSLOAD`; provider reply separate	M1-M2 candidate; idempotency/role/provider recovery gaps
Plan to physical completion	`PROC-TMS-INBOUND-PLANNING`	atomic / `tms.transload`	Planning, Assignment Board, Loader, Timeline, Completed	Transload, planner, staff event, completion and Yard handoff	M1-M2 candidate; role/undo/side-effect gaps
Final loading review	`PROC-WMS-FINAL-LOADING-REVIEW-CTC`	atomic / `wms.inventory`	Report > Inventory Adjustment / Final Loading Review	`T_TRANSLOAD.BALE_REVIEW_*` review state; readiness consumes planner, metrics and active ledger evidence	M2 source-reconciled; role/policy/Production/M3 gaps
Yard execution	`PROC-YMS-YARD-DISPATCH`	atomic / `yms.yard-move`	Yard Dispatch, Instruction, Map, Closing	Queue=`T_YARD_DISPATCH_QUEUE`; occupancy=`T_YARD_LOCATION`	M1-M2 candidate; concurrency/duplicate/partial physical recovery
Delivery execution	`PROC-TMS-DRIVER-DELIVERY`	atomic / `tms.delivery`	Driver	Delivery, driver log, file evidence and conditional Yard effects	M1-M2 candidate; assignment/partial recovery gaps
Yard-to-driver	`PROC-OPS-YARD-TO-DRIVER-HANDOFF-CTC`	composite / operations	Yard + Driver entries	No new state; Yard and Driver owners reread separately	M1; durable correlation and acceptance incomplete

CTC execution handoff skeleton¶

reviewed request / manual appointment
-> scheduled work
-> Inbound Planning
-> assignment
-> Loader execution
-> completed transload/unload/reload
-> Final Loading Review for eligible Reload/Transload
-> Source/Leftover adjustment when required
-> Inventory and/or Yard handoff
-> optional Driver delivery
-> document/billing/reconciliation

A completed child does not imply the next child completed.

3. CTC Billing, Documents And Provider Effects¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Billing close	`PROC-BMS-BILLING-CLOSE-CTC`	composite / `operations.billing`	AR Billing, Billing Presets	No direct write; reconciles transaction/QBO/file/email children	M1; provider/role/field acceptance incomplete
Local transaction	`PROC-BMS-TRANSACTION-LIFECYCLE-CTC`	atomic / `bms.transaction`	AP/AR transaction lists	`T_TRANSACTION`, `T_TRANSACTION_LIST` local lifecycle	M1-M2 candidate; delete/correction/role evidence required
AR confirmation	`PROC-BMS-AR-BILLING-CONFIRM-CTC`	atomic / `bms.transaction`	AR Billing	Preset/candidate review and local AR confirmation	M1-M2 candidate; exact role and duplicate behavior required
QBO delivery	`PROC-BMS-AR-QBO-DELIVERY-CTC`	atomic / `bms.transaction.qbo`	AR Billing	Provider delivery/reconciliation after local commit	M1-M2 candidate; durable retry/reconcile/manual fallback critical
Transaction file	`PROC-BMS-TRANSACTION-DOCUMENT-CTC`	atomic / shared files	Nested transaction document action	`T_FILE` object/link plus transaction reference	M1-M2 candidate; file/storage/delete parity needed
BOL email	`PROC-TMS-BOL-EMAIL-CTC`	atomic / `tms.transload`	Appointment/Transload edit	BOL/scale attachment email effect	M1-M2 candidate; provider idempotency/unknown-result handling
Packing-list email	`PROC-TMS-PACKING-LIST-EMAIL-CTC`	atomic / `tms.booking`	Packing List	Target/part email effect	M1-M2 candidate; multipart/retry/reconciliation gaps

Independent completion checkpoints¶

local record committed
!= provider effect delivered
!= file readable
!= email delivered
!= composite close accepted

Migration packets must preserve these independent checkpoints.

4. CTC Warehouse, Inventory And Reports¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Label output	`PROC-TMS-WAREHOUSE-LABEL-PRINT-CTC`	atomic / `tms.transload`	Label Print, Load Label	Read/render/physical print; no durable print completion	M1; output projection/physical proof distinction
Placement	`PROC-WMS-LABEL-WAREHOUSE-PLACEMENT-CTC`	atomic / `wms.inventory`	Load Label	Warehouse location plus transload compatibility mirror	M1-M2 candidate; one owner and correction parity required
Warehouse visibility	`PROC-WMS-WAREHOUSE-GRID-INVENTORY-OVERLAY`	atomic / `wms.inventory`	Warehouse Map	Read projection over grid, lot, location and source work	M1-M2 read candidate; freshness/query/role parity needed
Final loading review	`PROC-WMS-FINAL-LOADING-REVIEW-CTC`	atomic / `wms.inventory`	Inventory Adjustment / Final Loading Review	persisted review status, actor/time/reason and readiness policy	M2; canonical registry merge, role/policy/M3 evidence pending
Bale adjustment	`PROC-WMS-BALE-INVENTORY-ADJUSTMENT-CTC`	atomic / `wms.inventory`	Inventory Adjustment, Bale Inventory	Lot balance, ledger/count, Source/Leftover and reversal	M1-M2 candidate; now separated from review-state authority
Report reconciliation	`PROC-OPS-REPORT-RECONCILIATION-CTC`	composite / operations	Child report pages	No direct write; reconciles four report children	M1; no durable completion/owner cadence
Inventory movement report	`PROC-WMS-INVENTORY-MOVEMENT-REPORT-CTC`	atomic / `wms.inventory`	Inventory Report	Read-only movement projection	M1-M2 read candidate
Storage aging report	`PROC-WMS-STORAGE-AGING-REPORT-CTC`	atomic / `wms.inventory`	Storage Report	Read-only aging projection	M1-M2 read candidate
Trucking summary	`PROC-BMS-TRUCKING-SUMMARY-REPORT-CTC`	atomic / `bms.rate`	Trucking Summary	Read-only delivery/driver/transaction projection	M1-M2 read candidate
Monthly inventory	`PROC-WMS-MONTHLY-ACCUMULATIVE-INVENTORY-REPORT-CTC`	atomic / `wms.inventory`	Monthly/Accumulative reports	Read-only aggregate projection	M1-M2 read candidate; date/business rules required
Physical snapshot	`PROC-WMS-PHYSICAL-INVENTORY-SNAPSHOT-CTC`	atomic / `wms.inventory`	Inventory Report Physical	Draft/final snapshot transaction	M1-M2 candidate; immutable completion/reload recovery
Trucking AP-rate refresh	`PROC-BMS-TRUCKING-AP-RATE-REFRESH-CTC`	atomic / `bms.rate`	Trucking Summary	Guarded zero-rate batch update	M1-M2 candidate; batch/rollback/readback required

Final Loading Review reconciliation result¶

P6-007 source reconciliation decided:

PROC-WMS-FINAL-LOADING-REVIEW-CTC
= separate atomic process
= draft / source-reconciled
= M2
= canonical registry merge pending

The process owns review eligibility, derived readiness, Confirm, Bulk Confirm, Reopen and review-sensitive mutation protection. It references, but does not own, Source/Leftover lot and ledger mutation.

Current blockers include:

menu/API role mismatch;
Client-ID-specific role behavior;
customer-name TGI weight exemption;
Reopen metadata semantics;
reason-before-confirm partial-write semantics;
weight threshold/UOM/rounding policy;
Bulk mixed-result transaction characterization;
target-role/Production/Wiki evidence.

See:

FINAL_LOADING_REVIEW_WORKFLOW.md;
FINAL_LOADING_REVIEW_MIGRATION_PACKET.md;
Registry reconciliation packet.

5. MK Order-First Composite And Commercial Flow¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Order-to-packing	`PROC-OMS-ORDER-TO-PACKING-MK`	composite / OMS	Order, allocation, Scale, Trade and document pages	No direct state; references 14 atomic owners	M1; child maturity/role/optionality controls readiness
Commercial agreement	`PROC-OMS-COMMERCIAL-ORDER-MK`	atomic / `oms.commercial-order`	Commercial Orders	Commercial header/items, relation and status labels	M1-M2 candidate; post-execution edit/status/role gaps
Purchase to inventory	`PROC-OMS-INBOUND-PURCHASE-TO-INVENTORY-MK`	atomic / `oms.inbound-order`	Inbound Orders, Doortrade	Purchase header/items, receipt/transload/lot handoff	M1-M2 candidate; scale/no-scale and materialization parity
Sales to outbound	`PROC-OMS-OUTBOUND-SALES-ORDER-MK`	atomic / `oms.outbound-order`	Outbound Orders	Sales header/items and Booking/equipment bridge	M1-M2 candidate; readiness/delete/recovery gaps
Booking	`PROC-TMS-BOOKING-LIFECYCLE-MK`	atomic / `tms.booking`	Booking List	Booking, outbound references and sync tasks	M1-M2 candidate; tenant parameterization/compatibility/role gaps

MK composite skeleton¶

Commercial Purchase
-> Inbound Purchase
-> optional physical Scale
-> receipt / transload / inventory lot

Commercial Sales
-> Outbound Sales
-> Booking / equipment
-> inventory allocation
-> optional Scale / packing / documents / cost / trade outputs

Scale and document children are conditional. Composite completion does not create a new universal status.

6. MK Inventory, Allocation, Scale And Trade¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Inventory allocation	`PROC-OMS-INVENTORY-TO-OUTBOUND-ALLOCATION-MK`	atomic / `oms.allocation`	Allocation Workbench	Lot balance, allocation and outbound demand effects	M1-M2 candidate; concurrency and unsupported reversal block M4
Export brokerage	`PROC-OMS-EXPORT-BROKERAGE-MK`	atomic / `oms.export-brokerage`	Export Brokerage	Generated child owners; authoritative-data list remains a gap	M1; compensation/provenance/ownership reconciliation needed
Physical Scale	`PROC-YMS-SCALE-TICKET-EXECUTION-MK`	atomic / `yms.scale`	Scale Portal	`T_SCALE_TICKET`; order/link/finalize are separate owners	M1-M2 candidate; physical/transaction/role/correction evidence required
Trade summary	`PROC-OMS-TRADE-SUMMARY-RECONCILIATION-MK`	atomic / `oms.trade-summary`	Trade Summary	Read-only derived deal projection	M1-M2 read candidate; source classification/freshness parity
Outbound cost	`PROC-BMS-OUTBOUND-ORDER-COST-MK`	atomic / `bms.transaction`	Outbound Order Cost	Selected outbound-linked AP transaction	M1-M2 candidate; replace/delete/file recovery required

7. MK Rates And User-Facing Outputs¶

Value stream	Process	Type / owner	Normal operator entry	Record / mutation / completion authority	Current readiness note
Packing output	`PROC-TMS-PACKING-DOCUMENT-MK`	atomic / `tms.booking`	MK Packing List	Current projection and browser print only	M1-M2 read/output candidate; no durable completion
Packing rate correction	`PROC-OMS-PACKING-RATE-CORRECTION-MK`	atomic / `oms.outbound-order`	MK Packing List	Outbound item-rate correction	M1-M2 candidate; blur autosave/partial result/restoration
Purchase invoice output	`PROC-BMS-PURCHASE-LOCAL-INVOICE-OUTPUT-MK`	atomic / `bms.invoice`	Local Invoice	Read-only invoice calculation/output	M1-M2 read/output candidate
Booking confirmation	`PROC-TMS-BOOKING-CONFIRMATION-OUTPUT-MK`	atomic / `tms.booking`	Booking Confirmation	Current Booking output projection	M1-M2 read/output candidate
Sales weight ticket	`PROC-BMS-SALES-WEIGHT-TICKET-OUTPUT-MK`	atomic / `bms.scale-ticket`	Scale Ticket Print	Sales-weight output; not physical Scale authority	M1-M2 read/output candidate

Outputs must not be treated as durable document completion unless Product/process policy explicitly creates that authority.

8. Shared / Applicability Unknown¶

Process	Type / owner	Entry	Authority	Current disposition
`PROC-WMS-INVENTORY-LOT-CORRECTION`	atomic / `wms.inventory`	No confirmed active operator entry	Shared lot correction capability	Business/profile owner unknown; lifecycle `draft/partial`; M0-M1

P6-007 must decide whether this is:

a shared atomic process with explicit role/profile policy;
an internal command capability used by other processes;
a dormant compatibility endpoint;
a retirement candidate.

9. Portfolio Handoff Matrix¶

From	Completion evidence	To	Carried context	What is not implied
Appointment review	durable accepted request and scheduled work	Inbound Planning	request/item/work IDs, date and operational context	provider reply or physical execution completed
Inbound Planning/Loader	completed Reload/Transload and exact planner/metric reread	Final Loading Review	transload/planner IDs, loading type, quantity/weight and active ledger context	review ready or confirmed
Final Loading Review	exact Confirmed review readback	Inventory/daily reconciliation	transload ID, actor/time/reason and active source/leftover evidence	lot mutation, warehouse move, billing or provider completion
Source/Leftover adjustment	exact lot balance and active/reversed ledger readback	Final Loading Review	lot/ledger/transload identities	review confirmed
Yard Dispatch	queue/occupancy reread after physical move	Driver or completion review	work/delivery/location IDs	delivery completed
Commercial Purchase	accepted commercial relationship	Inbound Purchase	commercial/order/item identity	receipt, scale or inventory exists
Inbound Purchase	receipt/transload/lot readback	Inventory/Trade	order/item/lot/source identity	allocation or settlement completed
Commercial Sales	accepted sales relationship	Outbound/Booking	commercial/order/item identity	Booking or allocation completed
Booking	Booking/outbound/equipment reread	Allocation/packing/documents	Booking/outbound/container context	shipment or document completion
Local billing confirm	local transaction/invoice reread	QBO/document/email	local IDs and amount/source context	provider/file/email completion

Detailed identity, partial-result and recovery contracts are in CROSS_PROCESS_HANDOFF_AND_IDENTITY_MATRIX.md.

Every actual process contract must add partial/duplicate/stale/recovery behavior before M3/M4.

10. Role And Cadence Baseline¶

Responsibility	Likely role family	Cadence	Evidence state
Appointment/request review	Office / Dispatch	continuous/daily	exact current matrix incomplete
Planning/assignment	Office / Dispatch / Loader lead	daily/shift	partial source/local evidence
Loader execution	Forklift Operator	per job	partial; server/API parity gaps
Final Loading Review	Office reviewer	after eligible completion/daily	M2 source-reconciled; menu/API role and SLA unresolved
Bale Source/Leftover adjustment	Office / Inventory	exception-driven	source/local evidence; semantic role/capability incomplete
Yard movement	Dispatch / Yard Driver	continuous	partial; concurrency/role gaps
Delivery	Truck Operator	per job/day	partial; assignment/effect recovery gaps
Inventory/warehouse	Office / Warehouse	daily/periodic	fragmented across processes
Billing/provider close	Office / Accounting	daily/periodic	partial; provider/role evidence gaps
MK commercial/order	MK Office roles	per agreement/order	target-role matrix incomplete
Management/report review	Administrator / Manager	daily/monthly	cadence/completion/SLA incomplete

This is a gap map, not an approved role contract.

11. Reconciliation Requirements¶

P6-007 updates this matrix only after:

repinning the exact source revision;
reconciling the registry, current process documents and Operational handovers;
tracing changed entry/state/recovery behavior;
confirming current owner/version/lifecycle;
identifying roles/cadence/escalation or retaining UNKNOWN;
assigning evidence-backed M0-M5 status;
recording Wiki content coverage separately;
obtaining process-owner/user review for lifecycle promotion.

No row becomes approved or M3+ because it appears in this matrix. A P6-007 source-reconciled addition remains pending canonical registry merge until the registry owner accepts the reconciliation packet.

---¶

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