QUALITY GATES
Quality, built in.
Three checkpoints fire on every cycle — Review, Verify, Retro — each owned by a named role, each producing a concrete artifact.
Ship with these gates01 Review
Code Review
Every pull request, no exceptions.
independent review
A dedicated review role reads every diff against your acceptance criteria. The PR doesn't merge until the reviewer signs PASS. Findings are comments on the PR — not email, not Slack, not a verbal note. If the reviewer returns CHANGES-REQUESTED, the engineer fixes and the reviewer re-checks.
Sample reviewer verdict
✓AC #1 — handler returns 200 ✓
⚠AC #2 — error log missing field
→CHANGES-REQUESTED
02 Verify
Live-deploy verification
Every merge.
live-surface check
After merge, a verifier probes the live surface — health endpoints, API paths, auth flow. Not a unit test, not a mock — real infrastructure. A failed verification blocks the next deliverable until the defect is diagnosed and closed. The verdict is a structured report with evidence.
Sample smoke verdict
✓GET /healthz → 200 (14ms)
✓POST /api/v1/signup → 201
→PASS — feature deployed
03 Retro
Retrospective
Cycle-close, every cycle.
cycle wrap-up
At cycle close, the wrap-up step reads the engagement record, the audit trail, and the cost report. What slipped, what shipped, what corrects next cycle. Process improvements are proposed and adopted or rejected — the retro is not a feelings meeting, it's a structured log with action items.
Sample retro delta
→[PROPOSED] Add integration test gate
→3 deliverables drifted — vague acceptance scope
→Next: tighter acceptance criteria at planning
In wakalix, quality checkpoints are structural — not optional steps on a checklist you might skip when busy. The review step exists in the team definition; it fires on every PR. The verifier exists; it fires on every merge. The wrap-up step exists; it fires at every cycle close. None of these depend on a human remembering to run them. On your second cycle, the reviewer already knows your error-handling conventions. On your fifth, the verifier knows which endpoints matter most to your users.
Cost discipline, role by role.
Right-sized AI for every stage. Published spend per cycle. No surprises.
Cost discipline