CTC Product Platform And Documentation Context History¶

Status: CURRENT APPEND-ONLY DECISION HISTORY
Effective date: 2026-08-14
Current direction owner: CTC_PRODUCT_PLATFORM_AND_DOCUMENTATION_CONTEXT.md
Purpose: record material additions, corrections, supersessions and authority changes without expanding the current Context into multiple files
Does not own: current direction, live Roadmap status, Runtime facts, Task completion or execution authorization

Use Rules¶

Read the current Context first.
Read this file only when decision provenance, supersession or historical interpretation is material.
Append a dated entry when current meaning, priority, authority, prohibited interpretation or execution boundary changes.
Git history preserves exact former wording; this file is a navigable decision summary.
Historical status labels do not reactivate work.
Former appendix paths are compatibility pointers until inbound links are migrated.

Entry Format¶

## YYYY-MM-DD — Title

- Trigger:
- Previous interpretation:
- Decision:
- Current Context sections:
- Supersedes:
- Evidence/research:
- Repository/effect impact:

2026-07-30 — Product, Documentation And Repository Reset¶

Trigger: Task wrappers, generated status, Harness expansion and document hierarchy displaced Product direction.
Decision: one modular multi-tenant Product; Objective equals Phase; Roadmap owns live status; Product/Design/Development receive canonical owners; research is not completion; Process meaning precedes templates; verification remains evidence-scoped.
Current Context sections: 1-6, 9, 17-19, 21-24.
Repository/effect impact: documentation/planning only unless separately authorized.

2026-08-01 — Basic Operations Continuity Before Broad MK Expansion¶

Trigger: Client 2 demo exposed saved records not visible, excessive blocking inputs and disconnected workflow.
Decision: minimum necessary input, one primary action, stable ID, authoritative readback, visible result and explicit next work precede broad expansion; optional effects do not undo primary result.
Current Context sections: 4-8, 21.

2026-08-02 — Code-Composition Cleanup Distributed To Existing Owners¶

Trigger: giant helpers/global state/type dispatch/query ownership were being proposed as a separate catch-all optimization Task.
Decision: distribute context, Process, backend, frontend and performance responsibility to P4/P5/P6/P7/P9; caller-zero and measured performance remain distinct.
Current Context sections: 14-15, 19.

2026-08-03 — P1 Correction, Live-Tenant Safety And Wiki Synchronization¶

Trigger: P1 completion was overstated and a broad role guard caused Client 1 outage.
Decision: require source/consumer accounting, tenant × role × page/API/action evidence, controlled target-role verification, minimum-input UX and separate internal/user Wiki owners.
Current Context sections: 7-9, 17, 21-22.

2026-08-04 — Current-Code Review Disposition And Tenant Parameterization¶

Trigger: structural findings were being treated as equal-priority defects or automatic rewrites.
Decision: numeric tenant business/UI branches prohibited; bounded compatibility may remain; generic mutation/auth/KJDatabase replacement are owning-Task decisions; continuity precedes neatness.
Current Context sections: 7, 14-15, 19.

2026-08-05 — Shared Codex Session And Non-Developer UI Direction¶

Trigger: /codex design accumulated sharing/takeover/developer-console concepts not required by staff.
Decision: fixed account/session-visibility contract, simple non-developer UI, no separate Workspace Product or generalized ACL.
Current Context section: 20.

2026-08-07 — Phase And Operational Tracks, Executable Tasks And Branch Parity¶

Trigger: Phase work drifted while field fixes expanded into architecture changes.
Decision: separate Phase Transformation/Operational Delivery; require executable Tasks/visible completion; one writer per authority; preserve qa/master parity; approve Next.js full-stack direction.
Current Context sections: 18-22.

2026-08-07 — Explicit React + Next.js Target¶

Trigger: wording could imply Next.js without explicit React or React adoption remained TBD.
Decision: React + Next.js App Router + Tailwind, framework-independent TypeScript application/domain, separate durable Node worker, MySQL first and PostgreSQL later.
Current Context sections: 10-13, 19.

