Sprint Status Brief
Time until Sprint Planning
90 min
Planning starts 8:30 AM ET
Brief generated 2026-06-29 7:00 AM ET
New sprint: Sprint 2 · 2026-06-29 → 2026-07-03 ET
8 / 0✓
Sprint 1 committed → slipped
6
Sprint 2 planned (unfiled)
1Previous sprint review Sprint 1 · completed Mon–Fri 6/22–6/26 ET · 7 tickets
None of these were Sprint 1’s committed work. Sprint 1 committed 8 tickets (Foundation + AMS + Acct-v2) and shipped 0 of 8. The 7 closures below were all unplanned SIP / indicator / tooling work that jumped the queue. See §2 for the slipped commitments.
sip3 shipped
- ✓P1LYNCH Continuation Breakout module built + test harness2026-06-22 · claude
- ✓P1SIP next-day preview builder (v1 + v2) -> _sip_preview_2026-06-232026-06-22 · claude
- ✓P2SIP/MGP explainer page published2026-06-23 · claude
atlas1 shipped
- ✓P2EOD brief generator + catch-up automation2026-06-22 · claude
foundation1 shipped
- ✓P2econ_calendar.py — add ISM Manuf/Services + BEA GDP/PCE + Conference Board + UMich Sentiment + Fed-speak (compute-by-cadence pattern)2026-06-25 · claude
pinepb1 shipped
- ✓P1J3P v2.2 — webhook ENTRY/EXIT emission into alerts_tradingview.indicator_alerts2026-06-26 · claude
exec1 shipped
- ✓P1PLAN published: SIP->Indicators->g8trade roadmap2026-06-26 · claude
2Previous sprint slippage Sprint 1 scope · still pending · created before last Monday
All 8 of Sprint 1’s committed tickets carried over — 0% completion. Three of them predate the sprint by months; five are the AMS/Backup batch filed 6/20:
- ○atlasP01/6 Data-freshness dashboard: /system/freshness.json + banner on hubowner claude · 73d old · created 2026-04-17
- ○acct-v2P0BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)owner jimbo · 53d old · created 2026-05-07
- ○acct-v2P0BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)owner jimbo · 47d old · created 2026-05-13
- ○amsP0AMS: seed main.users with trader rows so identity_fn returns non-zeroowner user · 9d old · created 2026-06-20
- ○amsP0AMS: create main.remembered_devices table (migration 002) — Phase 1 hard dependencyowner claude · 9d old · created 2026-06-20
- ○amsP0AMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop)owner user · 9d old · created 2026-06-20
- ○amsP1AMS: write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md (Phase 3a baseline shipped, what's left)owner claude · 9d old · created 2026-06-20
- ○backupP1Backup: mirror scheduled-task SKILL files from domino-1 to jimdo via scpowner claude · 9d old · created 2026-06-20
Wider backlog context: 151 pending tickets were created before last Monday and remain open — 33 P0, 59 P1, 23 P2 (+36 untriaged). This is the aged debt the sprint cadence exists to drain.
3This sprint’s goal Sprint 2 · 2026-06-29 → 2026-07-03 ET
Classifier production + AMS Phase 1 sign-off
Get the classifier refreshing live (unblocks Exec). Close AMS Phase 1.
⚠ Note: Sprint registry still shows active_sprint_id = 1 — Sprint 1’s window closed Friday 6/26. Advancing the pointer to Sprint 2 and rolling the 8 carryover tickets forward is the first planning action.
4This sprint’s backlog 6 planned (from sprint-plan.html) · not yet filed as tickets
| St | Project | Ticket | Owner | Est | Pri |
|---|
| ○ | classifier | Ship roberto-classifier-refresh-cron — every-1-min refresh of classify/<SYMBOL>.json during RTH | roberto | 0.5d | P0 |
| ○ | classifier | Persist manual overrides to DB (currently flat JSON) | roberto | 2d | P1 |
| ○ | ams | Apply migrations 021 (trade_action_requests) + 022 (hud_usage_events) to dev DB | claude | 0.5d | P1 |
| ○ | ams | AMS Phase 1 sign-off — Auth boundary green-lit per integration plan | user | 1d | P0 |
| ○ | backup | JIMDO Step 0: delay+skip if primary already wrote today's output | claude | 1d | P1 |
| ○ | atlas | Cross-link AMS todos with main todos (single source for tasks) | claude | 0.5d | P2 |
None of these 6 exist in todos.json yet — they live only in the sprint plan. File them during planning. Plus the 8 carryover tickets from §2 that must roll into Sprint 2 — realistic committed load is ~14 items, which exceeds last sprint’s delivered 7.
5Dependencies no depends_on field in todos.json — inferred from notes + critical path
| Ticket | State | What blocks / readies it |
|---|
| classifierShip roberto-classifier-refresh-cron | BLOCKED | Owner Roberto. Needs Roberto’s availability + a cron host. Gates the entire Exec Trigger Engine (Sprint 3) — classify/*.json must update every minute during RTH. |
| classifierPersist manual overrides to DB | READY | Roberto-actionable once refresh-cron lands; can ship independently to dev. No hard external blocker. |
| amsApply migrations 021 + 022 to dev DB | BLOCKED | Logically gated by D3 (DB-strategy decision, owner=user, §2). Idempotent once decision is made; ~30 min. |
| amsAMS Phase 1 sign-off | BLOCKED | Owner you. Depends on seed-main.users + D1–D7 resolution (both carryover P0s). Cannot sign off until identity_fn returns non-zero. |
| backupJIMDO Step 0: delay+skip | READY | ssh jimdo / scp verified. claude-actionable now; depends only on the SKILL-mirror carryover ticket. |
| atlasCross-link AMS todos with main todos | READY | Pure tooling. claude-actionable now, no blocker. |
6Critical-path stack top 7 from sprint-plan.html, sorted by readiness
1 | You run scientific_layer migrations 001–009 via psql tunnel Critical-path step 1 — open 68d. Retires 4 user P0s; unblocks daily-summary view, rule-based classifier, identity_fn DB writes. | BLOCKED user · 15 min |
2 | You seed main.users + resolve D1–D7 (AMS) Two carryover P0s that gate the entire AMS Phase-1 sign-off chain. Pure decisions + one seed script. | BLOCKED user · ~45 min |
3 | Jim ships the 2 Acct-v2 date-range bugs Open 47–53d. Without these, no metric on a multi-day view can be trusted — blocks any team rollout. | BLOCKED jimbo · 2 P0s |
4 | Atlas ships p0-freshness-dashboard MVP (property side) Completes Phase-0 freeze. DB-source half follows once migrations land. claude-actionable now. | READY claude · 2h |
5 | Classifier refresh cron ships (Roberto) classify/*.json must update every minute during RTH for the Trigger Engine to fire. Sprint 2 headline item. | BLOCKED roberto · 4h |
6 | Backup warm-runner online (heartbeat + delay/skip + liveness) Critical BEFORE Exec goes live. If domino-1 dies, jimdo keeps alerts firing. Carryover SKILL-mirror is step 1. | READY claude · 3 days |
7 | Exec Trigger Engine + Alert Channels in DEV First half of the execution arm (Sprint 3). Alerts to humans only at this stage. Downstream of step 5. | DOWNSTREAM claude · 1 wk |
7Velocity trend tickets completed per week (Mon–Fri), last 4 weeks
Trend: -20 WoW (27→7). Velocity collapsed after three weeks of acceleration — and the 7 that did close were all off-plan work. The committed Sprint 1 backlog moved 0. See Q2.
8Stale alarms human-owned P0 >14d · properties RED >48h
8 human-owned P0s aged >14 days (3 owner=user, 2 owner=jimbo, 3 owner=james)
- ○atlasP06/6 indicator_alerts DDL audit: dump schema, commit as ground truthowner user · 73d
- ○multi-traderP0USER: 3 steps to finish journal persistenceowner user · 72d
- ○multi-traderP0USER: run scientific_layer migrations 001–009 via psql tunnelowner user · 68d
- ○acct-v2P0BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)owner jimbo · 53d
- ○atlasP0Compliance follow-up: delete (or hide) historical MGP pages 4/17 through 5/12 — they still contain Vital Knowledge textowner james · 47d
- ○acct-v2P0BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)owner jimbo · 47d
- ○atlasP0BUG: MGP auto-fire skipped 5/14 mid-day + recap; 5/15 morning ran ~2h45m lateowner James · 45d
- ○atlasP0Nightly PM daemon went dark 5/20-5/22 (3 consecutive missed fires) — fix wake/launchowner james · 37d
2 properties RED, stale >48h (per app-status.json, probed 2026-06-29 07:01 ET · overall RED · host DESKTOP-AKU8I62)
- ○Playbooks 182h stale (threshold 30h) · 182.4h stale (threshold 30.0h, EOD trading-day regen)
- ○Param Surface (DB) 120h stale (threshold 30h) · 119.7h stale (threshold 30.0h, EOD trading-day regen)
Not alarms: VWAP-bands Strategy Bar (304h), VWAP-bands Strategy Registry (304h), Strategy Library (276h) are stale >48h but GREEN — static informational pages with no scheduled refresh.
9Pre-meeting questions answer these in planning
Q1.The sprint pointer still reads active_sprint_id = 1, but Sprint 1’s window closed Friday and Sprint 2 starts today. Do we advance it to 2 and roll the 8 unfinished tickets forward — or formally extend Sprint 1?
Q2.Sprint 1 shipped 0 of its 8 committed tickets while 7 unplanned SIP/indicator tickets jumped the queue. Are we committing to a plan, or working reactively? What changes this week so the committed backlog actually moves?
Q3.Sprint 2’s 6 planned items are not filed in todos.json — they exist only in the sprint plan. Do we file them now, and is Roberto available this sprint for classifier-refresh-cron (the Sprint 2 headline + Sprint 3 gate)?
Q4.The scientific_layer migrations (P0, owner=user, 68 days stale) are critical-path step 1 and unblock 4 downstream P0s + the rule-based classifier. Still not scheduled — can you commit the 15 minutes this sprint?
Q5.Velocity dropped 27→7 and every human-owned P0 is stalling (8 of them, up to 73d). What is the single task each human owner — you, Jim, James — commits to closing this week?