Skip to content

CTC Parallel Read-Only Evidence Integration — 2026-08-10 Queue / 2026-08-11 Revalidation

  • Task: CTC-EVID-007 — Parallel Evidence Integration And Contradiction Review
  • Status: INTEGRATED / CURRENT PRODUCTION READ-ONLY REVALIDATION / OPEN FAILURES AND DEFERRED EFFECTS PRESERVED
  • Queue: CTC_PARALLEL_READONLY_EVIDENCE_QUEUE_2026-08-10.md
  • Repository and remote refs: qa == origin/qa == origin/master == 85025157609bf32f3b2904cc816bb7397d88b468
  • Production deployed source: master@85025157609bf32f3b2904cc816bb7397d88b468
  • Production DB: prod, MySQL 8.0.45, read-only transaction verified
  • Tenant/account scope: canonical superadmin plus Client 1 admin and jaylee; no login, logout, impersonation or browser session created
  • Restriction delta: NONE
  • Phase impact: NONE — Phase Transformation remains USER HOLD
  • M3/M4 change: NONE

This document integrates the six original family result/handover pairs and the 2026-08-11 Production read-only revalidation. The original result files remain the exact 2026-08-10 execution records; this file controls current cross-family interpretation when their old repository or environment statements conflict with the revalidation below.

1. Input Accounting

Task Result Handover Input state
CTC-EVID-001 RBR-MK-TRADE-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-mk-trade-readonly-evidence-handover.md accounted
CTC-EVID-002 RBR-ALLOC-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-mk-allocation-readonly-evidence-handover.md accounted
CTC-EVID-003 RBR-SCALE-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-mk-scale-readonly-evidence-handover.md accounted
CTC-EVID-004 RBR-IDENTITY-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-platform-identity-readonly-evidence-handover.md accounted
CTC-EVID-005 RBR-TENANT-CONFIG-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-platform-tenant-config-readonly-evidence-handover.md accounted
CTC-EVID-006 RBR-DEPLOY-RESTORE-002-EVIDENCE-RESULT-2026-08-10.md 2026-08-10-platform-deployment-recovery-readonly-evidence-handover.md accounted

Expected inputs: 6. Received exactly once: 6. Missing: 0. Duplicate: 0.

2. Common Identity Readback

Evidence Result Current observation
Git qa/master parity PASS local and remote refs equal 8502515760...
Production deployed SHA PASS /var/www/html is clean master@8502515760... except an unreadable archive-manifest directory warning
Production DB identity PASS MySQL 8.0.45, database prod, transaction_read_only=1, 77 tables
Production web entry PASS loopback /login.php returned 200
PHP-FPM process PASS service active; unit is static/disabled rather than boot-enabled directly
Auto-pull PASS autopull.timer loaded, active, waiting and enabled
Voice Gateway PASS service active/enabled; loopback /healthz returned 200 with ok=true, enabled=true
Controlled browser session NOT_RUN no login/session effect authorized or created
Provider behavior NOT_RUN no OAuth, email, QBO, Twilio or other provider call made
Physical Scale behavior NOT_RUN — PHYSICAL AUTHORIZATION REQUIRED no device, calibration, weighing or vehicle action

Git parity proves repository deployment identity only. It does not prove every business path, target role, provider, file/object or physical result.

3. Current Source Drift

Trade / Cost / Rate / Documents

The five core Trade owner blobs from the original result remain unchanged at 8502515760.... The Scale Ticket document page changed from the old result blob to 9702f41c...; current source still keeps the direct page role guard and the separate order-derived and ticket-ID branches. The deployment matches this source.

Inventory Allocation

Six dedicated Allocation owner blobs remain unchanged. Shared app/systems/OMS/inbound-order/mk_post_helper.php changed from 0b331049... to 1085baec..., but the reviewed diff changes Sales/Purchase draft and Scale order behavior, not the Allocation route/query/apply symbols. The focused Allocation browser contract passed.

Physical Scale

