Architecture Decision Records¶
One decision per file. Format: context → decision → consequences, with an explicit status in the header.
Statuses: open (undecided) · proposed (candidate, pending validation) · accepted (in force) · superseded by ADR-XXXX.
Index¶
| ADR | Title | Status |
|---|---|---|
| 0001 | Build our own engine instead of adopting Copier/Cookiecutter | ✅ Accepted |
| 0002 | The engine is agnostic; knowledge lives in the manifest | ✅ Accepted |
| 0003 | Templates compile; three transformation mechanisms | ✅ Accepted |
| 0004 | Verification runs in containers, declared in the manifest | ✅ Accepted |
| 0005 | Answers file from day one; three-way-merge updates postponed | ✅ Accepted |
| 0006 | Engine implementation language: Go | ✅ Accepted |
| 0007 | Minimal grammar for tpl: directives |
✅ Accepted |
| 0008 | Project name: Templetry | ✅ Accepted |
| 0009 | Repo creation on any forge (multi-forge) | ✅ Accepted |
| 0010 | Engine execution model: web backend | ❌ Superseded by 0012 (desktop) |
| 0011 | Catalog model: parents, forms and combinable features | ✅ Accepted |
| 0012 | Desktop app with Wails, engine embedded | ✅ Accepted |
| 0013 | Declare v1.0.0 across all components (soak window waived) | ✅ Accepted |
| 0014 | Lazy pieces: decoupled units with their own lifecycle | ✅ Accepted |
| 0015 | Multi-forge foundation: BYOR and source schemes | ✅ Accepted |
| 0016 | Common pieces: one idea, many implementations | ✅ Accepted |
| 0017 | Template taxonomy: three axes, one closed vocabulary | ✅ Accepted |
| 0018 | Environment profiles: three names, each ecosystem's own mechanism | ✅ Accepted |
| 0019 | The engine moves to Apache License 2.0 | ✅ Accepted |