← WI-041 Decouple reseed from local builds + seed preserves HITL ★ Live Board · Overview WI-043 Doc/link hygiene + plan-doc refresh hooks →

WI-042 · Tracker Hardening · coverage-backfill

Gate↔requirement + requirement↔work-item backfill (Platform+Spine) + owners

done P1 medium risk   Owner: Codex   Reviewer: Claude   100% · 4/4 tasks complete

Gates: TH4 Requirements: REQ-TRACK-012 Updated: 2026-06-22

At a glance

CodeWI-042
PhaseTracker Hardening
Order77 of 93
Story points5
Primary surfaceroadmap.json + status.json + requirements.json
Retires—
Depends ontracker:check plan-integrity script
Blocks—
Evidence
roadmap.json P1-P8/B1-B5 requirements backfilled; status.json WI-010-WI-017/WI-044-WI-048 requirements + owners; tracker:check 0 errors / 18 warnings

Goals

Backfill Platform & Contracts and Spine coverage so gate requirements, work items, and owners line up before Platform work starts.

Implementation — what to build

Gate↔req

  • Extend each Platform (P1-P8) + Spine (B1-B5) gate's requirements[] to list the decomposed sub-requirements it covers.

Req↔item

  • Ensure every accepted requirement in those phases has a work item (create slices where missing).

Owners

  • Replace TBD owners with an agent/person; tracker:check validates labels.

Acceptance

  • tracker:check reports zero unlinked gate/req and zero TBD in scope.

Checklist

  • ✓ Extend P1-P8 and B1-B5 gate requirements to include decomposed accepted requirements
  • ✓ Map every accepted Platform/Spine requirement to a work item
  • ✓ Assign owners for in-scope TBD Platform/Spine items
  • ✓ Run tracker:check and regenerate tracker pages

Gates & testing

  • ✓ TH4 Gate↔requirement + requirement↔work-item coverage backfilled (Platform + Spine); owners assigned + validated.
    CODE TEST

Requirements

  • REQ-TRACK-012 accepted Every gate must enumerate its requirements and every accepted requirement must map to a work item; owners assigned + validated.
    Done when: Platform + Spine gates list their sub-requirements; accepted reqs in a sprint have a work item; owners are set and resolve to PEOPLE.
    Spec: docs/tracking/decision-log.md#d23 · docs/tracking/retrospectives/proposed-retro-tracker-foundation.html

Verify (done when)

Platform+Spine gates enumerate their sub-requirements; each accepted req maps to a work item; TBD owners resolved + validated.

Cost triggers

No paid API / infra spend triggered by this item.

Status & editing

done   Sprint: Tracker Hardening

Edit status / sprint on the ★ Live Board → — changes are logged live with who / when / why.

Human-in-the-loop

No human tasks linked.

Findings

  • P1-P8 currently cite only one umbrella requirement each despite decomposed accepted requirements in requirements.json.
  • Spine already has granular slices WI-044-WI-048, but B1 still needs REQ-SPINE-007 in the gate coverage.
  • Platform items WI-010-WI-017 are the right work-item homes for accepted Platform requirements; no new Platform slices are needed for this pass.
  • No new Platform slices were needed: WI-010-WI-017 already map one-to-one to P1-P8 and now carry the decomposed requirement IDs.
  • Spine coverage is complete through existing granular slices WI-044-WI-048; B1 now includes REQ-SPINE-007 in both the gate and WI-044.
  • Remaining tracker:check warnings are intentionally outside WI-042 scope: later-sprint/backlog TBD owners plus non-Platform/Spine coverage still to backfill in later planning.

Concerns

None recorded yet.

Risks

None recorded yet.

Tech debt

None recorded yet.

Tools used

  • Shell ? read AGENTS.md, llminterchange.md, session-handoff.md, status.json, decision-log.md, CHANGELOG.md, and verified no open deliberation blocked plan edits
  • Shell ? ran baseline tracker:check (0 errors / 26 warnings) and inspected Platform + Spine requirements/work items
  • Edit ? status.json (marked WI-042 in_progress, added baseline log, then completion log/status/evidence)
  • Edit ? roadmap.json (backfilled P1-P8 and B1-B5 gate requirements[])
  • Edit ? status.json (mapped Platform/Spine accepted requirements to WI-010-WI-017/WI-044-WI-048 and assigned Platform owners)
  • Shell ? ran tracker:check after backfill (0 errors / 18 warnings)
  • Shell ? regenerated tracker pages with tracker-check + build-sprint-tracker + tracker-push (local push skipped Supabase by design)
  • Shell ? ran exact npm run tracker:check under approved escalation (0 errors / 18 warnings)
  • Git ? committed and pushed f07dce2 Complete tracker coverage backfill to origin/main

Files & artifacts

Update log

Update · 2026-06-19 · Started coverage backfill

Started WI-042 with a baseline tracker:check: 0 errors, 26 warnings. The in-scope gaps are Platform & Contracts / Spine gate coverage, Platform work-item coverage, and TBD owners on WI-010-WI-017.

Baseline signalCountScope
Errors0Build gate clean
Warnings26Known coverage + owner warnings
Requirements without gate refs52/120Global WI-042 coverage backlog
Requirements without work items52/120Global WI-042 coverage backlog
TBD owners248 in Platform scope plus later-sprint/backlog items
  • P1-P8 currently cite only one umbrella requirement each despite decomposed accepted requirements in requirements.json.
  • Spine already has granular slices WI-044-WI-048, but B1 still needs REQ-SPINE-007 in the gate coverage.
  • Platform items WI-010-WI-017 are the right work-item homes for accepted Platform requirements; no new Platform slices are needed for this pass.
Update · 2026-06-19 · Backfilled Platform + Spine coverage

Completed the WI-042 backfill. Platform & Contracts gates P1-P8 and Spine gates B1-B5 now enumerate the decomposed accepted/implemented requirements they actually cover, and every accepted Platform/Spine requirement maps to a work item. Platform ownership is assigned across Codex/Claude so the next build sprint has named owners.

ScopeBeforeAfter
Platform/Spine accepted requirements missing gate or item coverage18 in scope0 in scope
Global requirements not referenced by any gate52/12034/120
Global requirements without work item52/12036/120
TBD owners24 total / 8 Platform in scope16 total / 0 Platform in scope
tracker:check0 errors / 26 warnings0 errors / 18 warnings
Work itemOwnerCoverage
WI-010CodexP1 scan I/O contracts, scan types, watchlists, enums, provenance
WI-011ClaudeP2 provider adapter + YAML-to-schema config
WI-012CodexP3 validation pipeline
WI-013ClaudeP4 deterministic ranking
WI-014CodexP5 ingestion/promotion + credential/key boundaries
WI-015ClaudeP6 data-model layers, public safety, RLS path
WI-016ClaudeP7 MCP safe/candidate/approval tool tiers
WI-017CodexP8 observability, cost, scoped image access
  • No new Platform slices were needed: WI-010-WI-017 already map one-to-one to P1-P8 and now carry the decomposed requirement IDs.
  • Spine coverage is complete through existing granular slices WI-044-WI-048; B1 now includes REQ-SPINE-007 in both the gate and WI-044.
  • Remaining tracker:check warnings are intentionally outside WI-042 scope: later-sprint/backlog TBD owners plus non-Platform/Spine coverage still to backfill in later planning.