Scale materially changed after the original result:

  • Check-in and Check-out now require an already-saved order and saved items;
  • the execute routes no longer save order headers/items;
  • submitted Scale ticket weight remains the stage authority;
  • the portal now uses shared inbound/outbound order editors and a two-direction table.

The four direction/prefix rules remain source-present:

Purchase / Doortrade: Gross in -> Tare out
Sales / Export:       Tare in  -> Gross out

Focused source contracts produced 26 PASS / 3 FAIL. Failing checks:

  1. Yard table fallback should show Driver when Company is absent.
  2. Check-in shared-editor delegation contract does not match the current portal bytes.
  3. Two-direction Booking/container axle-entry contract does not match the current portal bytes.

Therefore current Scale source verification is FAIL; passing route/direction checks do not override the three failures.

Identity, Tenant/Config And Deployment

No Identity or Tenant/Config owner drift was located after the original family results. Current deployment and DB metadata now replace their former environment-blocked status only for the exact observations recorded here.

4. Production Schema And Data Evidence

Trade

  • Required Trade tables and V_TRADE_SUMMARY are present.
  • V_TRADE_SUMMARY: 27,579 Client 1 rows; 89 have more than one outbound-order link.
  • AP transactions: 718 CREATED, 32,044 CONFIRMED, 229 CLOSED.
  • AR transactions: 5,984 CREATED, 567 CONFIRMED, 103,650 CLOSED.
  • T_COMMODITY_RATE has zero active Client 1 rows; T_TRUCKING_RATE has 602.
  • Row-specific Trade/AP/rate/document ownership and browser/Wiki rendering remain BLOCKED because no exact business record fixture or controlled browser session was selected.

Inventory Allocation

Schema metadata for T_INVENTORY_LOT, T_LOAD_ALLOCATION, T_LOAD, T_LOAD_ITEM, T_EQUIPMENT, T_EQUIPMENT_LOAD, T_TRANSLOAD and T_INVENTORY_LOT_LEDGER is present.

Client 1 aggregate readback:

active allocations                         8318
matching active lots                       8204
allocations pointing to soft-deleted lots   114
missing lot rows                               0
cross-tenant lot links                         0
missing order/item links                       0
item/order identity mismatches                 0
negative allocation quantity/weight            0
active lots with blank LOT_STATUS              77
blank-status lots with positive quantity       61
blank-status lots with positive net weight     50
active PARTIAL lots                             0

ALLOC-EVID-DAT-001 is FAIL: active allocation rows are expected to resolve to active same-tenant lots, but 114 resolve only to soft-deleted lots. Blank LOT_STATUS rows are a second current-data reconciliation signal. No repair, delete, status normalization or allocation replay was performed.

Physical Scale

Schema metadata for ticket, event, inbound/outbound bridge and order/item tables is present. Client 1 aggregate readback:

active Scale tickets                    45329
both Gross and Tare recorded            37855
Gross total below Tare total              110
inbound-linked tickets                  23465
outbound-linked tickets                 17321
unlinked active tickets                  4543
Scale event rows                            0
inbound Purchase item Net mismatches     5332

The 4,543 unlinked tickets, 110 Gross-below-Tare tickets, zero event rows and 5,332 current item Net mismatches are FAIL / RECONCILIATION REQUIRED for the corresponding consistency checks. They do not by themselves prove when a row was created, whether it is a permitted legacy state, or what repair is safe.

Identity And Tenant/Config

  • Canonical users exist without deletion: superadmin under Client 0, and admin/jaylee under Client 1.
  • admin and jaylee currently carry Client 1 Role ID 1 (Administrator).
  • Client 1 Role, module and config metadata was read without config values.
  • T_TENANT_CONFIG exposes key/type/module/timestamp metadata; no plaintext, ciphertext, token, cookie, password or hash was read.
  • No table name matching session/revocation/token was found. This is bounded schema-name evidence, not proof that no other session authority exists.
  • Login/logout, impersonation, role mutation, credential reveal/update and cache-update tests remain NOT_RUN.

