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

Trade document registry reconciliation (2026-08-07)

  • Status: EXACT REGISTRY REVIEW INPUT / NOT MERGED INTO REGISTRY
  • Date: 2026-08-07
  • Registry owner: single P6 process-portfolio writer
  • Source baseline: qa@d96498360bb9c3541a1b5f862284596a7ed217b9
  • Effect boundary: documentation only

1. Purpose

Record exact Process-document version and source-reconciliation changes without partially overwriting the shared process-registry.yaml authority.

This packet does not create new Process IDs for the Trade/Cost/Rate/Document family. It proposes version/source-note reconciliation for existing Process records.

2. Current Family IDs

PROC-OMS-TRADE-SUMMARY-RECONCILIATION-MK
PROC-OMS-EXPORT-BROKERAGE-MK
PROC-BMS-OUTBOUND-ORDER-COST-MK
PROC-OMS-PACKING-RATE-CORRECTION-MK
PROC-TMS-PACKING-DOCUMENT-MK
PROC-BMS-PURCHASE-LOCAL-INVOICE-OUTPUT-MK
PROC-TMS-BOOKING-CONFIRMATION-OUTPUT-MK
PROC-BMS-SALES-WEIGHT-TICKET-OUTPUT-MK

No new family umbrella Process is required. The family rebuild packet is a reconstruction assembly, not a Process owner.

3. Proposed Version Reconciliation

Process ID Current registry/doc version to verify Proposed document version Reason
PROC-OMS-TRADE-SUMMARY-RECONCILIATION-MK likely 0.2.0 keep 0.2.0 pending atomic owner review family packet adds reconstruction detail but atomic doc was not rewritten
PROC-OMS-EXPORT-BROKERAGE-MK 0.2.0 0.3.0 current generated marker/provenance and compensation source reconciled
PROC-BMS-OUTBOUND-ORDER-COST-MK 0.2.0 keep 0.2.0 pending accounting/source review family packet adds migration detail; current atomic doc remains source-compatible
PROC-OMS-PACKING-RATE-CORRECTION-MK 0.2.0 keep 0.2.0 pending field review source contract unchanged
PROC-TMS-PACKING-DOCUMENT-MK 0.2.0 keep 0.2.0 pending template/source review source contract unchanged
PROC-BMS-PURCHASE-LOCAL-INVOICE-OUTPUT-MK 0.2.0 keep 0.2.0 pending access/formula review source contract unchanged
PROC-TMS-BOOKING-CONFIRMATION-OUTPUT-MK 0.2.0 0.3.0 current explicit page-role guard and source precedence documented
PROC-BMS-SALES-WEIGHT-TICKET-OUTPUT-MK 0.2.0 0.3.0 current physical IDS[] access correction and output/Scale separation documented

Related prior wave:

Process ID Proposed document version Registry check
PROC-YMS-SCALE-TICKET-EXECUTION-MK 0.3.0 registry version/source note must be reconciled with Physical Scale packet

4. Lifecycle

All listed Process documents remain:

draft

Source reconciliation and document version updates do not promote lifecycle to reviewed or approved.

5. Registry Metadata To Reconcile

For the three updated documents and Physical Scale:

  • contract_version;
  • source-document path;
  • last source-reconciliation date/revision;
  • owner domain/module keys if current registry differs;
  • current Wiki slug;
  • M2 source-reconciled note where the registry supports it;
  • unresolved policy/evidence references;
  • no false M3/M4 state.

Do not add the family rebuild packet as an atomic Process.

6. Source Corrections To Preserve

Export Brokerage

  • generated Equipment and generated Booking marker support exists;
  • no durable Job/request identity exists;
  • selected active Booking remains primary in inspected Ocean validation;
  • exact generated-Booking create path requires Runtime characterization;
  • cancel is guarded compensation, not general delete.

Booking Confirmation

  • current direct page explicitly requires bookingConfirmation page-role access;
  • output remains nondurable and does not confirm/approve Booking.

Sales Weight Ticket

  • ORDER_ID output remains Sales projection, not physical Scale evidence;
  • current generic physical IDS[] branch has role/tenant/active predicates;
  • output remains nondurable.

Physical Scale

  • current integrated Check-in and event/reversal behavior are documented;
  • Gross/Tare Sales/Export contradiction remains blocking.

7. Merge Procedure

Single registry writer:

  1. read current process-registry.yaml at merge revision;
  2. locate exact existing records;
  3. compare all fields and current writers;
  4. update only accepted version/source-note fields;
  5. validate count/unique IDs/reference paths;
  6. reread the changed records;
  7. record commit and evidence in P6-007;
  8. do not change lifecycle/readiness without separate acceptance.

8. Stop Conditions

Stop registry write when:

  • current registry has a different owner/version under active review;
  • another writer is modifying the same records;
  • source-document paths differ;
  • updating version would imply lifecycle/readiness promotion;
  • current Process owner rejects the source correction;
  • Exact Wiki slug/module/profile remains unresolved.

9. Current Effect State

process-registry.yaml changed: NO
Process IDs added: NO
Lifecycle changed: NO
Runtime changed: NO
Wiki changed: NO

This packet is the exact handoff for the registry owner.

---

Source: docs/processes/reconciliation/2026-08-07-trade-document-registry-reconciliation.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.