Skip to content

Current Operational Evidence Worksheet Index — 2026-08-08

1. Purpose

The parent evidence register defines what must be proved. These worksheets and preflight packages define how a later authorized evidence session can execute the current high-risk packages without reconstructing source callers, database queries, accounts, fixtures, concurrency cases, cleanup, or acceptance criteria from conversation history.

evidence package defined
!= evidence authorized
!= evidence executed
!= PASS
!= M3/M4

Every package separates:

  • source facts;
  • database facts;
  • runtime/API/browser facts;
  • provider/physical facts;
  • current Wiki facts;
  • cleanup and acceptance.

2. Worksheet Register

Package Current question Source preflight DB preflight Detailed worksheet Status
RBR-AWCO-002 Are current Loader Work Assignment Route and typed-helper contracts safe and consistent across queue writers, roles, Clock Out guards, Final Break, and providers? Caller and guard inventory Read-only DB preflight Evidence worksheet SOURCE PREFLIGHT PASS / DB QUERY PACKAGE COMPLETE / NOT RUN
RBR-FLR-001 Do current Final Loading Review comparison, Edit Outbound, adjustment, Confirm/Bulk/Reopen, and recovery paths work for intended roles? Current source delta defined inside worksheet Evidence worksheet DEFINED / NOT AUTHORIZED / NOT RUN
RBR-STREET-001 Do current Street Turn create and guarded Revert preserve exact identity, downstream blockers, transaction, physical, and recovery boundaries? Current Process contract defined inside worksheet Evidence worksheet DEFINED / NOT AUTHORIZED / NOT RUN

3. RBR-AWCO-002 Source Preflight

Current source has two representations:

active Route rows
= QUEUE_WORK_ASSIGNMENT + COMMODITY_NAME + FINAL_DRAFT

separate typed helper
= ASSIGNMENT_DATA + requestToken + advisory locks

The current caller inventory located:

  • active Route registrations;
  • Office Assignment Board calls;
  • Loader page calls;
  • typed helper Runtime includes;
  • terminal guard callers in Break and Transload writers;
  • typed active-row reader in the general Staff Time Clock Out endpoint;
  • selected Transloading transition writer boundaries.

Confirmed source discrepancies:

terminal Clock Out guard sees typed rows only
general Clock Out protection sees typed rows only
Final Break uses different Planner/event identity by representation
cancellation uses CANCELED versus CANCELLED
request and notification evidence differs by representation

Source-only result:

static caller/guard preflight: PASS
current DB occurrence: NOT READ
runtime reproduction: NOT RUN
target-role impact: NOT ESTABLISHED

4. RBR-AWCO-002 Read-Only DB Preflight

The query package defines stable statements for:

AWCO-DB-001..004  environment/schema/index identity
AWCO-DB-010..012  representation population and JSON validity
AWCO-DB-020..021  status and cancellation spelling
AWCO-DB-030..033  terminal rows, later rows, bypass candidates
AWCO-DB-040..041  Started-job and queue-order conflicts
AWCO-DB-050..052  Route/typed/mixed Final Break evidence
AWCO-DB-060..061  request-token and notification evidence
AWCO-DB-070..071  Staff Time duplicate and Planner/event consistency
AWCO-DB-080       bounded safe row sample
AWCO-DB-090       final classification

Safety properties:

  • SELECT and information_schema reads only;
  • explicit tenant scope;
  • no row/advisory lock;
  • no subquery or derived table;
  • no full JSON or employee/provider target export;
  • no repair statement;
  • stop conditions for target, schema, read-only safety, PII, and query pressure.

Current result:

query design: COMPLETE
template validation: PASS
database connection: NOT PERFORMED
queries executed: 0
results: NONE

5. RBR-AWCO-002 Priority Runtime Scenarios

AWCO-RUN-031 — later Break after Route-owned Clock Out
AWCO-RUN-032 — later Load/Work after Route-owned Clock Out
AWCO-RUN-050 — general Clock Out against Started Route-owned Clock Out
AWCO-RUN-051 — cleaning prerequisite bypass attempt
AWCO-RUN-052 — final-Break prerequisite bypass attempt
AWCO-RUN-060 — missing create response and queue reread
AWCO-RUN-061 — notification failure recovery on existing row

The DB preflight must run first. No scenario is authorized by this index.

