Governance
The review/approval processes major technical and data decisions pass through — see SYSTEM_DESIGN_ALIGNMENT.md section 10.1.
Why we need this / what value this brings
Without any process, major technical decisions (new vendor, new DB) get made informally and are hard to trace or reconsider later.
When to use this
Mostly aspirational at Localz's current team size — worth adopting formally once there's more than one decision-maker.
How to use or implement this
Start lightweight: log major decisions somewhere durable (already happening via LocalzTodos/NOTES.md) before building a formal review process.
Subtopics
Research questions
- At Localz's current single/small-team stage, most of this is aspirational — worth revisiting once there's more than one decision-maker.
Empty folder — drop notes, links, and findings here as you research.