This is an internal working record, not an everyday instruction. It was written while the system was being rebuilt, for whoever maintains it. If you are here to do today's work, use the everyday documents instead: Procedures · Processes · Runbooks · The working day, step by step

Outputs — Current Source Operator Addendum¶

Status: CURRENT-SOURCE REPOSITORY RUNBOOK / NOT FIELD-ACCEPTED
Current source refresh: MK_TRADE_CURRENT_LINEAGE_AND_SOURCE_REFRESH_2026-08-09.md
Parent Runbook: MK_TRADE_COST_RATE_DOCUMENT_OUTPUTS_OPERATOR_RUNBOOK.md
Evidence package: RBR-TRADE-001-READONLY-CURRENT-SURFACE-PREFLIGHT.md
Phase implementation: USER HOLD

1. Purpose¶

Use this addendum when investigating current Trade, Export Brokerage, Cost, Rate, or document-output behavior. It corrects the historical candidate baseline and supplies current unknown-result boundaries.

It does not authorize a source change, data repair, Export Brokerage create/cancel, Cost/Rate write, email, file action, or physical Scale action.

2. Before Investigation¶

Record:

source/deployed SHA
environment/database
tenant/profile
actor/subject/role
page/API/action
approved business IDs
current time/timezone
expected result
whether any local/provider/file/physical effect may already exist

Do not record:

provider credentials;
full customer payload;
unrestricted remarks/notes;
signed file URL;
full rendered document with unrelated records.

3. Identify The Capability First¶

Choose exactly one:

TRADE_PROJECTION
EXPORT_BROKERAGE_CREATE
EXPORT_BROKERAGE_CANCEL
OUTBOUND_COST
PACKING_RATE
PACKING_DOCUMENT
PURCHASE_LOCAL_INVOICE
BOOKING_CONFIRMATION
SALES_WEIGHT_TICKET_ORDER_DERIVED
SALES_WEIGHT_TICKET_PHYSICAL

Do not investigate all of them as one transaction.

4. Trade Summary Investigation¶

Symptom: wrong total, margin, or status¶

stop editing the report;
identify the selected Trade/order/equipment/booking references;
record the query time and filters;
identify every included AP/AR source class;
compare Header and Detail source coverage;
verify deleted-row and status filters;
verify shipment marker/date precedence;
correct only the owning business source when separately authorized;
rerun the projection.

Important¶

CLOSED-like derived label
!= accounting settlement
!= irreversible business close

CSV¶

A downloaded CSV is a projection copy. Do not use it as proof that the underlying source is immutable or reconciled.

5. Export Brokerage Investigation¶

5.1 Before create¶

Verify:

exact source record;
intended child types;
no existing coherent generated child set;
no partial/multiple/conflicting generated set;
current state of related Booking, Outbound, Equipment, Inventory, Allocation, and Transaction records;
intended actor authority.

5.2 Response missing after create¶

STOP
-> do not submit create again
-> search exact source and generated markers
-> build the expected child manifest
-> classify COMPLETE_MATCH / PARTIAL / MULTIPLE_MATCHES / CONFLICT / UNKNOWN

If a complete match exists, treat the create as committed even if the browser response was lost.

If partial or unknown, escalate to the owning process engineers. Do not fill missing rows through generic forms or direct data edits.

5.3 Before cancel/reverse¶

Identify:

exact generated child set;
downstream business history;
balance/allocation effects;
file/provider/physical effects;
children already compensated;
children blocked from compensation.

5.4 Response missing after cancel¶

Reread every child and return a per-child disposition.

COMPENSATED
ALREADY_COMPENSATED
BLOCKED_DOWNSTREAM
NOT_FOUND
CONFLICT
UNKNOWN

Do not repeat the whole cancellation while any child is unknown.

6. Outbound Cost Investigation¶

Symptom: wrong Cost row opened or updated¶

identify the exact Outbound Order;
list all active AP transactions linked to it;
identify whether the request supplied a Transaction ID;
detect latest-row fallback or ambiguous selection;
compare Header and active Lines;
verify allowed Status;
verify file links separately;
verify Trade Summary readback separately.

Response missing after save¶

reread exact transaction ID
+ active line set
+ outbound relation
+ updated timestamp/status

Repeat only if absence is proven.

Non-implications¶

Cost saved
!= QBO delivered
!= accounting approved
!= Trade settled
!= file stored

7. Packing Rate Investigation¶

Before rate change¶

Record:

Booking ID;
every intended Sales/Outbound item ID;
current rate per item;
expected new rate;
role/account;
print state.

Response returns only an updated count¶

Do not assume all requested items succeeded.

Reread every intended item and classify:

UPDATED
UNCHANGED
STALE
DENIED
NOT_FOUND
INVALID

Print/save race¶

When print opens before save/readback completes:

close or disregard the stale preview;
reread every intended item rate;
regenerate the document;
open print preview again.

Do not manually alter the printed document to hide a failed rate update.

8. Document Output Investigation¶

8.1 General rule¶

Rendered
!= Stored
!= Emailed
!= Approved
!= Completed

8.2 Packing document¶

Verify Booking, item, Equipment Load, commodity/detail, and Rate sources. Record whether browser-only note/amount fields are persisted or transient.

8.3 Purchase Local Invoice¶

Verify:

source quantity/weight;
UOM and conversion divisor;
rate;
fee;
credit;
rounding;
total;
source business date/reference.

Do not report the output as a durable accounting invoice unless a separate record proves that lifecycle.

8.4 Booking Confirmation¶

Verify reference precedence, template/branding owner, date source, recipient authority, and current page-role access.

8.5 Sales Weight Ticket¶

Label the evidence source explicitly.

ORDER_DERIVED
or
PHYSICAL_SCALE

An order-derived ticket must not be represented as proof that a physical scale measurement occurred.

9. Access Problems¶

For a visible/hidden/forbidden mismatch, collect:

menu/page
module
route method/path
route role metadata
handler actor check
tenant/record predicate
record state
UI control state
actual result

Do not solve the problem by granting a broad Administrator role or enabling every module.

Packing Rate currently carries numeric route roles. That current fact is not an accepted long-term role policy.

10. Safe Result Labels¶

Use:

CURRENT SOURCE PRESENT
CURRENT SOURCE-RECONCILED
CURRENT DATA EXPOSURE
PARTIAL RESULT
MULTIPLE MATCHES
CONFLICT
PROVIDER/FILE/PHYSICAL EVIDENCE REQUIRED
UNKNOWN — DO NOT REPLAY
TARGET DESIGN
HISTORICAL CANDIDATE EVIDENCE

Do not use:

DONE
CLOSED
SENT
SAVED
APPROVED
REVERSED

without naming the exact authority that proves it.

11. Escalation Packet¶

source/deployed SHA
environment/database/tenant
actor/subject/role
capability and exact action
business IDs
before/current state
request/correlation ID if available
source/child/item/file/scale evidence
partial/unknown classification
what was NOT repeated
safe screenshots/IDs
requested owner decision

Exclude secret values and unrelated customer content.

12. Current Readiness¶

Repository Runbook:
CURRENT-SOURCE ADDENDUM PRESENT

DB/role/browser evidence:
NOT RUN

Wiki publication:
NOT RUN

Field acceptance:
INCOMPLETE

M3 / M4:
NO / NO

---¶

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