Skip to content

MK Process Contract Reconstruction Baseline

  • Evidence date: 2026-07-17
  • Evidence class: source-reconciled current-state baseline
  • Scope: Client 2 (mk-trading); no runtime, DB, browser mutation or deployment evidence

Canonical Owners

The registered MK commercial, inbound/outbound, booking/packing/allocation/export, Scale, Trade, cost and document workflows own current behavior. The matching Local and Production Wiki pages own operator procedure.

Commercial, Inbound And Outbound

  • Commercial Purchase/Sales agreements are separate and the optional Purchase to Sales relation has tenant/type checks but no approved lifecycle policy.
  • Inbound header, item, transload, Scale and lot state remain separate. Direct operational/time edits can materialize inventory outside explicit receipt commands.
  • Direct Outbound creation is UNMAPPED; Allocation owns lot-balance effects. Ambiguous multi-request results require exact child reread, never blind retry.

Booking, Packing, Schedule, Allocation And Export

  • Booking flags and Packing output are independent; rendered/printed output has no durable completion acknowledgement.
  • Schedule is a projection, while Allocation owns allocation rows and current lot-weight decrement. It has no general reversal or proven complete concurrency guard.
  • Export Brokerage is a child-process orchestrator, not a generic delete or a durable Job owner; multi-line/lot-sync and cancel provenance remain gaps.

Scale, Trade, Billing And Documents

  • Scale owns physical ticket/link boundaries; Trade Summary is a derived reconciliation read, not a stored lifecycle state.
  • Outbound Cost selection, Packing Rate autosave and document outputs have incomplete subtype, validation, acknowledgement or readback guarantees.
  • Local Invoice, Booking Confirmation and Sales Weight Ticket are projections, not durable invoice/confirmation/ticket-output completion.

Limits

The baseline preserves WP03-13 through WP03-16 source findings. It does not approve draft lifecycles, resolve role/tenant/concurrency/output-policy gaps, or prove provider, physical, Production or field-user behavior.

---

Source: docs/research/mk/2026-07-17/MK_PROCESS_CONTRACT_RECONSTRUCTION_BASELINE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.