Scale — Current Authority Index — 2026-08-09¶

Status: CURRENT DUAL-REF SOURCE AUTHORITY / DOCUMENTATION ONLY
Release authority: master@baff406d964b9f785bf98d2ae84cfb262e26f4b2
Integration authority: qa@1dfed7d5c827f992e763c63bfca95324a60af387
Previous detailed refresh baseline: a71386e3baf176534939a42397249bcd2b535c49
Previous promotion commit: 40fb4020e2993347eb7cde9cb24ee9f6201cd806
Phase implementation: USER HOLD
Runtime, DB, role, provider, file, device, Wiki and deployment effects: NONE

1. Why This Index Exists¶

The MK Trade, Inventory Allocation and Physical Scale families already have detailed source-authority, rebuild, policy, Runbook, Wiki and read-only evidence packets.

After those packets were refreshed, two materially different current refs emerged:

master
= released source authority

qa
= integration-candidate authority
= includes master
+ additional unpromoted source changes

The refs are intentionally not interchangeable.

qa behavior
!= released behavior

master behavior
!= every candidate correction already present

document on both refs
!= source on both refs is identical

This index prevents a future session from reading one branch and silently describing its behavior as universal current behavior.

2. Precedence¶

For current operational claims, use this order:

1. exact named environment/deployed SHA evidence
2. released source at master@baff406...
3. post-refresh release/QA delta
4. current family source refresh at a71386...
5. detailed family source-authority and rebuild packets
6. historical plans and candidates

For integration review, use:

1. qa@1dfed7... source
2. release/QA delta matrix
3. released master behavior as compatibility baseline
4. candidate-specific evidence and rollback

Never use QA-only behavior as an operator procedure for a released environment without an exact deployed-source readback.

3. Current Delta Owners¶

Cross-family post-refresh source authority¶

Existing current refreshes¶

The 2026-08-08 refresh remains valid for its baseline. The 2026-08-09 delta owns changes after that baseline.

4. Family Reading Order¶

Trade / Cost / Rate / Document Outputs¶

Post-refresh branch delta
-> Trade lineage/source refresh
-> Trade/Cost/Rate/Document source authority
-> capability rebuild packet
-> caller/effect matrix
-> read-only evidence packet
-> operator and Wiki addenda

Current high-risk deltas:

date-filtered Trade projection includes rows with no ETA and no ETD;
mk-deal-ledger alias has a canonical module-repair migration candidate, not an applied-state proof;
Outbound Cost no longer has the prior advanced-operation helper guard in released source;
order/reference update semantics can preserve the existing link instead of applying an invalid requested link;
UI role scope and backend mutation scope require separate evidence.

Inventory Allocation¶

Post-refresh branch delta
-> Allocation baseline/caller refresh
-> Allocation source authority
-> capability rebuild packet
-> read-only evidence packet
-> operator and Wiki addenda

Current high-risk deltas:

no direct released Allocation command change was identified after the prior refresh;
shared Inbound/Outbound save and reference owners changed materially;
empty item sets and line deletion no longer carry the prior advanced-operation guard in the released shared order path;
QA contains additional OrderSync and shared writer changes not released to master;
source-lot and target-order evidence must state which ref produced the read model.

Physical Scale¶

Post-refresh branch delta
-> Physical Scale baseline/caller refresh
-> Scale source authority
-> rebuild packet
-> read-only evidence packet
-> operator and Wiki addenda

Current high-risk deltas:

the prior Gross for every flow source contradiction is closed in released source;
released Check-in now selects Gross for inbound and Tare for outbound;
released outbound Check-in derives Tare steering weight from the commodity Gross aggregate, which requires policy and runtime evidence;
released source does not expose the integrated /yms/scale/check-out/execute route;
the released Scale workflow smoke expects that integrated route;
QA adds integrated Check-out, order-ticket relationship checks and item-count readback, but those are integration-candidate behavior;
legacy Check-out remains present alongside the QA integrated route.

5. Stable Discrepancy IDs¶

SCALE-DISCREPANCY-001
Gross-for-all integrated Check-in
Disposition: CLOSED IN RELEASE SOURCE

SCALE-DISCREPANCY-002
Release runtime does not expose integrated Check-out route expected by release smoke
Disposition: CURRENT RELEASE SOURCE/TEST MISMATCH

SCALE-DISCREPANCY-003
Released outbound Check-in writes Tare steering from commodity Gross aggregate
Disposition: CURRENT SEMANTIC QUESTION / RUNTIME EVIDENCE REQUIRED

SCALE-DISCREPANCY-004
Release and QA have different Scale command boundaries
Disposition: CURRENT DUAL-REF AUTHORITY

ORDER-DISCREPANCY-001
UI role scope and backend Order/Cost mutation scope are not equivalent
Disposition: CURRENT ACCESS/POLICY EVIDENCE REQUIRED

TRADE-DISCREPANCY-001
Date filter retains undated rows
Disposition: CURRENT SOURCE FACT / PRODUCT POLICY REQUIRED

TRADE-DISCREPANCY-002
Legacy deal-ledger alias repair exists as migration candidate only
Disposition: APPLIED-STATE EVIDENCE REQUIRED

6. Evidence State¶

Existing packages remain:

RBR-TRADE-001
RBR-ALLOC-001
RBR-SCALE-001

The post-refresh addendum extends them with:

release-vs-QA source identity
Scale route inventory
Scale entry-weight provenance
legacy and integrated Check-out coexistence
Trade undated-row behavior
module alias applied-state check
order/reference preservation behavior
role/UI/API parity
Allocation handoff parity across refs

Current state:

source delta: DOCUMENTED
read-only addendum: DEFINED
runtime/database/role/device/Wiki execution: NOT RUN
M3: NO
M4: NO
Phase progress: NONE

7. What This Index Does Not Authorize¶

merging QA source into master;
changing Scale routes or weight policy;
changing Order, Cost, Booking or Allocation roles;
applying the deal-ledger migration;
executing Scale, Trade, Cost, Rate, Allocation or document commands;
changing DB rows or schema;
publishing Wiki content;
treating QA tests as released acceptance;
treating released source as current production without deployed SHA readback;
Phase activation.

8. Maintenance Rule¶

Whenever either long-lived branch changes a named owner file, update:

exact branch SHA
changed owner/caller
release vs integration disposition
operator-visible meaning
read-only evidence extension
rollback/caller-zero impact

Do not overwrite the prior refresh. Add a dated delta so historical source authority remains traceable.

---¶

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