Architecture Decision Records (ADRs)
This directory contains all Architecture Decision Records for the Hollowgate game project.
What is an ADR?
An Architecture Decision Record (ADR) captures an important architectural decision made along with its context and consequences. ADRs help us:
- Document the reasoning behind important decisions
- Understand the historical context of our architecture
- Avoid revisiting already-decided issues
- Onboard new team members faster
How to Use
- Copy the template from
../Templates/ADR-Template.md - Name your file:
ADR-XXX-short-title.md(e.g.,ADR-001-game-engine-selection.md) - Fill in all sections
- Update the index below
- Commit to the repository
Index of ADRs
Status Definitions
- Proposed: Under discussion
- Accepted: Decision has been made and is active
- Deprecated: No longer relevant but kept for history
- Superseded: Replaced by a newer ADR (link to the new one)
Categories/Tags
Use these tags to categorize your ADRs:
#architecture- Overall system architecture#gameplay- Gameplay mechanics and design#graphics- Rendering, visual effects#networking- Multiplayer, server architecture#performance- Optimization decisions#tooling- Development tools and pipeline#ai- AI systems and behavior#audio- Sound design and implementation#ui-ux- User interface and experience