2026-08-07 — Process Architecture, Wiki Projection And Migration Readiness¶

Trigger: page/API documentation did not explain operating model or migration units.
Decision: use L0-L5 hierarchy, P6 owns Process/M0-M5 readiness, P8 owns user projection, and P5/P7/P12 consume accepted meaning.
Current Context sections: 6, 9, 17-19.

2026-08-07 — Rebuild-Grade Documentation¶

Trigger: documentation was framed as a substitute for unavailable Runtime testing.
Decision: document Product, Process, data, interface, UI, effect and migration meaning deeply enough to rebuild while keeping documentation/evidence independent.
Current Context section: 17.

2026-08-08 — Phase Hold And Documentation-Only Lane¶

Trigger: user paused Phase implementation while permitting source/document reconciliation.
Decision: recorded Phase hold, documentation lane and explicit Operational request requirement. This status was later superseded by the 2026-08-12 all-Phase activation recorded in Roadmap.
Current status owner: Roadmap.

2026-08-10 — Work Graph Execution Governance¶

Trigger: context loss, incomplete fan-in, omitted inputs, broad restarts and false completion.
Decision: every request classifies LINEAR/WORK_GRAPH; manifests, bounded discovery, one writer, independent verification, invalidation and calculated closure; live graph state remains outside Git.
Current Context section: 18.

2026-08-10 — Live-Operation Continuity And Restriction Control¶

Trigger: AI-assisted changes added required inputs, validation and access restrictions causing outages.
Decision: default RESTRICTION DELTA = NONE; unknown does not become deny; security/integrity rationale is not self-authorization; preserve allow paths and primary results.
Current Context section: 8.

2026-08-11 — Code Simplification And Abstraction Quality¶

Trigger: unnecessary-function cleanup needed a safer heuristic.
Decision: short_body and low fan-in are metadata; review distinct contracts/minimum exposure/caller mechanisms/dead-code cause/semantic duplication; use behavior-sensitive tests; P9 owns measured performance.
Evidence: docs/research/code-quality/2026-08-11/CTC_CODE_SIMPLIFICATION_GUIDELINE_REVIEW.md.
Current Context section: 15.

2026-08-11 — Context Consolidation¶

Trigger: many Context appendix files made current direction difficult to identify.
Decision: one canonical Context, one append-only History, former appendices as compatibility pointers only.
Supersedes: multi-file current Context/addendum model.
Repository/effect impact: documentation/governance only.

2026-08-11 — Production-Safe Deployment, DB Migration Confirmation And Wiki Sync¶

Trigger: source could reach master before required DB migration; Wiki could drift; Production already auto-pulls master.
Decision: QA_COMMIT_PUSH + MASTER_MERGE + parity is one set; classify DB dependencies before qa push; require confirmation for absent/unknown migration; same-delivery bounded Wiki sync; two-minute auto-pull; no routine PHP service restart/manual pull.
Current Context section: 22.

2026-08-11 — New Wiki Slug Standing Authorization¶

Trigger: user authorized bounded new Wiki pages without another per-page confirmation.
Decision: bounded new stable slug is standing-authorized with exact authority/visibility/rollback/readback; rename/retire/delete/visibility/navigation/bulk remain explicit decisions.
Current Context sections: 17 and 22.

2026-08-11 — Repository Cleanup Completion Correction¶

Trigger: P5 completion was reported while numeric tenant branches, legacy paths, symbol/caller review, giant owners and broad cleanup remained.
Decision: safety parity is a Gate, not structural result; cleanup remains cross-phase; actual replacement/retirement and accepted residual matrix required.
Current Context sections: 7, 14-15, 19, 21.

2026-08-11 — Shared Backend Core And Tenant Extension Direction¶

