Logistics Workspace Decisions¶
ADRs record the background, alternatives, reasoning, impact, recovery and supersession of a durable decision. The current phase and its exit conditions are in ROADMAP, the scope, progress and verification of work are in the Task documents and git history, and the current rules are owned by the relevant specification.
Browse By File¶
This links the decision files in this directory. Being listed here does not mean a decision is currently valid, implemented or verified at runtime. For its applied scope and later changes, check each document's own state, current application note and supersession relation.
| Decision | Source |
|---|---|
0001 |
Booking evidence and Legacy transition scope |
0002 |
UI direction before process and foundation implementation |
0003 |
UI copy, required input and temporal fields |
0004 |
Media attachment and temporal input layout |
0005 |
Photo ordering and group lightbox |
0006 |
Initial UX direction approval |
0007 |
Page tests, in-app Wiki and change history |
0008 |
Foundation-first Booking development scope |
0009 |
Modernisation, plugin reuse and greenfield boundary |
0010 |
Foundation quality before feature expansion |
0011 |
UUID-first identity and dual-key coexistence |
0012 |
Value-first foundation delivery |
0013 |
Five-phase modular product development |
0014 |
Continuous Phase 1 and 2 development |
0015 |
Architecture change control |
0016 |
Six-phase delivery and tenant productisation |
0017 |
Tenant runtime authority |
0018 |
Inbound, receipt and cancellation authority |
0019 |
Outbound allocation authority |
0020 |
Settlement source reconciliation authority |
0021 |
Tenant-neutral database adapter naming |
0022 |
Wiki runtime owner |
0023 |
Role, screen and portal boundary |
0024 |
Platform route and client boundary split |
0024 |
Tenant policy and Trade writer authority |
0025 |
Shared icon system |
0026 |
Path rename from tooling to scripts |
0027 |
Development sequence on a tenant administration foundation |
0028 |
Persistent release and runtime execution receipt contract |
0029 |
Bounded structure and format debt transition for UUID candidates — proposed |
Citation And Change¶
Cite a decision by an exact file link, not by number alone. The two 0024 files are different
decisions, so their existing names and numbers are preserved and the title distinguishes them. When
choosing a new ADR number, check the numbers already used.
When a decision changes, leave the reasoning, the alternatives reviewed, the impact and the retained/superseded scope on the relevant ADR, and update the current rules in the owning specification. Link onward so that a superseded decision can be reached from its successor or from the current rules. The approval date and past evidence preserve the scope they were given and are not copied into the ADR as current Task state. Do not create a new ADR just to record a routine edit result or a verification summary.
Source:
new-system/docs/decisions/README.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.