Engineering standards

How work enters a sprint, what done means, how code is reviewed, merged, gated and released. The same rules apply to every module; per-workflow specifics are in quality gates.

Standard	Rule of thumb
Definition of Ready	no story enters a sprint without testable acceptance criteria, an estimate and named dependencies
Definition of Done	merged, deployed, observable, documented, accepted
Branching and git workflow	trunk-based, branches under 2 days, squash merge, feature/ hotfix/ chore/
Code review guidelines	first review in 4 business hours, under 400 lines, comment prefixes
Quality gates	build, lint, tests, coverage floor, scans on every PR in GitHub Actions
Testing strategy	pyramid per module, architecture tests, coverage floors
Release readiness checklist	backward-compatible migrations, rollback verified, production approval
ADO hygiene	work item hierarchy, tags, capacity, say/do ratio

flowchart LR
    R["Refined<br/>(DoR)"] --> B["Branch<br/>feature/…"] --> PR["Pull request<br/>review + CI gates"] --> M["Squash merge<br/>to main"] --> D["Deploy<br/>production approval"] --> V["Verify in production<br/>(DoD)"]