approvedcompleteApache-2.0
Template layout: frontend/ + backend/, nothing else to explain
019-two-directory-layout
After spec 018 sheds the toolchain payload, the remaining tree is restructured into two directories a developer understands at first glance: frontend/ (the SPA, one directory per flavor lifecycle) and backend/ (every Encore.ts service plus the shared lib and CoreLedger). Decided 2026-07-14, chosen over client/apis and app/services because frontend/backend is the pair with zero ambiguity. All Encore.ts concerns co-locate under backend/, which is what makes the chassis easy to reason about; everything else at the root is contract, packaging, or governance. Lands before statecraft spec 002 so the first template consumer imports the simple shape.
- Depends on
- Establishes
- backend/ (directory)
- frontend/ (directory)
- Sections
- 019: Two-directory layout
- 1. Target tree (stamped-app view)
- 2. Movement map
- 3. Risks the implementer must verify first
- 4. Acceptance
- 5. Out of scope
- 6. Status
- Source
- specs/019-two-directory-layout/spec.md @ dc4c9237e12aas of 2026-07-21 ยท shard ed4a8b9ca0ab