NS0-003 Open Decisions And Unknowns¶
- Status:
ACTIVE DECISION LEDGER - Task:
NS0-003 - Updated:
2026-08-15 - Rule: unknowns do not become policy, required fields, states, permissions or hidden UI assumptions.
Booking And Source Linkage¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-001 |
What triggers Booking creation for CTC and MK? | Current UI/API allow create; business trigger is not encoded. | target Process |
OD-NS0-003-002 |
What is the target Booking lifecycle? | No explicit Booking status owner; dates/flags are independent. | state/UI |
OD-NS0-003-003 |
Who owns Booking source linkage? | Booking and outbound Sales execution both synchronize pointers. | command owner |
OD-NS0-003-004 |
Are ports/rates Booking facts or source snapshots? | Current named extension stores them. | aggregate |
OD-NS0-003-005 |
Does invoice number belong on Booking? | Current create can allocate one. | settlement/documents |
OD-NS0-003-006 |
What do PL/invoiced/pierpass/clean-truck/not-in-use flags mean? | Independent compatibility flags. | state/read model |
OD-NS0-003-007 |
Cancel/delete/retire/reopen semantics? | Main API lacks one approved lifecycle. | commands |
OD-NS0-003-008 |
Which roles may create/update/clone/link/correct? | Distributed menu/module/route checks. | access |
OD-NS0-003-009 |
Is one-to-one Sales execution linkage required? | Application intent exists; DB uniqueness not proven. | linkage |
OD-NS0-003-010 |
Should Booking Save update Sales execution Consignee? | Current path can do so. | command boundary |
OD-NS0-003-011 |
What is profile/state-specific Next Action? | No approved composite state. | workspace |
OD-NS0-003-012 |
Final owner of CTC booking-list? | Current page/module ownership conflicts. | module/page |
OD-NS0-003-013 |
Timezone/precision by cutoff/date? | DB/browser representations vary. | temporal fields |
OD-NS0-003-014 |
Link correction/history model? | Pointers are overwritten. | recovery |
OD-NS0-003-015 |
Current tenant-2 config state? | Source defaults exist; rows not read. | profile facts |
Platform, Profile And Access¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-020 |
First-class tenant-to-profile binding? | Target profiles exist; universal runtime binding not proven. | effective contract |
OD-NS0-003-021 |
Which routes require strict tenant principal during coexistence? | Adoption is caller-specific. | platform migration |
OD-NS0-003-022 |
Target semantic role/action matrix? | Numeric CSV roles and distributed checks remain. | access |
OD-NS0-003-023 |
Which fail-open compatibility paths must remain? | Missing module/page mappings may allow. | cutover |
OD-NS0-003-024 |
What audit proves command completion? | Current evidence is fragmented. | command contract |
OD-NS0-003-025 |
File metadata/object cleanup policy? | DB metadata and object effect are separate. | attachments |
Master, Commercial And Intake¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-030 |
Party roles/types model? | T_COMPANY combines flags/type IDs. |
Party |
OD-NS0-003-031 |
Live references versus persisted snapshots? | IDs/names vary by record. | migration |
OD-NS0-003-032 |
First-class UOM/conversion registry? | No universal converter proven. | quantity/weight |
OD-NS0-003-033 |
Port/Terminal/Warehouse/Yard/Dock hierarchy? | Separate authorities exist. | Location |
OD-NS0-003-034 |
Ownership of mixed platform.master pages? | Current menu grouping crosses modules. | page map |
OD-NS0-003-035 |
Where may autocomplete create new values? | Caller policies vary. | forms |
OD-NS0-003-040 |
Commercial status transition matrix? | Operator-selectable labels. | commercial |
OD-NS0-003-041 |
Agreement link cardinality/direction? | Current UI/backend differ. | linkage |
OD-NS0-003-042 |
Post-execution Commercial edits? | Partial current guards only. | correction |
OD-NS0-003-043 |
First-class CTC Service Request? | Source is distributed. | intake |
OD-NS0-003-044 |
Appointment capacity/status policy? | Blocks exist; complete policy not reconstructed. | appointment |
OD-NS0-003-045 |
Reserved slots as policy or facts? | Company-name compatibility branches exist. | policy |
OD-NS0-003-046 |
Fulfillment creation trigger? | Current T_LOAD/T_TRANSLOAD paths vary. | fulfillment |
Operations And Scale¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-050 |
Plan versus actual execution owner? | T_TRANSLOAD/planner responsibilities overlap. |
operations |
OD-NS0-003-051 |
Canonical Assignment representation? | Route FINAL_DRAFT and typed ASSIGNMENT_DATA diverge. |
assignment |
OD-NS0-003-052 |
Loader/Office confirmation policy? | Current capture paths vary. | execution |
OD-NS0-003-053 |
Work/Break/Idle/Clock Out owner? | Planner and Staff Time overlap. | workforce |
OD-NS0-003-054 |
Terminal Undo/Correction boundary? | Current compensation is partial/selected. | recovery |
OD-NS0-003-055 |
Scale precision/UOM/rounding? | Current integer/decimal usages vary. | scale |
OD-NS0-003-056 |
Reweigh/correction/void/reversal semantics? | Selected event adapters exist. | scale lifecycle |
OD-NS0-003-057 |
Device/manual/offline provenance? | Mixed current adapters. | hardware |
OD-NS0-003-058 |
Weight consequence reconciliation owner? | Consumers are distributed. | downstream |
Inventory And Allocation¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-060 |
Receipt confirmation trigger? | Current UNLOADED adapters can materialize lots. |
receipt |
OD-NS0-003-061 |
Lot status transition policy? | OPEN/PARTIAL/HOLD/CLOSED appear. | lot |
OD-NS0-003-062 |
Quantity versus weight balance policy? | Both persist; writes differ. | inventory |
OD-NS0-003-063 |
Placement correction/physical mismatch owner? | Mirrors and placement rows coexist. | placement |
OD-NS0-003-064 |
Split/merge/hold/reopen commands? | Complete public authority not proven. | correction |
OD-NS0-003-065 |
First-class Cost Layer? | Rate snapshots exist, landed-cost aggregate does not. | costing |
OD-NS0-003-066 |
Partial/full Allocation policy? | Current UI supports partial weight. | allocation |
OD-NS0-003-067 |
Allocation quantity/UOM conversion? | Weight decrements immediately; quantity does not. | allocation |
OD-NS0-003-068 |
Reverse/Unallocate owner? | No general public command found. | recovery |
OD-NS0-003-069 |
Allocation idempotency identity? | No durable request token found. | unknown result |
Transportation, Yard And Equipment¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-070 |
Shipment/TransportLeg identity and creation trigger? | No first-class current aggregate found. | transportation |
OD-NS0-003-071 |
Internal/external/hybrid/customer execution policy? | CTC internal is detailed; MK external lifecycle incomplete. | composition |
OD-NS0-003-072 |
Map T_DELIVERY states to target Leg states? |
Current Delivery state is compatibility-specific. | state |
OD-NS0-003-073 |
Durable Yard queue correlation to Delivery/Leg? | Current correlation is indirect. | orchestration |
OD-NS0-003-074 |
Queue-after-clear idempotency/duplicate completion? | Auto-completion and duplicate evidence risk exist. | recovery |
OD-NS0-003-075 |
Pull-Out closing orchestration? | BMS save and YMS completion are separate requests. | partial state |
OD-NS0-003-076 |
Arrival versus parking/Yard assignment semantics? | Current labels/actions overlap. | UI/state |
OD-NS0-003-077 |
Driver/Vehicle/Chassis assignment cardinality? | Current records/mirrors do not define target policy. | equipment |
OD-NS0-003-078 |
What exactly proves Port Return? | Return delivery mutates load/equipment/time/Yard. | lifecycle |
OD-NS0-003-079 |
requiresContainerReturn source/default/override? |
Current behavior is route/profile-specific. | policy/fact |
OD-NS0-003-080 |
External carrier milestone set and proof? | First-class current milestone store not found. | external leg |
OD-NS0-003-081 |
Delivery Undo compensation? | Current Undo leaves child effects possible. | recovery |
OD-NS0-003-082 |
Hardcoded Yard Driver roster retirement? | Named users remain in current helper. | role/config |
OD-NS0-003-083 |
Physical/system mismatch correction owner? | Delivery, Yard and Equipment can diverge. | reconciliation |
OD-NS0-003-084 |
Container/Chassis lifecycle states? | Current states are distributed. | equipment |
OD-NS0-003-085 |
CTC/MK transport role/action matrix? | Not runtime verified. | access |
OD-NS0-003-086 |
Provider retry/outbox contract? | Telegram/QBO/events use mixed boundaries. | effects |
Remaining Families¶
| ID | Question | Current source fact | Blocks |
|---|---|---|---|
OD-NS0-003-090 |
Service charge versus trade settlement owners? | Current BMS/Commercial sources remain to reconcile. | settlement |
OD-NS0-003-091 |
Document lifecycle and source snapshots? | File/document/provider sources remain. | documents |
OD-NS0-003-092 |
Email/message/accounting/AI/job effect ownership? | Current effects are distributed. | integrations |
Required Evidence Queue¶
E1 live MySQL schema/index/status/value distribution
E2 tenant 1/2 representative records and relation mismatches
E3 role/menu/API positive and denied paths
E4 CTC operator Booking/Transload/Driver/Yard/Return walkthrough
E5 MK Commercial/Inventory/Allocation/external-carrier walkthrough
E6 current caller inventory and dynamic reachability
E7 provider/file/device failure and recovery
E8 physical/system mismatch and correction examples
E9 target business decisions
Decision Discipline¶
- current source establishes current behavior, not desired policy;
- historical documents are secondary to current source;
- target business meaning requires explicit approval;
- missing evidence remains unverified;
NS0-004receives only approved facts and named open questions.
---¶
Source:
new-system/docs/reconstruction/NS0-003_OPEN_DECISIONS_AND_UNKNOWNS.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.