Sprint Status — pre-planning brief

Generated Friday 2026-07-10, 4:38 AM ET by Atlas · sources: /todos/todos.json (live) + /system/sprint-plan.html (frozen 2026-06-20 ET). All times ET.
Time until Sprint Planning
3d 3h 52m
Next planning: Mon 2026-07-13, 8:30 AM ET
Sprint 3 closes today (Fri 7/10)
Sprint 4 opens Mon 7/13
⚠ This brief did not run on its scheduled trigger, and two inputs disagree.

1Previous sprint reviewSprint 3 · 7/06 → 7/10 ET · closes today

Four tickets closed inside Sprint 3’s window — all four are James’s nightly roll-up entries, each covering a day of J3P/SIP work. Zero of Sprint 3’s five filed tickets closed.
CompletedProjectOwnerTicket
2026-07-06—JamesSIP Today + Nuance tracking + Exit study + Trades-by-day + Replay tool
2026-07-07—JamesJ3P visual stack: cheat cards, swing DMA, trend playbook, analog target, trust report
2026-07-08—JamesJ3P watcher page + alerts cheat card
2026-07-09—JamesJ3P live setups + churn-today meter + command surface + multi-tf-stack
For reference, the sprint before it — Sprint 2 (6/29 → 7/03) — closed 3, none of them from its planned backlog:
CompletedProjectOwnerTicket
2026-06-29ExecclaudeJ3P v2.4 regime-filter matrix run end-to-end (shorts + Dale-trend + CBO + 6 filters)
2026-07-01—JamesJ3P 2-min parity build + TOD matrix page
2026-07-02—JamesJ3P exit surface + ladder OOS + Data Trust Spec refresh

2Previous sprint slippagecreated before last Monday · still pending

Sprint 1 committed 8 tickets. Three sprints later all 8 are still pending — 0/8. They have now been carried through Sprint 2 and Sprint 3 untouched. This is the single most important number in the brief.
PriOwnerProjectAgeTicket
P0claudeAtlas84dData-freshness dashboard: /system/freshness.json + banner on hub
created 2026-04-17
P0jimboAcct-v264dBUG: Risk Bump Progress bar ignores selected date range
created 2026-05-07
P0jimboAcct-v258dBUG: Ticket Meter denominator does not scale with date range
created 2026-05-13
P0userAMS20dSeed main.users with trader rows so identity_fn returns non-zero
created 2026-06-20
P0claudeAMS20dCreate main.remembered_devices (migration 002) — Phase 1 hard dependency
created 2026-06-20
P0userAMS20dResolve 7 open decisions D1–D7 (domain · auth stack · DB strategy)
created 2026-06-20
P1claudeAMS20dWrite PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md
created 2026-06-20
P1claudeBackup20dMirror scheduled-task SKILL files from domino-1 to jimdo via scp
created 2026-06-20
Sprint 3 adds 5 more pending tickets to the carry pile. None were started:
OwnerProjectTicket
claudePinePBJ3P — live smoke test: TV alert → webhook → indicator_alerts row (1 SIP name)
claudePinePBJ3P — FashLate-style label/alert polish (compact toggle + per-play templates)
claudePinePBJ3P v2.3 — rebuild Trend play as Dale VWAP 1st-deviation pullback
claudeSIPDeploy J3P across SIP master_watchlist (TV layout + webhook alert per symbol)
claudeSIPAuto-sync /sip/watchlist.json → TradingView symbol list
The divergence. Sprint 3’s planned scope in sprint-plan.html was Exec Trigger Engine, Alert Channels, Risk Gate, MultiTrader parameterizer, Backup heartbeat. The tickets actually filed against Sprint 3 in todos.json are J3P webhook, label polish, Trend-play rebuild, SIP watchlist deploy and autosync. The two lists share nothing. Real effort went to J3P and SIP; the Exec arm never started.

3This sprint’s goalSprint 4 · opens Mon 7/13

Sprint 4 · Exec Gr8Trade adapter + forward-test
7/13 → 7/24 ET (2 weeks)
Theme: First broker adapter, forward-test only. No real orders yet — wire the chain end-to-end.
Dates per todos.json. sprint-plan.html says 7/12 → 7/25 for the same sprint; titles and goals match, boundaries do not.

4This sprint’s backlog5 planned (unfiled) + 2 filed tickets

