Architecture decision records
This directory records decisions that define Forge’s architectural baseline. A decision is immutable once accepted: material changes require a new ADR that supersedes the old one.
| ADR | Decision | Status |
|---|---|---|
| 0001 | Repository layout and ownership | Accepted |
| 0002 | One template in v1 | Accepted |
| 0003 | npm workspaces | Accepted |
| 0004 | Safe template materialization | Accepted |
| 0005 | Publishable, integration-neutral content model | Accepted |
| 0006 | Independent package versioning | Accepted |
| 0007 | Isolated Forge project website | Accepted |
| 0008 | Independent frontmatter lint package; extends 0003/0006 | Accepted |
| 0009 | Retain npm after Vite+ evaluation | Proposed |
| 0010 | Retain locked template delivery | Proposed |
| 0011 | Retain static templates and typed CI authoring | Proposed |
| 0012 | Retain Forge release orchestration after evaluation | Proposed |
These records implement the Forge roadmap, beginning with FGE-001, and follow the project roadmap represented by their linked work items.
See the architecture guide for the current system map, contract boundaries, data flow, and verification layers. Maintainer procedures are documented separately in the maintainer guide and release guide.