Two teams, one week
What replaces the architecture review board
Illustrative scenario, drawn from episode 6.
Team A: a new customer API
They use the standard API pattern, on the AI platform, with approved data services. Their pipeline runs the automated checks on every change, and everything passes. They write a one-page decision record about the one small choice they made, and they ship. No meeting. No queue. Same week.
Team B: AI that recommends credit limits
That is new, and it affects customers directly, so it is tier three. An architect has been working with the team since day one, so there are no surprises. The review happens within two days, with a risk specialist and a data expert in the room. They agree three conditions:
- human approval above a threshold
- a monthly bias check
- a named owner
Team B ships a week later, with conditions everyone understands.
The lesson
Two very different risks. Two proportionate responses. And neither team had any reason to go around the architects.