Build Review Lab

A shared language for “done” across Hyper Sys cohorts. Use these artefacts in stand-ups, mentor sessions, and stakeholder demos — they are living documents, not bureaucracy for its own sake.

Project milestones

Charter lock — Problem, non-goals, and success metrics written and acknowledged by a mentor.
Vertical slice — One user journey works end-to-end in staging with seeded data.
Observability hook — Traces/logs tie customer-visible behaviour to deploy identifiers.
Review rubric pass — Pull requests scored against the rubric below with at least one “needs improvement” note addressed.
Demo rehearsal — Ten-minute narrative with metrics slide and known risks called out.

Code review rubric

Signal	Looks for	Pass hint
Boundary clarity	Modules own their errors; no silent catch-alls.	Typed or documented error paths for external calls.
A11y basics	Keyboard path matches visual order; focus states visible.	Checklist ticked in PR template with exceptions noted.
Test honesty	Assertions match user behaviour, not implementation trivia.	At least one test renamed after review feedback.

Release checklist

Changelog entry with customer-visible bullet
Rollback command or feature flag position documented
Metrics dashboard link attached in deploy thread
Support macro updated if user-facing strings changed

Flow sketch

┌─────────┐    ┌──────────┐    ┌─────────────┐    ┌─────────┐
│ Charter │───▶│ Vertical │───▶│ Observability│───▶│ Demo    │
│  lock   │    │  slice   │    │    hook      │    │ rehearsal│
└─────────┘    └──────────┘    └─────────────┘    └─────────┘
        │                           │
        └─────────── Rubric pass ───┘