Architecture Decision Records

• 1. Split user and business interfaces by default
• 2. Decouple with events
• 3. Use Git commits to explain our work
• 4. Store time and actor information in data
• 5. For release, prioritise consistency over availability
• 6. Treat Delius NSIs as collectors, not owners of interventions
• 7. Integrate performance testing into the continuous integration pipeline
• 8. Measure feature impact with dbt and QuickSight
• 9. Validating user-given custody data with prison data

This page was last reviewed on 5 March 2025. It needs to be reviewed again on 5 March 2026 by the page owner #interventions-dev .

This page was set to be reviewed before 5 March 2026 by the page owner #interventions-dev. This might mean the content is out of date.