Skip to main content
Reference — generated from the toolkit

Source of truth: toolkit/gates/tech-selection.md. Edit it there; this page is regenerated on build.

Gate: Tech Selection sign-off

Transition: Tech selection → Build Owner: Senior Dev (Lead) Runs: once per product/feature entering Build

Purpose​

Lock the stack and reference architecture — default-first from the radar — so Build starts inside a known scaffold rather than inventing structure. Days, not weeks.

Entry criteria​

  • Design Review passed.
  • The default golden-path stack was considered first; any deviation has a stated reason.

Exit criteria​

  • Stack selected and captured in an ADR (see decision-records standard).
  • The product maps onto one of the reference architectures (multi-tenant SaaS / API service / data pipeline) with UK-insurance non-negotiables addressed (audit trail, PII handling, retention).
  • Radar updated (any new component enters at the correct ring; deprecated components are not selected without a signed risk acceptance).
  • Agent-friendliness and UK+India skills considered and noted.
  • A stack playbook stub exists (to be filled during Build so the next squad inherits it).

Evidence required​

  • Link to the ADR and the radar diff.
  • Reference-architecture mapping.

Automated vs human​

CheckAutomated in CIHuman sign-off
Dependency/licence/CVE intake checks on new components✅—
Architecture fit—Senior Dev + Security

Sign-off & waiver​

  • Signs: Senior Dev (Lead); Security for any component touching auth/PII.
  • May waive: Lead may fast-track an on-radar adopt choice with a lightweight ADR. Selecting a hold-ring component requires a signed risk acceptance, never a waiver.
  • Waiver record: logged in toolkit/registers/ with expiry.