The five planned items exist only as rows in sprint-plan.html — none has been filed as a ticket, so none carries a real owner, status, or estimate. Estimate cells are left blank where the plan gives no figure; the only available number is the critical-path estimate (*). Nothing here is invented.
ProjectItemStatusOwnerEstReadiness
ExecGr8Trade adapter via Kore tick bridge — gr8.send_order() signatures + adapter wrapperunfiled—~2 wks*BLOCKED
exec-kore-live-j3p awaits firm-confirm of Gr8Script/Kore call signatures
ExecFull forward-test in DEV: real signals → real alerts → simulated orders (caps 1 share, 1 order/day)unfiled——BLOCKED
Needs the adapter above, plus the classifier refresh cron (Sprint 2, never shipped)
StratLibAlex onboarding: codify Range Break rules into catalog JSONunfiledalex—READY
No upstream dependency
AMSPhase 4 surface wiring starts: copy → auth-wrap inside ams/ → green-lightunfiledclaude—BLOCKED
AMS Phase 1 sign-off never happened (Sprint 2 carryover); needs migration 002 + D1–D7
MultiTraderTrader selector dropdown on /scorecards/ indexunfiledclaude—PARTIAL
Depends on /scorecards/?user=; resolve_user() known broken, static map in place
ExecBacktest J3P plays (Focus-3/KITE) on SIP names — edge by playbook × grade × tierin_progressclaude—READY
Active now
ExecWire setups.today.json → hotkey-engine for J3P-graded entries (SIM → forward-test)pendingclaude—READY
V1 SIM already shipped
* sprint-plan.html’s critical path estimates the Gr8Trade adapter at 2 weeks, claude+jim. Of the seven rows above, only three are unblocked today.

5Dependenciesinferred from notes — no depends_on field exists

