Skip to content

CTC Inbound Loader Evidence — 2026-07-16

  • Classification: OBSERVED-FACT
  • Captured: production aggregate observation and Local rollback-safe checks
  • Tenant: CLIENT_ID = 1
  • Does not own: current process contract, Runtime fact, lifecycle promotion or operator procedure

Bounded production aggregate

For [2026-07-15 00:00:00, 2026-07-16 00:00:00) UTC, a tenant-scoped, aggregate-only sample observed 50 start jobs, 49 end jobs, and one active in-progress job. Completed pairs ended as TRANSLOADED 42, UNLOADED 6 and SPARE 1; paired duration was 18s minimum, 2,449.1s average and 8,569s maximum. This is not an SLA or productivity measure.

Observed and unproven boundaries

  • Local rollback checks observed Start/Complete state transitions, duplicate completion rejection and zero provider calls after cleanup.
  • The dated source did not prove assigned-user mutation enforcement, complete unload atomicity, server photo revalidation, durable Telegram delivery or Client-2 route UAT.
  • Timeline GET may auto-close an expired break and is not strict read-only audit evidence. Terminal undo did not prove complete compensation.

2026-07-17 source-reconstruction boundary

The dated source reconstruction separated Planning Save, Apply, assignment and Telegram send; established the embedded Assignment Board as the active entry; and recorded the Office → Loader → completion report → Timeline → Yard handoff. It also recorded that the prior source did not prove universal DOCKED, clock-in, assigned-user or five-photo server invariants; direct terminal Undo was not a complete compensation path; and Completed/Timeline surfaces may write or expose separate controls. These were source risks, not newly imposed runtime restrictions. The current workflow owns later behavior changes and recovery rules.

Retention

This record preserves aggregate evidence only: no raw IDs, user names, SQL, payloads, phone numbers or before-row data were retained. Current behavior and recovery remain in the Inbound Planning workflow and process registry.

---

Source: docs/research/processes/2026-07-16/CTC_INBOUND_LOADER_EVIDENCE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.