Skip to content

Decision 0001 — Scope, Booking Golden Slice, Evidence Authority And Legacy Surface Transition

  • Status: ACCEPTED
  • Date: 2026-08-14
  • Owner: Logistics Workspace Product program
  • Supersedes: Material Receipt as the first shared transactional Golden Slice; parity guidance that did not require preservation of familiar Legacy surfaces

Context

The successor program needed explicit answers for scope, MK evidence, Process order, first transactional proof, current-vs-target authority, evidence depth, UI parity and engineering knowledge boundaries.

Decision

  1. Implement CTC and MK first. Inventory other families but defer implementation.
  2. Use current CTC repository/source as current-behavior baseline.
  3. Treat MK as same CTC Runtime/MySQL under CLIENT_ID = 2.
  4. Treat reference/mkmetal/** as historical/secondary evidence.
  5. Reconstruct Processes in dependency order: Platform -> Master Data -> Intake -> Booking/Fulfillment -> Operations -> Scale -> Inventory -> Transport/Equipment -> Settlement -> Integrations.
  6. Use Booking/Ocean Booking as first shared transactional Golden Slice.
  7. Start evidence with source/schema/docs, then authorized DB read-only, QA role/browser, critical Production read-only and operator/provider evidence.
  8. Preserve existing menus/pages/popups/familiar paths while adding Product surfaces; change defaults page by page.
  9. Keep CTC engineering knowledge project-local. A generic Knowledge Platform is a separate Product.

Consequences

  • NS0-003 approves the Booking Process contract and current source/schema/caller map.
  • NS0-002 supplies initial representative UI direction and NS0-004 supplies final Process-reconciled page contracts.
  • NS2-001 implements Booking rather than Material Receipt.
  • Material Receipt remains later.
  • NS4 implements compatibility and Product surfaces.
  • NS5 tracks menu/page/popup/default/route/writer separately.
  • NS6 owns removal after caller/usage zero.
  • Current source conflicts are not resolved by frozen docs, UI prototypes or AI inference.

Evidence Boundary

This decision is target authority. It does not prove current Runtime behavior, DB state, UI approval, target-role acceptance or cutover readiness.

---

Source: new-system/docs/decisions/0001-scope-booking-evidence-and-legacy-surface-transition.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.