Progress
Auto-generated from specs/_status.json on each build. Last status update: 2026-06-10.
Phase: pre-build (specs + contracts; implementation not yet started)
Overview
Section titled “Overview”8 specs entered · 78 requirements tracked.
Delivery ░░░░░░░░░░░░░░░░░░░░ 0% built (passing test)Readiness ██████████████░░░░░░ 72% unblocked & ready to build- Delivery: 0% — 0 of 78 requirements have a passing, ID-tagged test. This is real progress, and it stays at 0% until implementation starts.
- Readiness: 72% — 56 buildable now, 22 (28%) blocked on a clarification. This is how much is teed up, not done.
By spec
Section titled “By spec”| Spec | Area | State | Buildable | Blocked | Done | Key blockers |
|---|---|---|---|---|---|---|
| Identity & Access | Platform | 🟢 ready | 5 | 0 | 0 | auth broker vendor (WorkOS / Keycloak / Auth0) |
| Notifications | Platform | 🟢 ready | 7 | 0 | 0 | confirm Mailgun |
| Org Chart Management | Admin | 🟢 ready | 5 | 0 | 0 | admin-only vs People Team; single vs multiple roots |
| Tenant Settings | Admin | 🟢 ready | 5 | 0 | 0 | — |
| Personal Page | People | 🟢 ready | 14 | 2 | 0 | OQ-03 PDF parse (FR-05); OQ-01 Mojo API (FR-08) |
| MVP Nominations | People | 🔴 blocked | 5 | 5 | 0 | G2 winner-setting; Q6 anonymity; Q1 team deadline; Q4 access role; Q5 directory source |
| Weekly Goals | People | 🔴 blocked | 9 | 8 | 0 | G1 spine relationship; G3 org-chart reads; G4 near-identical; OQ-03 drift threshold |
| Weekly Summary | People | 🔴 blocked | 6 | 7 | 0 | N notifications build; Q3 trend threshold; Q2 response visibility; G1 week definition |
Pre-build readiness. Counts are indicative, authored from each spec’s build-status table. Phase 2: the ‘done’ column is replaced by CI test results (Must-Have FRs with a passing, ID-tagged test).
Once implementation starts, Done is sourced from CI — a Must-Have requirement counts as done only when its ID-tagged test passes (see the operating model). This page then tracks real delivery, not just readiness.