Skip to content

NS0-002 To NS0-003 Handoff

  • Status: ACTIVE HANDOFF
  • Date: 2026-08-14
  • From: NS0-002 — USER-APPROVED INITIAL UX DIRECTION
  • To: NS0-003 — ACTIVE PROCESS RECONSTRUCTION
  • Decision: ../decisions/0006-initial-ux-direction-approval.md

1. Preserve During Reconstruction

compact/high-density Legacy-compatible Office surfaces
familiar menu/page/popup entry and return behavior
H/Cobalt for CTC
K/Indigo for MK
identical H/K non-color metrics
workspace-tab direction
concise UI copy
shared Form/Attachment components

Do not redesign these silently during Process discovery. Record a conflict or required correction for NS0-004.

2. Approved Form Catalog Sequence

Text & Number
Autocomplete
Schedule
Selection
Notes & Files
Field State Matrix

The primary catalog must keep Autocomplete directly below Text & Number and must demonstrate exact-match, creatable, dependent and multiselect patterns.

3. Process Questions To Resolve

Booking

  • trigger and authoritative identity;
  • tenant uniqueness and duplicate behavior;
  • draft/confirmed/cancelled/corrected/reopened semantics;
  • required/optional/default fields by role/profile;
  • Sales Order and service-source linkage;
  • explicit Fulfillment/Shipment/Equipment/Document boundaries;
  • timeout, correction, rollback and authoritative readback;
  • current menu/page/popup/direct-route compatibility.

Temporal and Appointment

  • precision and timezone for each business fact;
  • date-only facts versus date-time facts;
  • Appointment time-block source, capacity, status and correction.

Media

  • Process-owned media groups;
  • who may reorder or reassign groups;
  • whether any group needs wraparound lightbox navigation;
  • authoritative sequence/readback and unknown-result recovery.

Workspace Tabs

  • maximum open tabs;
  • persistence and restore duration;
  • stale-data refresh on reactivation;
  • dirty-state close rules;
  • browser-window coordination and permission revalidation.

4. Evidence Priority

current CTC source/schema/runtime
-> authorized MySQL read-only evidence
-> current role/browser/Wiki/runbook/provider evidence
-> reference/mkmetal historical evidence
-> frozen Legacy documents/Tasks
-> inference

Current source establishes current behavior. Target Process changes require explicit approval.

5. First NS0-003 Work Packet

1. Source Registry for CTC/MK/Booking/UI/media source families
2. CLIENT_ID 1/2 current-behavior map
3. reference/mkmetal disposition
4. Process candidate/deferred inventory
5. Booking menu/page/popup/API/schema/caller map
6. Booking state/command/query/transaction/recovery candidate
7. CTC/MK shared-versus-policy-versus-fact matrix
8. exact NS0-004 UI correction manifest

6. Effect Boundary

This handoff authorizes documentation and read-only reconstruction work only. Runtime, DB, config, route, writer, provider, service, Wiki publication and physical effects remain unauthorized.

7. Additional User Visual Direction — 2026-08-16

The accepted B · Contextual Workspace direction remains the base and is elevated to B+ · Contextual Precision Workspace.

Binding input:

The additional direction requires a premium, current and intentionally crafted operational Product with richer purposeful motion. It preserves dense Office surfaces, Field speed, H/K color-only variation, concise copy, accessibility, explicit state and authoritative recovery.

NS0-003 must record Process constraints that affect visual hierarchy, real-time updates, exceptions, state transitions, recovery and field behavior. It must not silently redesign representative surfaces or invent Process meaning.

The shared UI acceptance package must use actual high-fidelity CTC/MK representative surfaces, motion storyboards, reduced-motion variants and realistic operational-density evidence. This addition does not authorize Runtime changes by the reconstruction Task.

Current execution applies this reference to the shared NS1-002 UI contract and actual Foundation/Booking pages. It does not reopen the approved direction or authorize another standalone prototype.

---

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