CTC Logistics Workspace Product Reality

• Status: SOLE CURRENT CAPABILITY REALITY AND EXPOSURE OWNER
• Product scope: PRODUCT.md
• Phase order: ROADMAP.md
• Task context: tasks/ and git history

This document records what exists, what evidence supports it, whether it should remain and how far it may be exposed. It does not activate work. A validation cohort is evidence, not a module owner.

1. Status Axes

Axis	Values	Meaning
Disposition	KEEP, FIX, DEFER, RETIRE	Product decision
Evidence	NONE, SOURCE, FIXTURE, LOCAL_RUNTIME, QA_RUNTIME, TARGET_ROLE, ACCEPTED	What was actually proven
Exposure	HIDDEN, DIRECT_ROUTE_ONLY, MENU_VISIBLE, DEFAULT	How users may reach it
Task action	KEEP, FIX, ANALYZE, REMOVE	What a bounded slice may do

SOURCE or LOCAL_RUNTIME never implies target-role acceptance. A capability whose target exposure is lower than its current exposure is cleanup debt, not permission to add more UI.

2. Current Product Reality

catalog/product-reality.json is the sole current capability-status owner. Do not duplicate its evidence, blockers or exposure here; a validator rejects a second current-status table. A TARGET_ROLE or ACCEPTED capability must link through evidence_refs to the recorded revision, environment, scenario and result that support its claim.

3. Admission Rule

A new or expanded capability is rejected unless the selected Task document states one bounded result, capability actions, evidence target, reused source, explicit non-goals and surface changes. A public or package/module boundary additionally requires a previously accepted ADR under architecture/ARCHITECTURE_CHANGE_METHOD.md.

Generic platforms, all-screen completion, future-ready frameworks, empty packages/Workers and provider adapters without immediate consumers are invalid outcomes.

4. Tenant And Cohort Rule

CTC, MK, client 1/client 2 and other names may appear as historical evidence, compatibility aliases, configuration or validation cohorts. They may not create new backend packages, public exports, repositories, services, writers or business-policy branches.

Current backend paths and exports are tenant-neutral. Historical route/menu aliases may remain only as isolated compatibility inputs and never as owner names. Menu-derived profile selection remains active removal debt.

5. Machine-Readable Authority

The validator and active Task contract consume catalog/product-reality.json. This document owns only the admission and boundary rules.

---

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

In this section

Document	Contents
product-reality	Logistics Workspace Product Reality
requirements	Requirements Index
specifications	Specifications Index