Proposed Retro Actions — Tracker Foundation
Sprint retrospective proposal for human review (Paul). Deliberated by Claude + Codex; both did independent passes (D25) and converged. Each action is now categorized (type) and given a home (where/when it's tracked).
⚠ AWAITING YOUR APPROVAL — nothing has been applied.
Tracker Foundation gates (A1/A2/A3/A5/A6) all passed. This sprint is done, so its
corrective work needs a home: I propose a small new "Tracker Hardening" sprint
(a Phase A continuation, foundation lane) that runs next — before Platform &
Contracts metrics matter — to hold these as real pointed work items. Tech-debt &
risks are also logged in their panels; deferred work goes to Backlog.
See "Where this work lives" below. Reply proceed to apply, or adjust.
tech debt
risk
tooling
plan hygiene
process
deferred
A · Plan changes scoring & structure
1Fix the story-point double-counttech debt
What WI-026–031 → points:0 (stay as sprint labels); granular slices carry the points.
Why Same work counted twice (WI-027 8pt and WI-032–035 16pt); ~212→~162 pts, honest velocity.
Tracked in Tracker Hardening sprint + logged on the Overview Tech-debt panel (already WI-008). Round 1 Codex #3
2Add granular build slicesplan hygiene
What Split Spine B1–B5 (first), Capture D1–D5, Demand F1–F5, Vision E4–E9 into pointed slices.
Tracked in Tracker Hardening creates the Spine slices now (next sprint); Capture/Demand/Vision slices are created at each sprint's planning entry. Round 1 Codex #3
3Link gates → their requirementstech debt
Why 52/115 requirements aren't referenced by any gate.
Tracked in Tracker Hardening backfills Platform + Spine now; remaining phases at their planning. Gap A Codex #1
4Work item per accepted requirementprocess
What A sprint can't be scored until each accepted requirement maps to ≥1 work item (54/115 lack one).
Tracked in Sprint-planning entry rule (added to the handoff/process), applied per sprint. Gap B Codex #2
5Assign + validate ownersplan hygiene
What Replace 22 TBD owners; ensure labels resolve to the PEOPLE map (validated by #6).
Tracked in Tracker Hardening (initial pass) + each sprint's planning. Gap C Claude C2
B · Tooling & code fixes from the code review
6tracker:check integrity script — firsttooling
What Fail on dup codes, unresolved gate/req refs, bad sprint names, owner/reviewer labels not in PEOPLE, broken paths, overlapping pointed summary/slice rows.
Tracked in Tracker Hardening (pointed work item, owner Claude or Codex). Gap E Codex #8
7Decouple the Supabase reseed from local buildstech debt risk
Why Local docs:tracker writes the prod internal DB; deploy paths don't reseed at all.
Tracked in Tracker Hardening (work item) + Tech-debt panel + a Risk note (accidental prod writes). Claude C1 Codex #1
8One canonical "sprint complete" ruletech debt
What Items-done = complete (retro trigger); gates = separate axis; align static + live.
Tracked in Tracker Hardening (work item). Codex #2
9Stop the SQL seed clobbering live HITL staterisk
Why Re-running the old SQL seed erases live HITL status/notes (data loss).
Tracked in Tracker Hardening (work item) + Risk register (data loss). Codex #4
10Doc / link hygienetech debt
What Fix stale status.json retrospectives/ link; refresh lagging plan docs.
Tracked in link fix → Tracker Hardening; plan-doc refresh → existing items WI-022–025 (Positioning/parallel). Gap D Codex #7
C · Deferred parked, not dropped
11Reviewer authorization (server-side)deferred risk
What Enforce review → done server-side; add reviewer to the live GET.
Why deferred No Auth/permissions layer yet; advisory today (audit records who, doesn't prevent).
Tracked in Backlog as a tagged item (auth/RLS), linked to REQ-SEC-005; pulled into a future Security/Auth slice. Also a standing Risk note until then. Codex #5/#6
D · Where this work lives (answering "which sprint?")
- New "Tracker Hardening" sprint (Phase A continuation, foundation lane) — homes the tooling/code fixes (#6–#9, link fix) + the initial plan-structure pass (#1, #3 backfill, #5) as pointed work items. Runs next, in parallel with build, because the tracker must be trustworthy before sprint metrics matter.
- Per-sprint planning entry — #2 (granular slices for D/E/F), #3 (gate→req for later phases), #4 (req→work-item), #5 (owner assign) are enforced at each upcoming sprint's planning, not all up front.
- Tech-debt panel (Overview) — #1, #7, #8, #10 logged as
techDebt[] on their items so they stay visible until fixed.
- Risk register — #7 (prod writes), #9 (HITL data loss), #11 (review bypass), C2 (silent owner drift) recorded as risks/concerns on the relevant items.
- Backlog — #11 (reviewer auth), parked + tagged, reassigned into a Security/Auth slice at a future retro.
E · Execution order (if approved)
- Create the Tracker Hardening sprint (gates + items).
- #6
tracker:check first — so every later change can't introduce broken refs.
- #1 + #2 point restructure + Spine granular slices.
- #3 + #5 gate→req backfill (Platform/Spine) + owner assignment.
- #7 + #8 + #9 + #10 decouple reseed, canonical completion, seed-clobber fix, link fix.
- #4 added as a planning-entry rule; #11 parked in Backlog (deferred).
- Then close the retro: add
Tracker Foundation to status.retros, move the finalized retro into retrospectives/, rename the deliberation closed-*, regenerate.