Gate 06 · Key Risks

This is the gate that catches the “we didn’t think about that” problems while they’re still cheap. It produces a risk register: the technical and product risks worth knowing before you build, each paired with a way to handle it.

It reads the brief, your features, the tech stack, and the schema, and looks for where they’ll bite. Bring the concerns you already carry, scale, compliance, a fragile integration, a hard deadline, and the Architect will surface the ones you haven’t named yet.

The difference between a useful register and a useless one is specificity. “Payments are risky” tells no one anything. “A payment webhook can arrive twice, so make the handler idempotent” is a risk with a fix your agent can act on. Push for that.

Risks here feed the build order: high-risk functionalities often want to be sequenced early, so you find the sharp edges before you’ve built a mountain on top of them.

Output: key-risks.md.