Skip to content

System Reconstruction Coverage Matrix — MK Physical Scale Wave

  • Status: CURRENT PHYSICAL SCALE COVERAGE COMPANION
  • Parent register: SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX.md
  • Process: PROC-YMS-SCALE-TICKET-EXECUTION-MK
  • Rebuild packet: MK_PHYSICAL_SCALE_CAPABILITY_REBUILD_PACKET.md
  • Source authority: MK_PHYSICAL_SCALE_SOURCE_AUTHORITY.md
  • Important: these are documentation-coverage labels, not Process lifecycle, Runtime acceptance, deployment approval or migration authorization.

Coverage vocabulary

COMPLETE INPUT
PARTIAL
MAPPED
MISSING
FUTURE PLAN
RUNTIME EVIDENCE REQUIRED
DEVICE EVIDENCE REQUIRED
NOT APPLICABLE

Dimensions:

PDT Product outcome
ROL Roles/access
PRC Process
STA State
DAT Data/identity/fields
INT Query/command/error interfaces
EFF Device/async/provider effects
UIX UI/UX
OPS Operator procedure/recovery
WIK Wiki projection/publication
MIG Migration/rollback/caller-zero
VER Verification evidence

1. Physical Scale Coverage Summary

| Capability | PDT | ROL | PRC | STA | DAT | INT | EFF | UIX | OPS | WIK | MIG | VER | Primary remaining work | |---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| | Schedule and ticket discovery | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | target-role/menu/record scope, current Wiki and route-label verification | | Integrated Check-in | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | accepted flow-stage policy, Sales/Export defect characterization, request idempotency and role matrix | | Entry-stage correction/reweigh | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | recovery role, reason policy, stale/concurrent and response-loss tests | | Check-out preparation | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | replace browser-sequential owner saves with accepted owner preparation contract | | Scale Check-out | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | flow-stage direction, request identity, exact completed readback, all-flow regression | | Purchase finalize handoff | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | finalize-only recovery, multi-line receipt and target-role evidence | | Outbound close handoff | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | close-only recovery and ticket/order partial-result evidence | | Void/reversal | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | accepted recovery owner, downstream-lock matrix and BMS writer conflict | | Ticket event timeline | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | target-role support view and retention/access policy | | Physical device intake | PARTIAL | MISSING | PARTIAL | PARTIAL | PARTIAL | FUTURE PLAN | DEVICE EVIDENCE REQUIRED | FUTURE PLAN | PARTIAL | PARTIAL | FUTURE PLAN | DEVICE EVIDENCE REQUIRED | Product decision, adapter/session/reading provenance, hardware and field evidence | | Physical ticket print | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | target-role print and exact active/tenant fixture evidence | | BMS/YMS writer reconciliation | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | NOT APPLICABLE | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | accepted owner/record scope, competing-caller inventory and caller-zero | | Scale composite | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | Process owner acceptance and end-to-end physical/role/device evidence |


2. Schedule And Read Model Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT Schedule/search locates candidate Purchase, Doortrade, Sales and Export work confirm profile-level inclusion/exclusion and walk-in policy
ROL PARTIAL yms.scale module plus scale-portal menu compatibility semantic view capability and record-level visibility
PRC COMPLETE INPUT list/search/open detail and active-board handoff Process-owner review of current flow inference
STA COMPLETE INPUT Schedule, active and completed dispositions separated accepted target terminology
DAT COMPLETE INPUT order/ticket/Transload/equipment identities mapped exact UUID exposure policy
INT COMPLETE INPUT Schedule, open ticket, detail and event queries version/freshness response contract acceptance
EFF NOT APPLICABLE read-only none
UIX COMPLETE INPUT loading/empty/denied/conflict/completed views defined current target-role screenshots and labels
OPS COMPLETE INPUT exact identity/readback procedure field review
WIK PARTIAL mk-scale projection prepared current row/rendered-page read and publication
MIG COMPLETE INPUT read shadow and parity rows defined measured query result parity
VER RUNTIME EVIDENCE REQUIRED stable read scenarios prepared role/menu/browser/API/DB execution

Current read risk

The active board currently depends on the expected entry stage for the inferred flow. Therefore the Sales/Export Check-in direction contradiction can make a persisted ticket invisible or misclassified even when the ticket row exists.


