Architecture decision record template

Save as docs/adr/NNNN-short-title.md in your repository.

# NNNN. Title in the form of a short decision

- Status: Proposed | Accepted | Rejected | Superseded by [NNNN](NNNN-title.md) | Deprecated
- Date: YYYY-MM-DD
- Deciders: names or roles
- Decided by: team | SDA name | TDA | TGB
- Business capabilities: e.g. BC05 Issue licences and permits
- Technology capabilities: e.g. Manufacturing & Delivery (Business)
- Guardrails: e.g. GR-HOST-01 (met), GR-DEV-01 (departure - see below)
- Advice sought from: e.g. platform team, security architect, teams affected

## Context

What is the problem or opportunity? What constraints and forces are at play
(user needs, policy, deadlines, existing systems, skills, cost)? Write for someone
who was not in the room.

## Options considered

### Option 1: strategic option from the handrail

- Pros:
- Cons:

### Option 2:

- Pros:
- Cons:

## Decision

We will ... because ...

## Consequences

- What becomes easier?
- What becomes harder, or what risks are we accepting?
- What will we need to do as a result (follow-up work, exceptions, monitoring)?
- Exit: how would we reverse this if we needed to?