Trigger: user clarified profile-specific frontend may differ while backend authority remains common.
Decision: one canonical backend owner, profile/capability/policy composition, bounded additive extension only, no duplicated writer/transaction or speculative plugin framework.
Current Context sections: 3, 5-7, 14.

2026-08-13 — Close CTC P3 Scope And Separate Control Tower Accounts¶

Trigger: Control Tower and CTC responsibilities are separate.
Decision: close P3 for CTC execution; retain historical boundary inputs; Control Tower account/session lifecycle remains outside CTC Tasks/roles/deployment authority.
Current Context sections: 19-20.

2026-08-13 — UUID-First Tenant And Entity Identity Direction¶

Trigger: user clarified T_CLIENT.UUID can be the exact tenant-owned TENANT_ID and all persistent keys ultimately move to UUID semantics.
Decision: one canonical tenant UUID; numeric client/entity IDs and foreign keys are migration compatibility; P4 owns tenant migration, P12 entity waves, P11 starts after UUID-first stabilization.
Current Context sections: 7.1, 10-12, 22.

2026-08-14 — Greenfield Full-System Reconstruction With Incremental Production Cutover¶

Trigger: repeated legacy-core changes caused cross-page outages, and the user clarified that “page-by-page” means sequential Production opening rather than sequential page development.
Previous interpretation: P12 references/capability waves could be read as one page implemented, released and completed before the next page was developed; “no big-bang rewrite” could be read as prohibiting a clean full-system reconstruction codebase.
Decision:
approve greenfield full-system reconstruction as the development model;
keep existing MySQL authoritative during reconstruction;
keep legacy PHP as a compatibility/fallback Runtime until accepted cutover and caller-zero;
separate development state from Production cutover state;
expose canonical routes page-by-page through readiness/UAT/canary/rollback;
migrate mutation authority command/use-case-by-command/use-case with exactly one writer;
prohibit big-bang Production exposure, dual writers and simultaneous PostgreSQL transition;
restructure P12 into P12-001 architecture, P12-002 Runtime/UI foundation, P12-003 shared transaction foundation, P12-004 full reconstruction, P12-005 incremental cutover and P12-006 retirement.
Current Context sections: 10-12, 19, 22-23.
Supersedes: any interpretation that P12 requires page-by-page development or forbids a greenfield target structure. It does not authorize Runtime, DB, route, service or Production effects.
Evidence/detail: docs/tasks/P12-001/GREENFIELD_RECONSTRUCTION_AND_INCREMENTAL_CUTOVER_CONTRACT.md.
Repository/effect impact: canonical documentation and Task portfolio only; DB dependency NOT_REQUIRED, Wiki impact NOT_APPLICABLE, Runtime NOT_RUN.

2026-08-14 — CTC/MK Composable Operating Model And Shared UI Design System¶

Trigger: the full reconstruction needs durable CTC/MK business composition and a reusable UI system so every page is not redesigned independently.
Previous interpretation: shared backend could be mistaken for one identical workflow/UI, while profile-specific screens could drift into customer forks or page-local design systems.
Decision:
one shared domain/application authority with versioned profiles, named capabilities, typed policies and persisted record facts;
shared atomic capability != identical end-to-end workflow;
CTC is execution-first and MK is commercial-order/inventory/margin-first;
Commercial/Fulfillment, Inventory Lot/Cost Layer, Allocation, Transport/Container, Service Billing/Trade Settlement and independent states remain separated;
new React UI uses tokens -> primitives -> business patterns -> page templates -> profile composition -> effective surface/page contract -> component catalog;
CTC/MK may use profile-native page/read-model composition while sharing design language and backend authority;
every released major surface requires measurable user improvement and authoritative save/readback.
Current Context sections: 3-6, 12-14, 17, 21.
Evidence/detail: docs/tasks/P12-001/README.md and linked architecture contracts.
Repository/effect impact: documentation/Task/design target only; no current UI, Runtime, DB, provider, Wiki or deployment effect.

---¶

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