Decisions are split by domain. Each agent's briefing indicates which files to read. When in doubt about where a decision belongs: if it constrains how we build, it's architecture. If it defines what we build, it's scope. If it defines what the player experiences, it's content or perception. If it defines how the team works, it's process.

Cross-domain decisions live in one file with cross-reference notes in related files. Split threshold: when any file exceeds ~350 lines, review whether it should split.

Domain Files

File	Domain	Decisions
architecture.md	Technical foundation	D-008, D-009, D-010, D-012, D-020, D-026, D-030, D-031
perception.md	Player observation	D-011, D-015, D-016, D-017, D-018, D-019, D-033
content.md	NPC, dialogue, templates	D-023, D-024, D-025, D-028, D-029, D-032, D-034, D-035, D-036, D-037
scope.md	Game concept, prototype	D-001, D-003, D-005, D-006, D-007, D-013, D-014, D-027, D-038, D-039
process.md	Team, workflow	D-004, D-021, D-022, D-040
questions.md	Open questions	Q-001 through Q-017
rejected.md	Rejected alternatives	R-001 through R-010

Querying Decisions

The SQLite database contains a decisions table synced from these files. Common queries:

# All active architecture decisions
db/connectors/sqlite-query "SELECT id, title FROM decisions WHERE domain='architecture' AND status='active'"

# Decisions without implementing tickets
make decisions-orphan

# Decision coverage by domain
make decisions-coverage

Adding a Decision

Edit the appropriate domain file
Follow the existing format (### D-NNN: Title heading)
Commit — the pre-commit hook runs decisions-sync automatically
Update relevant agent briefings if needed

Maintained by Qatux.