Skip to content

CTC Logistics Workspace Context History

  • Status: APPEND-ONLY DECISION HISTORY
  • Current Context: CTC_NEW_SYSTEM_CONTEXT.md

2026-08-14 — Successor Program Reset

  • Legacy P1-P12 was stopped and frozen.
  • new-system/docs/** became the active Product/Design/Development/Roadmap/Task authority.
  • Legacy remained operational fallback and reconstruction evidence.

2026-08-14 — Foundation, Process And AI-Context Hardening

  • Process reconstruction was required before broad Runtime implementation.
  • The target filesystem, module ownership, dependency direction, documentation/catalog and Source Registry contracts were fixed.
  • Tasks became self-contained execution contracts.
  • Generated graphs/context became non-authoritative projections.

2026-08-14 — Scope, Booking Golden Slice And Legacy Surface Transition

  • CTC and MK became the initial implementation scope; adjacent families are candidate/deferred.
  • Current CTC source became the current-behavior baseline.
  • MK uses the current CTC repository and same MySQL as CLIENT_ID = 2; reference/mkmetal/** is secondary evidence.
  • Booking/Ocean Booking replaced Material Receipt as the first Golden Slice.
  • Legacy menus/pages/popups remain compatibility surfaces while Product surfaces are additive.
  • CTC project-local knowledge remains in-repository; a generic Knowledge Platform is separate.

2026-08-14 — UI Direction Before Process And Foundation

  • User requested UI direction confirmation before Process reconstruction and Runtime Foundation.
  • NS0-002 was reassigned to initial UX direction and representative surface approval.
  • Process reconstruction moved to NS0-003.
  • A separate NS0-004 finalizes UI/page/interaction contracts after Process reconstruction.
  • NS1 is blocked until NS0-004 is accepted.
  • Initial UI approval may decide visual language, shell, navigation, density and interaction direction, but may not invent final fields, states, requiredness, permissions or transaction semantics.

Effect: documentation, Roadmap and Task sequencing only. No Runtime, DB, route, writer, provider, service, Wiki or physical effect.

---

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