5. Cross-Family Evidence Matrix

PASS + BLOCKED means the exact bounded check passed while a broader evidence class still contains named unavailable items.

Family SRC SCH DAT ROL RUN PHY PRO FIL WIK DEP BAK
Trade PASS PASS PASS + BLOCKED NOT_RUN NOT_RUN N/A NOT_RUN BLOCKED NOT_RUN PASS N/A
Allocation PASS PASS FAIL NOT_RUN NOT_RUN N/A N/A N/A N/A PASS N/A
Scale FAIL PASS FAIL NOT_RUN NOT_RUN NOT_RUN N/A N/A N/A PASS N/A
Identity PASS PASS PASS PASS + NOT_RUN NOT_RUN N/A N/A N/A N/A PASS N/A
Tenant/Config PASS PASS PASS NOT_RUN NOT_RUN N/A NOT_RUN N/A N/A PASS N/A
Deployment/Recovery PASS PASS N/A N/A PASS N/A N/A BLOCKED N/A PASS BLOCKED

6. Contradiction Review

Class Result
SOURCE != DEPLOYED not observed for Git identity; Production matches current master
DOCUMENT != SCHEMA previous environment unknowns resolved for named tables; historical repository snapshots remain non-authoritative
DOCUMENT != DATA Allocation and Scale failures above; Trade multiple-link rows require record-level interpretation
SOURCE != ACCESS OBSERVATION NOT_RUN; no controlled browser/session observation
DB != FILE/OBJECT BLOCKED; DB file metadata was not reconciled to object inventory
DB CREDENTIAL ROW != KEY RECOVERABILITY BLOCKED; metadata exists, but compatible key/rotation recovery was not proved
SERVICE LIVE != READY service liveness passed; full dependency/business readiness remains unproved
BACKUP EXISTS != RESTORE VERIFIED backup metadata read was denied; restore was not attempted
SYSTEM SCALE DATA != PHYSICAL VERIFIED system data observed; physical/device evidence remains NOT_RUN

7. Recovery And Secret-Safety Boundary

  • /etc/ctc/prod.env metadata: root-owned mode 600.
  • external Gmail credential-file metadata: root/apache mode 640.
  • storage default reports s3; bucket is configured, but versioning/backup policy was not verified.
  • RDS backup metadata read returned authorization denied and remains BLOCKED.
  • No backup, restore, failover, provider callback or object read/write occurred.
  • No secret/config value, ciphertext, token, cookie, password or key material was captured in this document.

One execution deviation occurred: an S3 metadata command redirected stderr to /tmp/ctc-s3-versioning.err. The exact temporary file was immediately removed with readback confirming absence. No business/object data or durable server state remains, but the queue's strict no file effect performed claim is not asserted for this revalidation session.

8. Smallest Next Controlled Waves

  1. Review the three failing Scale source contracts against the intended current UI and fix either stale tests or source under a separately authorized operational change.
  2. Select bounded Allocation and Scale record IDs from the aggregate anomalies, then perform row-level read-only lineage classification without repair.
  3. Use an already-existing controlled admin/jaylee session for passive page/GET evidence; do not create or destroy sessions in that wave.
  4. Grant a read-only backup-inventory channel and inspect RDS/S3/EFS recovery metadata without restore.
  5. Run provider, mutation/concurrency, physical Scale and isolated restore waves only under their separate exact authorizations.

9. Completion Boundary

CTC-EVID-001..006 result/handover accounting: PASS
CTC-EVID-007 integration: PASS
current Production source/deployment identity: PASS
current schema metadata: PASS for named tables
current data integrity: FAIL for named Allocation/Scale checks
controlled browser/provider/physical/restore evidence: NOT_RUN / BLOCKED
restriction delta: NONE
Phase progress: NONE
M3/M4 promotion: NONE
queue no-file-effect claim for this revalidation: NOT ASSERTED

---

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