3. Integrated Check-in Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT first physical stage plus exact order/ticket/link result accepted flow-stage matrix
ROL PARTIAL current module/menu route separate Check-in capability and target-role negative matrix
PRC COMPLETE INPUT current integrated local transaction and target contract Process-owner acceptance
STA PARTIAL entry state derived from flow policy resolve all-flow Gross contradiction
DAT COMPLETE INPUT order/items/ticket/link/event fields and identities request-token schema and version marker
INT COMPLETE INPUT ExecuteScaleCheckIn, DTOs and stable errors final adapter/version shape
EFF PARTIAL current manual entry; device future accepted manual/device policy
UIX COMPLETE INPUT exact loading/unknown/readback/flow-conflict states current/future labels and target-role interaction evidence
OPS COMPLETE INPUT no-blind-retry and exact readback field review
WIK PARTIAL Check-in draft section current Wiki read/publish
MIG COMPLETE INPUT integrated Check-in one-writer wave rollback rehearsal and cohort selection
VER RUNTIME EVIDENCE REQUIRED Purchase/Doortrade/Sales/Export scenarios especially Sales/Export defect reproduction/fix proof

Current positive baseline

order/items/ticket/link
= one local transaction inside /check-in/execute

Current activation blocker

UI flow policy says Sales/Export Tare entry
but integrated Check-in writes Gross for every flow

4. Reweigh / Correction Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT reasoned pre-completion correction actor/approval policy
ROL PARTIAL same menu route currently dedicated yms.scale.reweigh mapping
PRC COMPLETE INPUT unchanged repeat, changed correction, event and exact reread owner review
STA COMPLETE INPUT exit absent, entry version matched, correction event final correction eligibility policy
DAT COMPLETE INPUT before/after stage, actor, reason, request and UOM retention and support-display policy
INT COMPLETE INPUT CorrectScaleEntryStage and stable errors request-token integration
EFF NOT APPLICABLE local transaction only none
UIX COMPLETE INPUT reason-required and stale conflict states target-role usability evidence
OPS COMPLETE INPUT reread before retry and event check field review
WIK PARTIAL recovery draft current content and publication
MIG COMPLETE INPUT separate writer wave old/current caller retirement
VER RUNTIME EVIDENCE REQUIRED same/stale/concurrent/timeout cases local execution and cleanup

5. Check-out Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT second stage and completed ticket accepted downstream completion wording
ROL PARTIAL current menu/module separate Check-out capability
PRC COMPLETE INPUT current sequential owner save, Scale Out and child handoffs documented accept target owner-preparation boundary
STA PARTIAL completed state depends on accepted flow direction resolve flow-stage policy and conflict disposition
DAT COMPLETE INPUT ticket/order/item/link fields owner snapshot version and request identity
INT COMPLETE INPUT PrepareScaleCheckOut, CompleteScaleCheckOut, child results final owner/application interfaces
EFF PARTIAL physical/manual or future device input device policy if activated
UIX COMPLETE INPUT preparation partial, Scale complete/child failed, completed readback target-role evidence
OPS COMPLETE INPUT resume by last confirmed owner boundary field review
WIK PARTIAL Check-out and partial-result draft current Wiki review
MIG COMPLETE INPUT preparation then Scale writer then child handoffs rollback and in-flight reconciliation
VER RUNTIME EVIDENCE REQUIRED partial order save, Scale Out, child failure and response loss local DB/API/browser evidence

Current transaction reality

header/item saves
!= Scale Out
!= Outbound close
!= Purchase finalize

6. Void / Reversal And Event Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT reasoned void/reversal with downstream guard business approval and support ownership
ROL PARTIAL current Scale menu plus generic BMS route coexist semantic recovery capability and BMS restriction
PRC COMPLETE INPUT classify, guard, soft delete, event, detach, readback owner review and residual repair policy
STA COMPLETE INPUT void versus reversal based on completion accepted terminology
DAT COMPLETE INPUT ticket/event/link evidence explicit request-token and retention policy
INT COMPLETE INPUT VoidOrReverseScaleTicket, event query and errors final support DTO
EFF NOT APPLICABLE local transaction only none
UIX COMPLETE INPUT reversal-blocked and residual-conflict states role-field review
OPS COMPLETE INPUT no direct delete/rebuild; exact blocker escalation support rehearsal
WIK PARTIAL correction/reversal draft current Wiki review/publication
MIG COMPLETE INPUT YMS one writer and BMS caller-zero caller inventory and retirement proof
VER RUNTIME EVIDENCE REQUIRED allowed/blocked/response-loss/BMS conflict cases local fixture evidence

