Go-Live Checklist, Personal Training OS v1.0¶
Artifact: Phase 6 (Release) · Owner: Primary User · Gate: exits at G6 (Released & backed up) · Date: 2026-07-05
The go/no-go gate before real use. Everything must be ✅ (or consciously waived) before declaring v1.0 live. Timed to be usable for race week, 25 to 26 Jul 2026.
Pre-go-live (readiness)¶
| # | Item | Status |
|---|---|---|
| 1 | V&V complete, G5 signed, baseline tag vv-accepted |
✅ Done |
| 2 | Release notes / CHANGELOG published (release-notes.md) |
✅ Done |
| 3 | Backup/recovery runbook exists (backup-recovery-runbook.md) |
✅ Done |
| 4 | First real backup taken and logged (runbook §5), proves the procedure end-to-end | ✅ Done, the TC-19 export (Markdown & CSV, subpages) serves as the first backup; logged |
| 5 | Notion plan confirmed, 2 members (Primary User + Secondary User) covered / seats procured | ✅ Done, existing active plan already covers 2 members (predates this project) |
| 6 | Secondary User onboarded (has access to the OS page) | ✅ Household workspace member |
| 7 | Deferred scope communicated (no live sync yet, expectations set) | ✅ (release notes). Accurate at go-live 2026-07-05; live sync subsequently added in Increments 2-3 |
Go-live¶
| # | Item | Status |
|---|---|---|
| 8 | Declare v1.0 live, start logging real sessions (stop using it as a test bed) | ✅ Live 2026-07-05 |
| 9 | Tag the released baseline v1.0 (signed) |
⬜ via signed tag (command below) |
| 10 | Seed the immediate race-week plan (Example 5K 07-25, Example Half Marathon 07-26 already in Races) | ✅ Races seeded |
Post-go-live (hypercare)¶
| # | Item | Status |
|---|---|---|
| 11 | Use daily through race week; capture any friction as issues (not silent workarounds) | ⬜ |
| 12 | After race week: hold Phase 7 retrospective / lessons learned | ✅ Done, retrospective written 2026-07-09 (ahead of race week), with the full Phase 7 closure set (benefits realization + post-implementation review); project closed at G7 |
Open decisions, CLOSED at release (2026-07-05)¶
- A, First backup: ✅ the TC-19 export serves as the first backup (logged in runbook §5).
- B, Notion seats: ✅ existing active plan already covers 2 members, no procurement needed.
- C, Automation revisit: ✅ Garmin integration chosen as the first automation to evaluate, starting immediately after v1.0 lands (feasibility/discovery of the deferred sync work). Outcome (2026-07-05): built and live. Garmin activities and wellness (Increment 2a/2b), Withings weight (2c), and hockey auto-scheduling (Increment 3) all shipped and run on a daily 06:00 sync.
G6 sign-off¶
| Role | Name | Decision | Date |
|---|---|---|---|
| Delivery Manager / PO | Primary User | ✅ APPROVED, Released & backed up | 2026-07-05 |
Signature: authenticated by the SSH-signed release commit that records this and the signed
v1.0tag. Verify withgit tag -v v1.0. Next increment: Garmin integration evaluation.Update (2026-07-05): the Garmin evaluation shipped. Garmin activities and daily wellness (Increment 2a/2b) and Withings body weight (2c) are live, and hockey games auto-schedule into Training Sessions (Increment 3), all live and running on the daily 06:00 scheduled sync since 2026-07-05. These increments carry operational evidence only; the G5 20/20 + 7/7 UAT attestation above covers the v1.0 baseline.