TicketBlocked byEvidence
exec-kore-live-j3p (blocked)Firm confirmation of Gr8Script/Kore call signaturesTicket note: “Blocked: firm-confirm Gr8Script/Kore call signatures to un-inert kore_backend.py.”
Sprint 4 — Gr8Trade adapterexec-kore-live-j3pThe same call signatures are the adapter’s interface. You cannot wrap what is not confirmed.
Sprint 4 — forward-test in DEVClassifier refresh cron (Sprint 2, never shipped)Plan: “classify/*.json must update every minute during RTH for Trigger Engine to fire on live signals.”
Classifier parity testliberator-datasource-blocker (blocked 33 d)Note: kti liberator query --dataset minute_bars times out on every pair; account entitlements dropped.
Sprint 4 — AMS Phase 4 wiringAMS Phase 1 sign-off; migration 002; decisions D1–D7All three are Sprint 1 carryover, still pending. Migration 002 note: “Phase 1 hard dependency.”
p0-daily-summary-view, auto-classifier, identity_fn writesrun-scientific-layer-migrations (user, 79 d)Plan critical path #1: “Retires 4 user P0s, unblocks p0-daily-summary-view, auto-classifier rule-based path, identity_fn DB writes.”
Any multi-day team rolloutThe 2 Acct-v2 date-range bugs (jimbo)Plan: “Without these, no metric on a multi-day view can be trusted.”
MultiTrader per-trader monthly view/scorecards/?user= shippedPlan states the dependency explicitly; resolve_user() is currently a static map.

6Critical path stacktop 7 from sprint-plan.html · sorted by readiness

Plan #StepOwnerEstReadiness
1You run scientific-layer migrations 001–009 via psql tunnel
Idle 79 days. Retires 4 user P0s; unblocks p0-daily-summary-view, the auto-classifier rule-based path, and identity_fn DB writes.
user15 minREADY
2Jim ships the 2 Acct-v2 date-range bugs
Open 64d / 58d. Until these land, no metric on a multi-day view can be trusted — blocks any team rollout.
jimbo2 P0sREADY
3Atlas ships p0-freshness-dashboard MVP (property side)
Now self-evidently urgent: the existing watchdog has been dark 40.5 h and nothing flagged it.
claude2 hREADY
6Backup warm-runner online (heartbeat + delay+skip + liveness)
Must land BEFORE Exec goes live. If domino-1 dies, jimdo must keep alerts firing.
claude3 daysREADY
4Classifier refresh cron ships (Roberto)
The rule-based path is buildable now. The 20-pair Liberator parity test stays blocked — account entitlements dropped 33 days ago.
roberto4 hPARTIAL
5Exec Trigger Engine + Alert Channels in DEV
Blocked by #4. This was Sprint 3's headline scope — it never started.
claude1 wkBLOCKED
7Exec Gr8Trade adapter enabled in prod with caps
Blocked by #5, and by firm-confirm of Gr8Script/Kore call signatures.
claude+jim2 wksBLOCKED
Four of the seven are ready right now, and have been ready for weeks. The two blocked steps are blocked by the ready ones. Nothing on this path is waiting on an external party.

7Velocity trendcompleted_at within Mon–Fri, last 4 weeks

6/15–6/1927
6/22–6/267
6/29–7/033
7/06–7/104
27 → 7 → 3 → 4. Recorded throughput fell sharply the week Sprint 1 opened and has not recovered.
Read this number carefully — the drop is not all real. Two effects are mixed together. Through mid-June, tickets were filed individually. From 2026-06-29 onward, nearly every completion is a single nightly roll-up entry by James covering a whole day of work (one ticket reads “cheat cards, swing DMA, trend playbook, analog target, trust report”). So the June bars count tickets and the July bars count days — they are not comparable. The 7/06–7/10 bar is also incomplete: it was measured Friday at 4:38 AM ET, before Friday’s work. What this chart does not prove is that less work happened. What is independently true, straight from ticket status: 0 of 8 Sprint 1 commitments closed across three sprints.

8Stale alarmsP0 owner=user > 14 d · freshness > 48 h

⚠ The freshness monitor itself is dark. app-status.json reports generated_at 2026-07-08T12:01:08 ET and overall_status: RED. That is 40.5 hours ago, against a 30-minute probe cadence. Every age below is frozen as of that last successful probe — current staleness is unknown, and can only be worse. Nothing escalated this. The watchdog needs a watchdog.
PropertyStatusAge at last probeThresholdNote
param_surface_dbRED340.7 h ≈ 14.2 d30 hRoughly 16 days stale if the clock kept running. EOD trading-day regen.
playbooksRED38.7 h30 hAlready over threshold at the last probe. Current value unmeasured.
app-status.json (the probe itself)RED40.5 h0.5 hHost DESKTOP-AKU8I62. 10 of 12 sources last read GREEN — but that reading is 40 h old.
P0 tickets owned by the user, open more than 14 days — 10 of them. Four are over 78 days old.
AgeOwnerTicket
84duserp0-indicator-alerts-ddl
83duserjournal-user-steps
79duserrun-scientific-layer-migrations
58djamesmgp-historical-pages-cleanup
56dJamesmgp-cron-skipped-5-14
48djamesnightly-pm-silent-gap-2026-05-20-to-22
20duserams-seed-users-from-main
20duserams-decisions-d1-through-d7
19duserpinepb-tradingview-setup-guide
19duserpinepb-deploy-to-james-tradingview
Plus 2 P0s owned by jimbo (the Acct-v2 date-range bugs, 64 d and 58 d) and 1 blocked classifier ticket (Liberator entitlements, 33 d). Backlog totals: 162 pending, 7 in progress, 2 blocked, 248 completed, 3 cancelled.

9Pre-meeting questionsanswer these before committing Sprint 4

Sprint pointer and carryover
active_sprint_id has read 1 since 2026-06-26 ET, and Sprint 1 stands at 0/8 after three full cycles. Do we re-commit those eight tickets, or formally cancel the ones that stopped mattering? Who advances the pointer — and is that a manual step, or should Nightly PM own it?
Which document is authoritative?
Sprint-plan's Sprint 3 (Trigger Engine, Alert Channels, Risk Gate) shipped none of its scope; the week's actual output was J3P and SIP work. Is the Exec arm genuinely deferred, or is sprint-plan.html simply not tracking decisions we already made? On Monday, which artifact do we plan against?
Is Jim available this sprint?
Acct-v2 carries two P0s (64 days and 58 days), both owned by Jimbo, and together they gate any team rollout. Is Jim available this sprint — or do we reassign them, defer them, and stop calling them P0?
A 15-minute task, idle 79 days
run-scientific-layer-migrations is estimated at 15 minutes, sits at #1 on the critical path, and retires four user P0s. What is the real obstacle — access, risk, or that nobody has been asked in the room? Can we simply run it live during planning?
What is the smallest unblocked Sprint 4?
Sprint 4 commits to the Gr8Trade adapter, but exec-kore-live-j3p is blocked pending firm confirmation of Gr8Script/Kore call signatures, and the forward-test depends on a classifier cron that never shipped. Of the five planned items, only Alex's Range Break is cleanly unblocked. What do we actually commit to?