/todos/todos.json (live) + /system/sprint-plan.html (frozen 2026-06-20 ET). All times ET.todos.json still reports active_sprint_id: 1. Sprint 1’s window closed 2026-06-26. The pointer has not advanced through two complete sprints, so every downstream “active sprint” readout is wrong.sprint-plan.html was last written 2026-06-20 19:48 ET (20 days ago). Its sprint boundaries disagree with todos.json (plan: S3 = 7/05→7/11; todos: S3 = 7/06→7/10), and its contents disagree entirely — see §2.depends_on field. Every dependency in §5 is inferred from ticket notes, not read from structured data.| Completed | Project | Owner | Ticket |
|---|---|---|---|
| 2026-07-06 | — | James | SIP Today + Nuance tracking + Exit study + Trades-by-day + Replay tool |
| 2026-07-07 | — | James | J3P visual stack: cheat cards, swing DMA, trend playbook, analog target, trust report |
| 2026-07-08 | — | James | J3P watcher page + alerts cheat card |
| 2026-07-09 | — | James | J3P live setups + churn-today meter + command surface + multi-tf-stack |
| Completed | Project | Owner | Ticket |
|---|---|---|---|
| 2026-06-29 | Exec | claude | J3P v2.4 regime-filter matrix run end-to-end (shorts + Dale-trend + CBO + 6 filters) |
| 2026-07-01 | — | James | J3P 2-min parity build + TOD matrix page |
| 2026-07-02 | — | James | J3P exit surface + ladder OOS + Data Trust Spec refresh |
| Pri | Owner | Project | Age | Ticket |
|---|---|---|---|---|
| P0 | claude | Atlas | 84d | Data-freshness dashboard: /system/freshness.json + banner on hub created 2026-04-17 |
| P0 | jimbo | Acct-v2 | 64d | BUG: Risk Bump Progress bar ignores selected date range created 2026-05-07 |
| P0 | jimbo | Acct-v2 | 58d | BUG: Ticket Meter denominator does not scale with date range created 2026-05-13 |
| P0 | user | AMS | 20d | Seed main.users with trader rows so identity_fn returns non-zero created 2026-06-20 |
| P0 | claude | AMS | 20d | Create main.remembered_devices (migration 002) — Phase 1 hard dependency created 2026-06-20 |
| P0 | user | AMS | 20d | Resolve 7 open decisions D1–D7 (domain · auth stack · DB strategy) created 2026-06-20 |
| P1 | claude | AMS | 20d | Write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md created 2026-06-20 |
| P1 | claude | Backup | 20d | Mirror scheduled-task SKILL files from domino-1 to jimdo via scp created 2026-06-20 |
| Owner | Project | Ticket |
|---|---|---|
| claude | PinePB | J3P — live smoke test: TV alert → webhook → indicator_alerts row (1 SIP name) |
| claude | PinePB | J3P — FashLate-style label/alert polish (compact toggle + per-play templates) |
| claude | PinePB | J3P v2.3 — rebuild Trend play as Dale VWAP 1st-deviation pullback |
| claude | SIP | Deploy J3P across SIP master_watchlist (TV layout + webhook alert per symbol) |
| claude | SIP | Auto-sync /sip/watchlist.json → TradingView symbol list |
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.todos.json. sprint-plan.html says 7/12 → 7/25 for the same sprint; titles and goals match, boundaries do not.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.| Project | Item | Status | Owner | Est | Readiness |
|---|---|---|---|---|---|
| Exec | Gr8Trade adapter via Kore tick bridge — gr8.send_order() signatures + adapter wrapper | unfiled | — | ~2 wks* | BLOCKED exec-kore-live-j3p awaits firm-confirm of Gr8Script/Kore call signatures |
| Exec | Full 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) |
| StratLib | Alex onboarding: codify Range Break rules into catalog JSON | unfiled | alex | — | READY No upstream dependency |
| AMS | Phase 4 surface wiring starts: copy → auth-wrap inside ams/ → green-light | unfiled | claude | — | BLOCKED AMS Phase 1 sign-off never happened (Sprint 2 carryover); needs migration 002 + D1–D7 |
| MultiTrader | Trader selector dropdown on /scorecards/ index | unfiled | claude | — | PARTIAL Depends on /scorecards/?user=; resolve_user() known broken, static map in place |
| Exec | Backtest J3P plays (Focus-3/KITE) on SIP names — edge by playbook × grade × tier | in_progress | claude | — | READY Active now |
| Exec | Wire setups.today.json → hotkey-engine for J3P-graded entries (SIM → forward-test) | pending | claude | — | 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.| Ticket | Blocked by | Evidence |
|---|---|---|
exec-kore-live-j3p (blocked) | Firm confirmation of Gr8Script/Kore call signatures | Ticket note: “Blocked: firm-confirm Gr8Script/Kore call signatures to un-inert kore_backend.py.” |
| Sprint 4 — Gr8Trade adapter | exec-kore-live-j3p | The same call signatures are the adapter’s interface. You cannot wrap what is not confirmed. |
| Sprint 4 — forward-test in DEV | Classifier 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 test | liberator-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 wiring | AMS Phase 1 sign-off; migration 002; decisions D1–D7 | All three are Sprint 1 carryover, still pending. Migration 002 note: “Phase 1 hard dependency.” |
p0-daily-summary-view, auto-classifier, identity_fn writes | run-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 rollout | The 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= shipped | Plan states the dependency explicitly; resolve_user() is currently a static map. |
| Plan # | Step | Owner | Est | Readiness |
|---|---|---|---|---|
| 1 | You 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. | user | 15 min | READY |
| 2 | Jim 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. | jimbo | 2 P0s | READY |
| 3 | Atlas ships p0-freshness-dashboard MVP (property side) Now self-evidently urgent: the existing watchdog has been dark 40.5 h and nothing flagged it. | claude | 2 h | READY |
| 6 | Backup warm-runner online (heartbeat + delay+skip + liveness) Must land BEFORE Exec goes live. If domino-1 dies, jimdo must keep alerts firing. | claude | 3 days | READY |
| 4 | Classifier 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. | roberto | 4 h | PARTIAL |
| 5 | Exec Trigger Engine + Alert Channels in DEV Blocked by #4. This was Sprint 3's headline scope — it never started. | claude | 1 wk | BLOCKED |
| 7 | Exec Gr8Trade adapter enabled in prod with caps Blocked by #5, and by firm-confirm of Gr8Script/Kore call signatures. | claude+jim | 2 wks | BLOCKED |
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.| Property | Status | Age at last probe | Threshold | Note |
|---|---|---|---|---|
| param_surface_db | RED | 340.7 h ≈ 14.2 d | 30 h | Roughly 16 days stale if the clock kept running. EOD trading-day regen. |
| playbooks | RED | 38.7 h | 30 h | Already over threshold at the last probe. Current value unmeasured. |
| app-status.json (the probe itself) | RED | 40.5 h | 0.5 h | Host DESKTOP-AKU8I62. 10 of 12 sources last read GREEN — but that reading is 40 h old. |
| Age | Owner | Ticket |
|---|---|---|
| 84d | user | p0-indicator-alerts-ddl |
| 83d | user | journal-user-steps |
| 79d | user | run-scientific-layer-migrations |
| 58d | james | mgp-historical-pages-cleanup |
| 56d | James | mgp-cron-skipped-5-14 |
| 48d | james | nightly-pm-silent-gap-2026-05-20-to-22 |
| 20d | user | ams-seed-users-from-main |
| 20d | user | ams-decisions-d1-through-d7 |
| 19d | user | pinepb-tradingview-setup-guide |
| 19d | user | pinepb-deploy-to-james-tradingview |
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?sprint-plan.html simply not tracking decisions we already made? On Monday, which artifact do we plan against?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?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?