MK Inbound Mutation And Allocation Evidence

• Evidence period: 2026-07-17 to 2026-07-18
• Evidence class: source review plus bounded Local Client 2 fixtures
• Does not prove: Production, provider, field acceptance, general concurrency or policy approval

Observed Findings

• Inbound Save is transactional, but progressed item edits can reset lot remaining balance and delete protection does not fully express placement, ledger and Scale provenance.
• Placement, allocation, ledger and executed Scale fixtures reproduced the item-level balance/reset boundary with rollback residue reported as zero.
• Allocation summary previously included soft-deleted rows; the later active-row filter and lot-balance invariant changes were recorded as separate scoped deliveries, not as a general progressed-item policy.
• Caller mapping covers inbound editor, Schedule, Scale Portal, transload, Export Brokerage and direct routes. It does not authorize a new edit/delete policy or historical-data repair.

Current Owners And Limits

MK_INBOUND_PURCHASE_WORKFLOW.md, MK_SCHEDULE_ALLOCATION_WORKFLOW.md and their registry scenarios own current process/recovery behavior. This evidence does not replace their lifecycle/unknowns: multi-line receipt, allocation, ledger/Scale combinations, idempotency, concurrent writes and policy selection remain separately bounded.

---

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