/todos/todos.json (live, last nightly 2026-07-19 11:10 PM ET) + /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 — 26 days ago. The pointer has not advanced through three complete sprints, so every downstream “active sprint” readout is wrong. This has been flagged in every EOD brief since 7/13 and is still unfixed.sprint-plan.html was last written 2026-06-20 19:48 ET (32 days ago). Its sprint boundaries disagree with todos.json (plan: S4 = 7/12→7/25; todos: S4 = 7/13→7/24), and its contents disagree entirely with the filed tickets — see §4.depends_on field. Every dependency in §5 is inferred from ticket notes, not read from structured data.atlas-flow-status (stood up 7/13) is live and GREEN, last probe 7/21 7:00 PM ET. The two legacy monitors are still dark (see §8) but the signal is no longer entirely blind.| Completed | Project | Owner | Ticket |
|---|---|---|---|
| 2026-07-13 | Foundation | claude | Atlas flow-status monitor live and fresh (replacement for dead app-status) |
| 2026-07-13 | Foundation | claude | J3P Monday live-test surfaces regenerated (LIVE, WATCHER, ROBOT_REPORT, churn) |
| 2026-07-13 | Foundation | claude | LYNCH earnings + PIT live surface (TRUERULES) built on Sunday’s combinatorics |
| 2026-07-13 | Foundation | claude | setup_chart.js: entry/exit price markers on annotated charts |
| 2026-07-13 | Foundation | claude | market_sentiment.py alignment + visual rework |
| 2026-07-14 | Foundation | claude | Earnings-trade pattern analysis — reverse-engineer the backtest filters |
| 2026-07-14 | Foundation | claude | J3P Tuesday live-test surface set regenerated (2nd live session) |
| 2026-07-15 | Foundation | claude | J3P Wednesday live-test surface set regenerated (3rd live session) + LYNCH |
| 2026-07-16 | Atlas | claude | SIP page generator (build_sip_page.py) updated |
| 2026-07-16 | Acct-v2 | James | Prod HUD api/trader.php edited (backup tar taken) |
| 2026-07-17 | StratLib | James | VWAP research page (db_reports/vwap-research) updated |
| Pri | Owner | Project | Age | Ticket |
|---|---|---|---|---|
| P0 | claude | Atlas | 96d | Data-freshness dashboard: /system/freshness.json + banner on hubcreated 2026-04-17 · partially superseded by atlas-flow-status (7/13) |
| P0 | jimbo | Acct-v2 | 76d | BUG: Risk Bump Progress bar ignores selected date range created 2026-05-07 |
| P0 | jimbo | Acct-v2 | 70d | BUG: Ticket Meter denominator does not scale with date range created 2026-05-13 |
| P0 | user | AMS | 32d | Seed main.users with trader rows so identity_fn returns non-zerocreated 2026-06-20 |
| P0 | claude | AMS | 32d | Create main.remembered_devices (migration 002) — Phase 1 hard dependencycreated 2026-06-20 |
| P0 | user | AMS | 32d | Resolve 7 open decisions D1–D7 (domain · auth stack · DB strategy) created 2026-06-20 |
| P1 | claude | AMS | 32d | Write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md created 2026-06-20 |
| P1 | claude | Backup | 32d | 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. Not one of those shipped. The j3p-webhook-smoke-test is the closest live blocker — it needs James to attach one TradingView alert to fire the chain end-to-end. It has sat one manual step away from done for 26 days.sprint-plan.html and todos.json (both agree on title + theme). Dates per todos.json; the plan says 7/12 → 7/25 for the same sprint. With two days left, none of the theme’s headline work (adapter, forward-test) has started — see §4.sprint-plan.html — none is filed, so none carries a real owner, status, or estimate. The filed five are sprint=4 tickets in todos.json — all J3P backtest work, three already completed (though back in late June, before the sprint window opened). The two lists barely overlap. Estimates blank where the plan gives none; the only figure is the critical-path estimate (*).| Project | Item | Status | Owner | Est | Readiness |
|---|---|---|---|---|---|
| Exec | Gr8Trade adapter via Kore tick bridge — gr8.send_order() signatures + adapter wrapper | unfiled | — | ~2 wks* | BLOCKEDexec-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 + the classifier refresh cron (Sprint 2, never shipped) |
| StratLib | Alex onboarding: codify Range Break rules into catalog JSON | unfiled | alex | — | READY No upstream dependency — the one cleanly startable item |
| AMS | Phase 4 surface wiring starts: copy → auth-wrap inside ams/ → green-light | unfiled | claude | — | BLOCKED AMS Phase 1 sign-off never happened; 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 |
sprint=4 in todos.json — the work actually tagged to this sprint):| Project | Item | Status | Owner | Readiness |
|---|---|---|---|---|
| Exec | Backtest J3P plays (Focus-3/KITE) on SIP names — edge by playbook × grade × tier | in_progress | claude | READY Active now — the live thread of Sprint 4 |
| Exec | Wire setups.today.json → hotkey-engine for J3P-graded entries (SIM → forward-test) | pending | claude | READY V1 SIM already shipped; forward-test wiring outstanding |
| Exec | J3P backtest v1 engine + edge read + interactive chart viewers | completed | claude | closed 2026-06-27 — before the sprint window (retro-tagged) |
| Exec | J3P backtest expanded to WIDE 52-name canonical + runs registry + v2.4 plan | completed | claude | closed 2026-06-28 — before the sprint window |
| Exec | J3P v2.4 regime-filter matrix run end-to-end (shorts + Dale-trend + CBO + 6 filters) | completed | claude | closed 2026-06-29 — verdict: filtering narrows bleed, does not create edge |
Live Gr8Trade execution + StratLib expansion (7/27 → 8/07). Headline: enable Gr8Trade auto-execution in prod with conservative caps. That milestone inherits every blocker below it — the adapter, the forward-test, and the firm-confirm of Kore signatures all sit upstream and none has moved. Sprint 5 cannot start clean unless at least the Kore signatures land this week.| 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 the Trigger Engine to fire on live signals.” |
| Sprint 5 — live Gr8Trade auto-execution | Adapter + forward-test + Backup warm-runner | Plan critical path: warm-runner “must land BEFORE Exec goes live. If domino-1 dies, jimdo must keep alerts firing.” |
| Classifier parity test | liberator-datasource-blocker (blocked 45 d) | Note: kti liberator minute_bars entitlement dropped 27→10 datasets; every parity pair times out. |
| 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, 91 d) | Plan critical path #1: “Retires 4 user P0s, unblocks p0-daily-summary-view, the auto-classifier rule-based path, and 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.” |
| Plan # | Step | Owner | Est | Readiness |
|---|---|---|---|---|
| 1 | You run scientific-layer migrations 001–009 via psql tunnel Idle 91 days. Retires 4 user P0s; unblocks p0-daily-summary-view, the auto-classifier rule-based path, and identity_fn DB writes. Still #1, still untouched. | user | 15 min | READY |
| 2 | Jim ships the 2 Acct-v2 date-range bugs Open 76d / 70d. 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) Effectively delivered. atlas-flow-status shipped 7/13 as the working replacement — live + GREEN as of 7/21 7:00 PM ET. The original ticket stays open only for the DB-source half. | claude | 2 h | READY |
| 6 | Backup warm-runner online (heartbeat + delay+skip + liveness) Must land BEFORE Exec goes live — the Sprint 5 gate. If domino-1 dies, jimdo must keep alerts firing. Not started. | 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 — entitlements dropped 45 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. This is the Sprint 5 headline. | claude+jim | 2 wks | BLOCKED |
freshness.json last generated 2026-05-07 (76 days ago) and app-status.json froze 2026-07-08 12:01 ET at overall_status: RED (14 days ago, against a 30-min cadence). Neither has self-cleared — anything still reading them sees a stale RED. The working signal is now atlas-flow-status.json, GREEN at 7/21 7:00 PM ET. Action: retire or redirect the two dead files so they stop tripping false alarms.| Monitor | Status | Last generated | Age | Note |
|---|---|---|---|---|
| atlas-flow-status.json (current) | GREEN | 2026-07-21 7:00 PM ET | ~9.5 h | The replacement, stood up 7/13. Overall PASS. This is the signal to trust. |
| app-status.json (legacy) | RED | 2026-07-08 12:01 PM ET | 14 d | Host DESKTOP-AKU8I62. Frozen mid-probe; 10/12 sources last read GREEN, but that reading is 2 weeks old. |
| freshness.json (dead) | DEAD | 2026-05-07 9:38 PM ET | 76 d | Never cronned. Superseded. The original P0 ticket is the fix; atlas-flow-status covers the property half. |
| Age | Owner | Ticket |
|---|---|---|
| 96d | user | p0-indicator-alerts-ddl — dump + commit indicator_alerts schema as ground truth |
| 95d | user | journal-user-steps — 3 steps to finish journal persistence |
| 91d | user | run-scientific-layer-migrations — migrations 001–009 via psql tunnel (critical path #1) |
| 32d | user | ams-seed-users-from-main — seed main.users so identity_fn returns non-zero |
| 32d | user | ams-decisions-d1-through-d7 — resolve 7 open AMS decisions |
| 31d | user | pinepb-tradingview-setup-guide — TradingView setup guide for James |
| 31d | user | pinepb-deploy-to-james-tradingview — paste finalized Pine script into TradingView |
user bucket: 2 owned by jimbo (the Acct-v2 date-range bugs, 76 d / 70 d), 3 owned by james (mgp-historical-pages-cleanup 70 d, mgp-cron-skipped-5-14 68 d, nightly-pm-silent-gap 60 d), and 1 blocked (Liberator entitlements, 45 d). Backlog totals: 162 pending, 7 in progress, 2 blocked, 276 completed, 3 cancelled · 36 open P0.active_sprint_id has read 1 since 2026-06-26 ET; Sprint 1 stands at 0/8 after four full cycles. Do we re-commit those eight tickets, or formally cancel the ones that stopped mattering? Every EOD brief has flagged the stuck pointer for 10 days. Is advancing it a manual step, or should Nightly PM own it automatically?sprint-plan.html simply not tracking decisions we already made? On Monday, do we re-baseline the plan to match reality?run-scientific-layer-migrations is estimated at 15 minutes, sits at #1 on the critical path, retires four user P0s, and is 91 days idle. What is the real obstacle — access, risk, or that nobody has been asked? Can we simply run it during planning and clear the whole downstream stack?