Skip to content

Decision 0006 — Initial UX Direction Approval And NS0-003 Activation

  • Status: ACCEPTED
  • Date: 2026-08-14
  • Owner Task: NS0-002
  • Successor Task: NS1 Foundation, then NS2-001 Booking
  • Restriction delta: RD-000 / NONE
  • Runtime effect: NOT PERFORMED

Decision

The user approves the initial Logistics Workspace UX direction. Execution proceeds to Foundation and then the first real Booking slice under Decision 0008.

Approved direction:

Legacy-compatible Office pages
= compact/high-density and familiar

New Product pages
= guided Process stages + clear Next Action

CTC theme
= H / Cobalt Precision

MK theme
= K / Indigo Studio

H/K difference
= semantic colors only

The App Shell uses semantic workspace tabs as the initial direction. The same record is reused rather than opened repeatedly in duplicate app tabs.

Shared Form Catalog Order

1. Text & Number
2. Autocomplete
3. Schedule
4. Selection
5. Notes & Files
6. Field State Matrix

Autocomplete remains visible in the main Form Catalog directly below Text & Number. It is not placed in a separate lab or secondary navigation.

Existing Accepted UI Rules

  • no unrequested descriptive subtext;
  • required fields use a danger-colored * next to the label;
  • Date/Time use the shared TemporalField family;
  • Appointment uses the shared DatePicker plus status-aware TimeBlockPicker;
  • native browser file-picker copy is hidden behind the shared FileAttachmentField;
  • photos use the shared KJPhoto/PhotoAttachmentTool capability;
  • Photo Sequence is authoritative, while alternate sorts persist only through explicit Save order;
  • photo preview is a group-scoped keyboard lightbox;
  • mobile validation remains deferred and is not reported as passed.

Approval Boundary

This decision approves initial visual and interaction direction only.

It does not approve:

Booking Process semantics
final field requiredness/defaults
role/action authorization
transaction/effect boundaries
Runtime implementation
DB migration/data change
Production route/writer cutover
Legacy retirement

Those items are resolved for the Booking slice as needed during Foundation and NS2-001. Broad Process reconstruction remains deferred until Booking proves the implementation pattern. See Decision 0008.

---

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