6. RBR-AWCO-002 Worksheet Coverage

The worksheet defines:

  • Office/Loader/denied/foreign/support accounts;
  • current and historical representation row counts;
  • caller and terminal-guard classification;
  • duplicate create and missing-response cases;
  • Work/Break/Load concurrency;
  • one-active-job and event uniqueness;
  • Final Break and general Clock Out bypass;
  • notification and external-time partial/unknown recovery;
  • current advice-tooltip and mobile behavior;
  • current Wiki content;
  • cleanup of Planner, Staff Time, and provider fixtures.

7. RBR-FLR-001 Highlights

Current source question:

Shipper
CTC Inbound
Loading Difference
CTC Outbound
Avg/Bale warning
Pending Edit Outbound
Source/Leftover/Weight/Confirm/Reopen

The worksheet defines:

  • intended/denied/concurrent-reviewer accounts;
  • fixtures for every derived review state;
  • Shipper missing/zero/fallback cases;
  • positive/negative/zero/opposite-sign differences;
  • average exactly/above current threshold;
  • Edit Outbound validation and optimistic conflicts;
  • missing response before/after commit;
  • state recalculation;
  • Source/Leftover/Weight transactions;
  • Confirm/Bulk/Reopen and mutation guards;
  • no unintended Scale/inventory/billing/provider effect;
  • mobile/Wiki evidence;
  • reversible lot/ledger cleanup and compensation.

The current threshold and customer-name weight compatibility remain policy inputs, not universal target rules.

8. RBR-STREET-001 Highlights

Current source question:

eligible import EMPTY
-> matching export Booking
-> generated export load
-> guarded Revert
-> exact prior returned import restoration

The worksheet defines:

  • Import/Export/Manager/denied/foreign accounts;
  • equipment/load/Booking fixtures;
  • same shipping line/size and Booking eligibility;
  • batch partial results and create response loss;
  • exact generated export identity;
  • Delivery/Transload blockers;
  • concurrent export/equipment/import changes;
  • transaction rollback and double Revert;
  • prior-import lineage ambiguity;
  • physical/Yard handoff and non-implication;
  • current Wiki evidence;
  • compensation and fixture cleanup.

A database Revert is never treated as physical or downstream Process reversal.

9. Shared Authorization Contract

Before execution, every package must name:

repository and deployed source SHA
environment/runtime URL
DB identity/version
tenant/profile/timezone
actor/effective subject and role
allowed read/write/provider/physical/Wiki effects
fixture IDs and isolation method
cleanup/compensation owner
stop conditions
accepting owner

Defaults:

Production destructive/concurrency fixtures: PROHIBITED
provider calls to real users/employees: PROHIBITED
Wiki write: PROHIBITED
service/restart/deployment: PROHIBITED

Only a new explicit user instruction can change an effect boundary.

10. Shared Result Classification

Each scenario:

PASS
FAIL
BLOCKED
NOT_RUN
NOT_APPLICABLE

Each package:

PASS — all required dimensions characterized and accepted
FAIL — current behavior violates an accepted invariant
BLOCKED — authority/environment/fixture unavailable
PARTIAL — bounded evidence collected; named dimension remains

A package PASS does not itself:

  • select a canonical target contract;
  • authorize a source fix;
  • authorize deployment;
  • publish Wiki content;
  • establish M4.

11. Cleanup Rule

no disposable write without a named cleanup/compensation path
no live inconsistency treated as fixture residue
no blind provider replay
no raw DB repair in place of an owner command
no final PASS before after-state reread

Cleanup failure is reported as a package failure or unresolved residual effect.

12. Current Effect State

Worksheet creation: COMPLETE
Loader static source preflight: COMPLETE
Loader read-only DB query package: COMPLETE / NOT RUN
Runtime evidence execution: NOT RUN
Runtime source mutation: NONE
DB connection/read/write: NONE
Role/account mutation: NONE
Provider/physical/file effect: NONE
Wiki DB read/write: NONE
Deployment/recovery effect: NONE
Phase progress: NONE

13. Maintenance

Update the applicable source preflight, DB preflight, or worksheet when current source, persistence representation, schema/index, route/role contract, guard behavior, provider behavior, physical process, Wiki content, fixture policy, cleanup command, or accepting owner changes. Keep query and scenario IDs stable where the business question remains the same.

---

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