MK Trade Current-Lineage And Surface Validation — 2026-08-09¶
- Status:
STATIC VALIDATION PASS / CURRENT ENVIRONMENT EVIDENCE NOT RUN - Current refresh:
MK_TRADE_CURRENT_LINEAGE_AND_SOURCE_REFRESH_2026-08-09.md - Current matrix:
MK_TRADE_CURRENT_CALLER_EFFECT_AND_OUTPUT_MATRIX_2026-08-09.md - Read-only package:
RBR-TRADE-001-READONLY-CURRENT-SURFACE-PREFLIGHT.md - Effects: source/document inspection only
1. Validation Purpose¶
This document validates that:
- the historical detached candidate is no longer treated as current authority;
- current statements are grounded in current long-lived source owners;
- Trade, Export Brokerage, Cost, Rate, document output, and physical evidence remain separate;
- the read-only package does not mutate data or call a provider;
- detailed documentation is not presented as Runtime evidence, M3, or M4.
2. Lineage Validation¶
Historical source reference:
d96498360bb9c3541a1b5f862284596a7ed217b9
Current refresh reference:
master@a71386e3baf176534939a42397249bcd2b535c49
Validation rule:
candidate statement
-> locate current owner
-> confirm current source semantics
-> retain as current
otherwise
-> historical candidate evidence or open question
The refresh does not use candidate branch status, local candidate tests, or candidate completion language as evidence of current qa/master behavior.
Result: PASS.
3. Current Source Owner Validation¶
The following current owner families were inspected or mapped:
config/page_routes.php
app/addons/reports/query_helper.php
app/systems/OMS/export-brokerage/*
app/systems/OMS/inbound-order/*
app/systems/OMS/outbound-order/*
app/systems/TMS/booking/api_routes.php
app/systems/BMS/transaction/*
app/shared/sync/*
frontend/pages/system/BMS/reports/mk-trade-summary.php
frontend/pages/system/OMS/export-brokerage/mk-export-brokerage.php
frontend/pages/system/TMS/booking/*
frontend/pages/system/BMS/invoice/localInvoice.php
Validated current findings:
| Finding | Result |
|---|---|
| Trade Summary is a source projection, not a persisted Trade aggregate | PASS |
| Deal status/claimed-style labels require derived-status wording | PASS |
| Export Brokerage spans multiple child owners | PASS |
| generated compatibility markers exist but are not durable job identity | PASS |
| Outbound Cost is implemented through transaction infrastructure | PASS |
| Packing Rate writes Booking-linked Sales/Outbound item rates | PASS |
| item eligibility can yield partial effective coverage | PASS |
| current output pages are render/print projections | PASS |
| Sales Weight Ticket and physical Scale evidence must be distinguished | PASS |
Result: PASS.
4. Overclaim Validation¶
The refresh does not claim:
- that the current database contains Export Brokerage marker rows;
- that every generated marker belongs to one coherent child set;
- that no duplicate Export Brokerage set exists;
- that a durable job/manifest table is absent from every environment;
- that multiple AP cost candidates currently exist;
- that current users encounter a Packing Rate partial result;
- that a rendered document was emailed or stored;
- that any current role is over- or under-permitted;
- that a Production incident occurred;
- that current Wiki content matches the repository draft.
Result: PASS.
5. Capability Separation Validation¶
The matrix preserves:
Trade projection
!= Export Brokerage command
!= Cost transaction
!= Rate correction
!= Document render
!= File/email result
!= Physical Scale evidence
Examples:
Export Brokerage¶
orchestrator creates child
!= orchestrator permanently owns child lifecycle
Packing Rate¶
one updated item
!= all requested items updated
Sales Weight Ticket¶
order-derived output
!= physical measurement evidence
Result: PASS.
6. Read-Only Package Construction Validation¶
6.1 Allowed statement forms¶
The package is restricted to:
SELECT
SHOW
information_schema read
It contains no intended:
INSERT
UPDATE
DELETE
REPLACE
ALTER
CREATE
DROP
TRUNCATE
FOR UPDATE
LOCK TABLES
GET_LOCK
RELEASE_LOCK
mutating CALL
Result: PASS.
6.2 Schema-first behavior¶
The package inventories tables, columns, indexes, constraints, and candidate marker/relation columns before running family queries.
Unknown relationship columns are represented as explicit verified placeholders. The executor must stop rather than guess a join.
Result: PASS.
6.3 Tenant and record scope¶
Business queries require:
CLIENT_ID = <CLIENT_ID>
Detail queries require approved record IDs and bounded limits.
Result: PASS.
6.4 Sensitive-data boundary¶
The package does not require:
- full marker/remark/note text;
- customer email addresses;
- provider credentials;
- full document body;
- file object bytes;
- signed URLs;
- foreign-tenant data.
Marker queries return marker class and row identity only.
Result: PASS.
6.5 Browser scope¶
Browser evidence is limited to:
- menu/page GET;
- initial read API;
- approved record display;
- control visibility;
- non-mutating print preview;
- network/no-mutation observation.
Consequential controls are explicitly prohibited.
Result: PASS.
7. Recovery Validation¶
The packet requires authoritative reread before replay for:
Export Brokerage create/cancel
Outbound Cost save/delete
Packing Rate update
Document render/print
It never treats a response timeout as proof of absence or failure.
Result: PASS.
8. Target Architecture Validation¶
The refresh remains aligned with:
React UI
+ Next.js adapter
+ framework-independent TypeScript application/domain/policy
+ current MySQL repositories first
+ one writer per selected capability/cohort
+ rollback and caller-zero
+ PostgreSQL later
It does not prescribe:
- a monolithic Trade service;
- Route Handler SQL;
- React-owned business status;
- generic JSON mutation;
- generic cross-provider outbox;
- PHP/TypeScript dual writes;
- simultaneous database migration.
Result: PASS.
9. Documentation Set Validation¶
Required companion documents are present in this package:
current lineage/source refresh
current caller/effect/output matrix
read-only evidence preflight
current validation
high-risk drift correction
operator Runbook addendum
Wiki projection addendum
handover
navigation updates
Result: PASS after final branch comparison confirms only documentation paths.
10. Evidence Still Required¶
current deployed source identity
current schema/index inventory
current Trade source breakdown
current generated marker/child sets
current multi-AP cost cases
current Packing Rate item coverage
current document-source completeness
current role/page/API behavior
current render/print behavior
current file/email evidence
current physical Scale evidence
current Wiki rows/rendering/findability
11. Final Validation Result¶
Lineage correction:
PASS
Current static source mapping:
PASS FOR NAMED OWNERS
Capability/effect separation:
PASS
Read-only package safety:
PASS
Environment execution:
NOT RUN
Authenticated role execution:
NOT RUN
Provider/File/Physical execution:
NOT RUN
M3:
NO
M4:
NO
Phase progress:
NONE
---¶
Source:
docs/reconstruction/MK_TRADE_CURRENT_SURFACE_VALIDATION_2026-08-09.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.