Decision 0012 — Value-First Integrated Product Delivery¶
- Status:
ACCEPTED RATIONALE / NOT EXECUTION AUTHORITY - Authority:
RATIONALE_ONLY - Date:
2026-08-20 - Current Product:
../PRODUCT.md - Current Phase-1 scope:
../ROADMAP.md - Current execution:
../EXECUTION.md
Context¶
The program first drifted toward horizontal Foundation work with high code/review cost and low operator value, then over-corrected toward a minimal Booking CRUD slice that could not prove the reusable Product Core.
Booking was chosen because it crosses identity, tenant/access, dense UI, UUID data, files, images, documents, AI/provider, recovery, accessibility and performance in one real operating context.
Decision Rationale¶
Deliver through bounded vertical slices:
one operator result
-> only the supporting Foundation required now
-> actual read/write/provider evidence
-> measured correction
-> next capability
A new abstraction requires an immediate real consumer in the same slice. Empty packages, registries, workers, queues, event buses, repositories and generic quality frameworks are not deliverables.
Phase 1 must prove an integrated Booking Product Core, including file/photo, Packing/Confirmation and reviewed AI instruction intake. These capabilities are not optional polish because they establish reusable patterns needed by MK.
Retained Technical Intent¶
- UUID-only canonical identity;
- one semantic owner per record/command/query/transaction/effect;
- explicit object/relation and source/render/output/provider boundaries;
- copied modernization assets only through bounded adapters;
- no monolithic copied editor as target authority;
- AI suggestions never auto-save;
- actual-role evidence and measurable superiority over Legacy.
Current Authority¶
This decision explains why the program uses value-first integrated delivery. It does not own current scope, Task IDs, order, status or stage.
Use:
PRODUCT.mdfor Product outcome;ROADMAP.mdfor phase order and exit gates;ROADMAP.mdfor Phase-1 scope;EXECUTION.mdfor exact live Task order;- the exact Task and manifest for slice scope.
Immutability¶
Do not add another “latest amendment” to this record. A changed direction creates a new superseding decision and updates the current owner documents.
---¶
Source:
new-system/docs/decisions/0012-value-first-foundation-delivery.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.