Scale Correction — 2026-08-08¶

Status: CURRENT CORRECTION TO HIGH-RISK DRIFT REGISTER
Current review ref: qa/master@a71386e3baf176534939a42397249bcd2b535c49
Parent register: HIGH_RISK_PACKET_SOURCE_DRIFT_REVIEW_2026-08-08.md
Validation: MK_TRADE_ALLOCATION_SCALE_CURRENT_REFRESH_VALIDATION_2026-08-08.md
Phase implementation: USER HOLD

1. Purpose¶

The parent drift register correctly required additional review, but its three MK classifications were based on incomplete baseline interpretation.

This correction supersedes the parent register only for:

MK Trade / Cost / Rate / Document Outputs
MK Inventory Allocation
MK Physical Scale

It does not change the disposition of other families.

2. Corrected Summary¶

Family	Previous classification	Corrected classification	Current use
MK Trade / Cost / Rate / Documents	diverged candidate baseline / historical candidate input only	`CANDIDATE LABEL DISENTANGLED / CORE SOURCE REVALIDATED / ENVIRONMENT EVIDENCE REQUIRED`	use current lineage refresh plus existing packet
MK Inventory Allocation	baseline missing	`EXACT CURRENT BASELINE PINNED / CORE SOURCE REVALIDATED / DATA-POLICY EVIDENCE REQUIRED`	use current baseline/caller refresh plus existing packet
MK Physical Scale	baseline missing	`ORIGINAL BASELINE ALREADY PRESENT / CURRENT SOURCE REVALIDATED / STATIC CONTRADICTION AND PHYSICAL EVIDENCE REQUIRED`	use current baseline/caller refresh plus existing packet

3. Trade Correction¶

Previous interpretation¶

declared baseline = d964983...
baseline diverged from current
candidate-only source facts might exist

Current lineage result¶

The true merge base is:

4f6165bc4c53a7d98b0c246392dd9ed5bd75c21c

The only candidate-only commit is:

feat(tms): add loader assignment work and final clock out

It contains no Trade-family owner changes.

Current core Trade owner blobs are unchanged from 4f6165... except the shared Booking route file, whose material changes are adjacent Street Turn and Booking Inquiry behavior. The Packing Rate block was independently revalidated.

Corrected disposition¶

CANDIDATE LABEL PROBLEM:
RESOLVED

CANDIDATE-ONLY TRADE FACTS:
NONE LOCATED

CORE SOURCE:
CURRENT STATIC SOURCE REVALIDATED

CURRENT DB/ROLE/ACCOUNTING/WIKI:
EVIDENCE REQUIRED

Current owner:

Do not use d964983... as a Trade source baseline.

4. Allocation Correction¶

Previous interpretation¶

exact baseline absent
source freshness cannot be established

Current result¶

The current owner set is now pinned at:

qa/master@a71386e3baf176534939a42397249bcd2b535c49

Exact page, JS, API, query, post and shared write-helper blobs have been recorded. The Allocation API and shared write helper are unchanged from the reviewed 4f6165... ancestor.

Corrected disposition¶

BASELINE MISSING:
RESOLVED

CORE SOURCE:
CURRENT STATIC SOURCE REVALIDATED

CURRENT DATA/ROLE/QUANTITY-WEIGHT POLICY:
EVIDENCE REQUIRED

Current owner:

5. Physical Scale Correction¶

Previous interpretation¶

packet/source authority lacks exact source SHA

Current result¶

The existing source authority already declared:

qa@4f6165bc4c53a7d98b0c246392dd9ed5bd75c21c

Current revalidation at a71386e... found the core YMS Scale route and browser contracts unchanged.

Corrected disposition¶

BASELINE MISSING:
FALSE

CURRENT CORE SOURCE:
REVALIDATED

GROSS/TARE CONTRADICTION:
PERSISTS IN CURRENT STATIC SOURCE

YMS/BMS WRITER CONFLICT:
PERSISTS

DEVICE/RUNTIME/PHYSICAL EVIDENCE:
REQUIRED

Current owner:

6. Corrected Documentation Queue¶

After this package:

Trade current-lineage reconstruction:
COMPLETE

Allocation exact baseline/caller pinning:
COMPLETE

Physical Scale baseline/caller pinning:
COMPLETE

Read-only evidence packages:
DEFINED / NOT AUTHORIZED / NOT RUN

Remaining work is primarily:

current DB/schema/data evidence;
current roles/pages/APIs;
accepted business policy;
provider/physical evidence;
current Wiki content;
one-writer/rollback/caller-zero design after evidence.

7. Non-Implication¶

source freshness refreshed
!= runtime verified
!= target-role accepted
!= policy accepted
!= migration ready

No M3 or M4 status changes result from this correction.

---¶

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