7. Device Intake Detail

Dimension Result Current input Gap to close
PDT PARTIAL P2 asks for device-independent intake; current Product acceptance not detailed decide whether/which device capability is required
ROL MISSING no device/operator/maintenance role contract define capabilities and support owner
PRC PARTIAL proposed session/reading/acceptance sequence hardware and field workflow
STA PARTIAL proposed disconnected/unstable/stable/accepted states accepted lifecycle and reconnect behavior
DAT PARTIAL proposed reading envelope device/session/reading persistence and retention
INT FUTURE PLAN proposed adapter/query boundary concrete protocol/SDK/driver contract
EFF DEVICE EVIDENCE REQUIRED no accepted current integration lab and field evidence
UIX FUTURE PLAN Device Status panel operator usability and failure design
OPS PARTIAL manual fallback principles actual SOP/support procedure
WIK PARTIAL future-only notes do not publish until implementation
MIG FUTURE PLAN optional later wave dependency and rollback plan
VER DEVICE EVIDENCE REQUIRED stable/unstable/disconnect scenarios hardware fixture and approved environment

Device scope is not required for the first read-only or manual-entry React migration unless Product separately activates it.


8. BMS / YMS Competing-Writer Detail

Dimension Result Current input Gap to close
PDT COMPLETE INPUT one authoritative MK Scale owner required accept exact BMS retained scope or retirement
ROL PARTIAL module routes known record/capability scope for BMS versus YMS
PRC COMPLETE INPUT YMS and BMS write differences documented reconciliation and caller disposition
STA PARTIAL BMS can change/delete without YMS event/state contract characterize current active callers and data
DAT COMPLETE INPUT same T_SCALE_TICKET family and link differences exact audit/caller evidence
INT PARTIAL YMS owner commands defined; BMS current generic route mapped replacement BMS contract or caller-zero
EFF NOT APPLICABLE local writes none
UIX PARTIAL user conflict visibility not yet current support conflict UI
OPS COMPLETE INPUT freeze/reconcile/no-repeat guidance support rehearsal
WIK PARTIAL admin/support warning current content/publication
MIG COMPLETE INPUT BMS competing-writer retirement wave actual caller-zero and rollback
VER RUNTIME EVIDENCE REQUIRED BMS PATCH/delete conflict scenarios controlled local fixture evidence

9. Reconstruction Artifacts

docs/reconstruction/MK_PHYSICAL_SCALE_CAPABILITY_REBUILD_PACKET.md
docs/reconstruction/MK_PHYSICAL_SCALE_SOURCE_AUTHORITY.md
docs/reconstruction/SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX_SCALE_WAVE.md
docs/processes/MK_SCALE_TICKET_EXECUTION_WORKFLOW.md
docs/processes/MK_PHYSICAL_SCALE_RECONCILIATION.md
docs/processes/MK_PHYSICAL_SCALE_POLICY_DECISION_MATRIX.md
docs/processes/MK_PHYSICAL_SCALE_SEQUENCE_DIAGRAMS.md
docs/processes/MK_PHYSICAL_SCALE_PARITY_AND_CUTOVER_MATRIX.md
docs/runbooks/MK_PHYSICAL_SCALE_OPERATOR_RUNBOOK.md
docs/wiki/internal/MK_PHYSICAL_SCALE_WIKI_PROJECTION_PACKET.md

10. Current Readiness Disposition

Documentation coverage:
DETAILED INPUT

Current source/process reconciliation:
M2 INPUT

Current Process contract freshness:
RECONCILIATION REQUIRED / UPDATED IN THIS WAVE

Flow-stage policy:
CONFLICT / OWNER DECISION REQUIRED

Target-role/runtime evidence:
REQUIRED

Physical device evidence:
NOT ESTABLISHED

BMS/YMS one-writer policy:
OPEN

M4 migration authorization:
NOT ESTABLISHED

11. Next Coverage Wave

Trade / Cost / Rate / Document Outputs

The next family must split:

  • derived Trade Summary reads;
  • mutable cost/rate commands;
  • nondurable browser documents;
  • durable file/email/provider effects where applicable;
  • source freshness and identity;
  • local versus external completion;
  • React/Next.js/TypeScript ownership;
  • rollback/caller-zero and operator/Wiki guidance.

---

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