Skip to content
sp

sprint-status

Sprint Status — 95% Confidence Push Auto-regenerated every daemon tick. Open in Obsidian for the live view.

Researched by
K. Pendergrass iD
Last updated: 2026-06-09
Page Snapshot
Reconstructable record

Sprint Status — 95% Confidence Push

Auto-regenerated every daemon tick. Open in Obsidian for the live view.

Headline

1224 / 2570 cells done (47.6%) — 1346 remaining

Velocity: (insufficient history; need 1+ hour of dashboard runs)

Cell state distribution

StateCountCounts as
confidence: high431✅ done
populated n=0 (declared gap)793✅ done
confidence: medium322⏳ needs more sources
confidence: low482⏳ needs more sources
pending / missing523🔴 needs first research
other / unknown19🟡 audit

Pipeline health

ComponentState
Daemon heartbeat⚠️ unknown
auto-fetched/ PDFs in queue935 (fresh work for Codex/daemon ingest)
Audit queue: pending54 ⚠️
Audit queue: pending-audit-spawn-failed119 (async lane)
Wishlist: total downloaded historically72
Wishlist: total ingested historically0
Repo sync⚠️ 1 commit(s) ahead of origin/main
Commits last 1 hour35
Commits last 24 hours682

Most-needy ingredients (top 10 by total source-delta)

SlugSource-delta needed
baby-food100
bee-pollen100
beverages100
black-pepper100
bread100
casein100
cashews100
cereal-bars100
cereal-based-infant-formula100
cereal100

Last commit

9b96798 36 seconds ago — audit: hwang2010-dried-seaweed-korea-metals promoted per autonomous audit

How to read this

The headline number is the only one that matters: cells done / total. Everything else is process metric.

A well-oiled engine looks like:

  • Heartbeat fresh (<35 min old, daemon ticking)
  • auto-fetched/ depth fluctuating (refill then drain then refill — not stuck at zero or piling up indefinitely)
  • Audit queue pending ≤5 (Codex draining it)
  • Commits/hour ≥ 5 during active sprint
  • Velocity positive (cells done going UP between dashboards)
  • Unpushed = 0 (daemon pushes every tick)

When velocity stalls for >2 hours, something upstream broke. Check data/evidence/autonomy/daemon-runs/ for the most recent tick log and look for “FAIL:” lines.