Architecture Decision Records¶
F-Layer uses Architecture Decision Records for decisions that materially affect architecture, public contracts, compatibility, security boundaries, persistence, provider interfaces, or extension design.
Naming¶
0000-template.md
0001-short-decision-name.md
0002-another-decision.md
ADR numbers are stable once assigned.
Lifecycle¶
- Record the context and decision before or together with implementation.
- Link the implementation Feature/Task and relevant PRs.
- Describe consequences and rejected alternatives.
- Do not silently rewrite an accepted ADR to represent a different decision; supersede it with a new ADR when necessary.
Use 0000-template.md as the starting point.
Accepted decisions¶
| ADR | Decision |
|---|---|
| ADR 0001 | Separate desired configuration from owned resource state |
| ADR 0002 | Establish a read-only provider boundary using explicit folder scope |
| ADR 0003 | Safe Diagnostics with Explicit Observation Boundaries |
| ADR 0004 | Static installed-package documentation platform |
| ADR 0005 | Durable owned resource lifecycle |
| ADR 0006 | Scoped Yandex lifecycle mutations and explicit boot disk ownership |
| ADR 0007 | Explicit secure gateway profile and owned artifacts |
| ADR 0008 | Reproducible distributions and explicit owner publication |
| ADR 0009 | One source for distribution and runtime versions |
| ADR 0010 | Explicit repository documentation completeness |
| ADR 0014 | Milestone-scoped releases and human-readable changelogs |
| ADR 0015 | Explicit source-bound AI translation review |
Release history and the human-readable changelog follow ADR 0014.