NS0-003 Transportation And Equipment UI Reconciliation Manifest¶

Status: PROCESS-TO-UI INPUT FOR NS0-004
Source baseline: 1529bce22ae39c7c2c11e1b9b07e457e1e4c4355
Runtime implementation: NOT STARTED

1. Compatibility Surfaces To Preserve¶

Driver Operation
Yard Dispatch
Yard Instruction
Yard Closing
Yard Map
Delivery/Dispatch Office surfaces
Container/Chassis reference surfaces
Booking and outbound-order handoffs

Preservation means familiar route/task access during coexistence, not copying every accidental state merge.

2. Required Product Surface Corrections¶

Internal Dispatch Workspace¶

Must show independent facts:

Delivery/Leg state
Driver assignment
Vehicle/equipment
current physical location
Yard prerequisite/pending work
proof/evidence
provider result

One status badge must not merge them.

Driver Field Task¶

Must distinguish:

Start transport
Arrival/location signal
Finish delivery
Parking request
Parking assignment
Physical parking
Yard pending
Container return

Undo must state its actual compensation boundary.

Yard Dispatch¶

Must preserve compact queue review and clearly distinguish:

planned assignment
active claim
actual physical location
deferred queue-after-clear
completed instruction

Equipment Lifecycle¶

Must show:

Booking intent
assigned container/chassis
equipment load state
Yard position
transport association
return requirement
port-return evidence

Booking quantity intent is not assigned equipment.

External Carrier Workspace¶

May use milestone/reference presentation, but must not show internal Driver/Truck controls when disabled.

3. App Work Tabs¶

Recommended semantic tab keys:

shipment:<id>
transport-leg:<id>
delivery:<id>
yard-queue:<id>
equipment:<id>
container-return:<id>

A tab key is navigation state, not business state.

4. Required Runtime Evidence When Implemented¶

Each canonical page requires:

page-specific Playwright script
stable scenario IDs
runtime screenshots
evidence manifest/checksum
in-app User Wiki article
contextual Help mapping
append-only page CHANGELOG

This reconstruction packet creates none of those artifacts because no Runtime page is created or modified.

---¶

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