Sprint Status · Monday 2026-08-03

Atlas Scrum Master · pre-planning brief. All times Eastern (ET). Source: todos.json + sprint-plan.html.
TIME UNTIL PLANNING: 67 MINUTES
Planning starts at 8:30 AM ET. This brief was scheduled for 7:00 AM ET and published at 7:23 AM ET — 23 minutes after schedule, and 67 minutes before the meeting.
First on-time sprint brief in six weeks. It is a real agenda, not a retrospective.
✓ The ledger is alive again. todos.json was last written 8/2 11:40 PM ET — 7.7 hours ago. Last Monday it had been frozen 8 days and every number on that brief was fiction. nightly-helper-stale-date-fix-2026-07-28 shipped on 7/28 (the nightly helper was silently reverting meta to 2026-05-01) and the backfill re-populated the missing weeks.
Proof it worked: last Monday this page reported 0 closes for 7/20–7/24. The same query today returns 9. Those tickets were always real — the writer just was not recording them. Every number below can be trusted.
16
Done last week (7/27–7/31)
0 / 6
Sprint 5 scope closed
5
Days left in Sprint 5
15
Carry-over from Sprints 1/3/4
39
Open P0
75
Open P1
7.7h
Ledger age

1Previous sprint review — week 1 of Sprint 5 (7/27 → 7/31 ET)

Tickets marked completed with a completed_at date inside the window, grouped by project codename. Sprint 5 is a 2-week sprint, so this is the first half of the sprint we are still inside — not a closed sprint.

16 tickets closed — the best week in the whole 4-week series (7 → 11 → 9 → 16). Output is genuinely up.
But: zero of them are Sprint 5 committed scope. All 16 were unplanned work — Swing Radar, sentiment-accuracy pages, Pine sessions, VWAP band research, chart mount guards. Good work, none of it what the sprint said it would do.
ProjectClosedTickets
untagged52026-07-28 · P2 claude · SIP + live-scan tooltips use line feeds (and a standing rule for every page)
2026-07-28 · P2 james · HUD scorecard-chart: mount-generation guard + ET day bucketing
2026-07-28 · P2 claude · VWAP Band Research System page
2026-07-28 · P2 claude · LYNCH Forward-Test Archive published
2026-07-28 · P1 claude · Nightly todos helper rewritten payload-driven (was silently reverting meta to 2026-05-01)
alerts-hotkeys-etc22026-07-27 · P3 claude · Backside Short radar + trigger listener pass
2026-07-27 · P3 claude · J3P Swing Radar surface published
scorecards12026-07-27 · P3 claude · v3 live runner wired headless + folded into run_all_eod
param_surface12026-07-27 · P3 claude · Param Surface + monthly reports fully regenerated
strategy_library12026-07-27 · P3 claude · LYNCH archive page published
playbooks12026-07-27 · P3 claude · June 2026 playbook data + best-of set rebuilt
accountability_hud12026-07-27 · P3 claude · Accountability v2: scorecard click-through + chart wiring (landed in PROD)
strategy-library12026-07-29 · P1 James · Pine session — Alpha Compression Break + Fashionably Late v2 suite advanced
system-hub12026-07-31 · P1 James · Sentiment-accuracy scoring pages published (SENTIMENT_ACCURACY + MTF_SENTIMENT_ACCURACY)
j3p12026-07-31 · P2 James · J3P surfaces published — Swing Radar, Cup Verify, Watcher
accountability12026-07-31 · P1 James · EOD catch-up backfilled 18 trader-days clean (ok=18 fail=0)

2Slippage — what has carried over

Two kinds of slippage: (a) Sprint 5's own committed scope, none of which has started with 5 working days left; (b) tickets tagged to Sprints 1, 3 and 4 that are still open.

(a) Sprint 5 committed scope — week 1 progress
ProjectCommitted itemStatus nowOwnerAge
ExecEnable Gr8Trade auto-execution in prod with conservative caps (1 share, 1 order/day, 3-symbol whitelist)blocked P2claude38d
ExecDaily review of every executed order — calibrate caps weeklyNO TICKET EXISTSunassigned—
StratLibAlex Range Break walk-forward backtest at /backtests/range-break/pending P1alex89d
StratLibRegister Range Break in /strategies/ Library + canonical catalogpending P1alex89d
MultiTraderFirst Trader-of-the-Week session with Nolanpending P1user89d
MTFVPRoberto: TradingView ticket-in handler (Path B)pending P1claude89d
0 of 6 Sprint 5 items have moved off pending in week 1. One is blocked, one has no ticket at all, and the four that are merely pending are 44–89 days old — they were pending before Sprint 5 started. With 5 working days left, finishing all six is not on the table. Planning today is a re-scope, not a kickoff.
(b) Older sprint tags still open — 15 tickets
Sprint 1 ended 6/26 (38 days ago), Sprint 3 ended 7/10, Sprint 4 ended 7/24. These have survived every sprint boundary since.
SprintTicketOwnerStatusAge
S1P0 Atlas 1/6 Data-freshness dashboard: /system/freshness.json + banner on hubclaudepending108d
S1P0 Acct-v2 BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)jimbopending88d
S1P0 Acct-v2 BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)jimbopending82d
S1P0 AMS AMS: seed main.users with trader rows so identity_fn returns non-zerouserpending44d
S1P0 AMS AMS: create main.remembered_devices table (migration 002) — Phase 1 hard dependencyclaudepending44d
S1P0 AMS AMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop)userpending44d
S1P1 AMS AMS: write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md (Phase 3a baseline shipped, what's left)claudepending44d
S1P1 Backup Backup: mirror scheduled-task SKILL files from domino-1 to jimdo via scpclaudepending44d
S3P1 PinePB J3P — live smoke test: TV alert -> webhook -> indicator_alerts row (1 SIP name)claudepending38d
S3P2 PinePB J3P — FashLate-style label/alert polish (compact toggle + per-play templates)claudepending38d
S3P2 PinePB J3P v2.3 — rebuild Trend play as Dale VWAP 1st-deviation pullback (retire 9-EMA trigger)claudepending38d
S3P1 SIP Deploy J3P across SIP master_watchlist (TV layout + webhook alert per symbol)claudepending38d
S3P2 SIP Auto-sync /sip/watchlist.json -> TradingView symbol list for J3P coverage rotationclaudepending38d
S4P1 Exec Backtest J3P plays (Focus-3/KITE) on SIP names — edge by playbook x grade x tier before hotkeysclaudein progress38d
S4P1 Exec Wire setups.today.json -> hotkey-engine for J3P-graded entries (SIM -> forward-test)claudepending38d

3This sprint's goal

Sprint 5 · week 2 of 2 · 5 working days left
Live Gr8Trade execution + StratLib expansion
todos.json: 2026-07-27 → 2026-08-07  ·  sprint-plan.html: 7/26 → 8/08  ·  2 weeks  ·  Sprint 6 opens 8/10
Theme: The milestone where the system starts paying for itself. Real Gr8Trade orders behind conservative caps.
⚠ The board still does not agree that Sprint 5 exists. active_sprint_id is 1 (“Foundation hardening + AMS unblock”, 2026-06-22 → 2026-06-26) — the sprint that was supposed to end 6/26. This was the #1 recommendation of last Monday's brief and it did not happen. The ledger half of that recommendation did get fixed; the sprint-bookkeeping half did not. Every sprint-scoped number on this page still has to be reconstructed from the plan page rather than read off the board. It is a 2-minute edit. Do it in the room.

4This sprint's backlog

The six items sprint-plan.html commits to Sprint 5, matched to live tracker tickets. Estimated days are Atlas estimates — the tracker has no estimate field, so these size the conversation, they are not a commitment.

ProjectItemStatusOwnerEst.Ticket
ExecEnable Gr8Trade auto-execution in prod with conservative caps (1 share, 1 order/day, 3-symbol whitelist)blocked P2claude5dexec-kore-live-j3p
ExecDaily review of every executed order — calibrate caps weeklyNO TICKETunassigned2d—
StratLibAlex Range Break walk-forward backtest at /backtests/range-break/pending P1alex3dalex-range-break-backtest
StratLibRegister Range Break in /strategies/ Library + canonical catalogpending P1alex1dalex-range-break-register
MultiTraderFirst Trader-of-the-Week session with Nolanpending P1user1dphase-4-trader-of-the-week
MTFVPRoberto: TradingView ticket-in handler (Path B)pending P1claude4dmtf-vp-tradingview-handler
Total committed16d
16d of estimated work against 5 working days left. Velocity over the last 4 weeks averages 10.8 tickets/week — but that measures ticket count, not sprint scope, and the sprint-scope rate for week 1 was 0. Two of these six (Range Break backtest + register) are owned by Alex, who has never started any of his 3 tickets in 89 days. Realistically: pick one, maybe two.

5Dependencies — what blocks what

No ticket in the tracker has a depends_on field (0 of 496 — unchanged from last week). Everything below is inferred from ticket notes, the critical path, and the plan page. Adding real depends_on data is itself a candidate ticket — it is the reason this section is hand-reasoned every Monday.

Sprint 5 itemBlocked by (inferred)
Exec Enable Gr8Trade auto-execution in prod with conservative caps (1 share, 1 order/day, 3-symbol whitelist)Trigger Engine (not started) → Risk Gate (no ticket) → Gr8Trade adapter (pending, 44d) → firm-confirm on Gr8Script/Kore call signatures. Ticket itself is status=blocked.
Exec Daily review of every executed order — calibrate caps weeklyNothing executes until the item above ships. Cannot start.
StratLib Alex Range Break walk-forward backtest at /backtests/range-break/alex-range-break-rules (Sprint 4 carry-over, pending 89d) must be codified first.
StratLib Register Range Break in /strategies/ Library + canonical catalogThe backtest above must pass first. Two links back in the same chain.
MultiTrader First Trader-of-the-Week session with NolanPlan says deferred until classifier reliable. Classifier refresh cron still has no ticket and no owner.
MTFVP Roberto: TradingView ticket-in handler (Path B)None technically. But the plan says Roberto and the ticket says owner=claude — nobody has actually picked it up in 89 days.
The chain, in one line:
James runs migrations → classifier can write DB → Roberto's refresh cron makes classify/*.json live → Trigger Engine can poll it → Alert Channels fan out → Risk Gate checks the alert → Gr8Trade adapter turns it into an order → caps + daily review. Sprint 5's headline goal is the last link. The first three links have not moved in 103 days, and there are 5 working days left.

6Critical path stack — sorted by readiness

Top 7 from sprint-plan.html, re-sorted so everything that can start today with nothing in its way is on top.

1
James runs scientific_layer migrations 001–009 via psql tunnel READY
user · 15 min · ticket 103d old — Nothing blocks it. James needs a psql tunnel and a quarter of an hour.
Retires 4 user P0s · unblocks p0-daily-summary-view, the rule-based classifier path, and identity_fn DB writes.
2
Jim ships the 2 Acct-v2 date-range bugs READY
jimbo · 2 P0s · ticket 88d old — Nothing blocks it. Both bugs reproduce on any non-5-day range.
Until these land, no metric on a multi-day HUD view can be trusted — blocks any team rollout.
3
Atlas ships p0-freshness-dashboard MVP (property side) READY
claude · 2h · ticket 108d old — Property-side half needs no DB. Could ship before lunch. 108 days old.
Closes the Phase 0 freeze — and 3 properties are stale right now with nothing watching them.
6
Backup warm-runner online (heartbeat + delay+skip + liveness) READY
claude · 3 days — Nothing blocks it. Backup tickets open, none started.
Must land BEFORE Exec goes live. If domino-1 dies, jimdo has to keep alerts firing.
4
Classifier refresh cron ships (Roberto) AT RISK
roberto · 4h — Still no Roberto-owned ticket in the tracker for this. Unassigned in practice, 6 weeks running.
classify/*.json must refresh every minute during RTH before the Trigger Engine can fire on live signals.
5
Exec Trigger Engine + Alert Channels in DEV BLOCKED
claude · 1 wk · ticket 44d old — Waits on step 4 (classifier must be live to poll). Ticket pending, 44d, never started.
First half of the execution arm. Alerts to humans only at this stage — no orders.
7
Exec Gr8Trade adapter enabled in prod with caps BLOCKED
claude+jim · 2 wks · ticket 38d old — Waits on steps 4, 5, 6 — and on firm confirmation of Gr8Script/Kore call signatures.
This is Sprint 5's headline goal. It sits at the far end of a chain whose first three links have not moved.
4 of the 7 are READY — and they were the same 4 last Monday. Steps 1, 2, 3 and 6 have nothing in their way and none of them moved in a 16-ticket week. That is the whole story of this sprint: the team ships hard on whatever is in front of it, and the critical path is never what is in front of it. The bottleneck is attention, not dependencies.

7Velocity trend

Tickets marked completed, Monday → Friday, last 4 weeks. Read this as throughput, not sprint progress — almost none of it was committed scope.

Week (Mon–Fri)Closed
7/6 → 7/107
7/13 → 7/1711
7/20 → 7/249
7/27 → 7/3116
4-week average: 10.8/week, trend rising. Last Monday this chart ended in a 0 and the conclusion was “the ledger is broken.” That was right — the same 7/20 week now reads 9. The remaining question is not how much the team ships, it is whether any of it is the sprint.

8Stale alarms

Human-owned P0s open longer than 14 days — 12 of them
OwnerProjectTicketAge
userAtlas6/6 indicator_alerts DDL audit: dump schema, commit as ground truth108d
userMultiTraderUSER: 3 steps to finish journal persistence107d
userMultiTraderUSER: run scientific_layer migrations 001–009 via psql tunnel103d
jimboAcct-v2BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)88d
jamesAtlasCompliance follow-up: delete (or hide) historical MGP pages 4/17 through 5/12 — they still contain Vital Knowledge text82d
jimboAcct-v2BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)82d
JamesAtlasBUG: MGP auto-fire skipped 5/14 mid-day + recap; 5/15 morning ran ~2h45m late80d
jamesAtlasNightly PM daemon went dark 5/20-5/22 (3 consecutive missed fires) — fix wake/launch72d
userAMSAMS: seed main.users with trader rows so identity_fn returns non-zero44d
userAMSAMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop)44d
userPinePBTradingView setup guide for James — paste Pine script, configure alerts, test43d
userPinePBJames pastes finalized Pine script into TradingView + configures the 3 alerts43d
Plus 13 human-owned P1s over 14 days old. Median human-owned P0 age: 82d — every one of these is older than the sprint that was supposed to contain it.
Blocked on a human decision — 4 tickets
These are not work items. They are questions waiting for an answer, and nothing downstream of them can move.
ProjectTicketOwnerAge
P0 ClassifierLiberator minute_bars entitlement LOST (27->10 datasets) — Stage B mechanism backfill now BLOCKED on dataclaude57d
P2 ExecAutomate J3P execution via Kore backend (firm-confirm Gr8Script -> forward -> live)claude38d
P0 untaggedDECISION: SIP top-10 is always catalyst-sweep names — pick a rebalance optionjames6d
P0 untaggedDECISION: demote revbreak_long from the validated set (confidently negative live)james6d
Property freshness — probed directly off a2 disk just now (7:23 AM ET)
Not read from app-status.json: that file is itself 25 days old, so the freshness monitor still cannot report on freshness.
PropertyNewest fileAgeThreshold
MGP (Morning Game Plan)2026-08-03 06:49 ET0.6h24hOK
SIP (Stocks in Play)2026-08-03 07:22 ET0.0h24hOK
Scorecards2026-08-02 16:56 ET14.4h30hOK
Multi-TF Stack2026-08-03 07:22 ET0.0h24hOK
Playbooks2026-07-06 21:16 ET658.1h30hSTALE
Strategy Library2026-06-17 18:35 ET1116.8h720hSTALE
PM ledger (todos.json)2026-08-03 01:21 ET6.0h48hOK
Freshness monitor (app-status.json)2026-07-08 12:01 ET619.4h48hSTALE
3 properties past threshold — but the PM ledger is no longer one of them. The three still dark: Playbooks (last written 7/6, 27 days), Strategy Library (6/17, 46 days), and the freshness monitor itself (7/8, 25 days — nothing is watching the watchers). All trading-facing surfaces (MGP, SIP, Scorecards, Multi-TF) are current, some written within the hour. The outage is confined to the PM/monitoring lane, and it is one ticket — p0-freshness-dashboard, critical-path step 3, READY, 108 days old.

9Pre-meeting questions

Answer these before committing to anything. Each one is a real fork in the road.

  1. Sprint 5 has 5 working days left and 0 of 6 committed items started. Do we re-scope to one item, or do we admit Sprint 5 is already spent and plan Sprint 6 today?This is the only question that has to be answered this morning. The honest options are (a) pick one item, finish it by Friday, roll the rest to Sprint 6; or (b) declare Sprint 5 closed at 0/6, close it cleanly, and use today to plan Sprint 6 properly. Atlas recommendation: (a) with exactly one item — Trigger Engine MVP in DEV. A one-item sprint that lands beats a six-item sprint that does not.
  2. The team closed 16 tickets last week and none of them were the sprint. Is the sprint plan wrong, or is the work wrong?Four straight sprints now: high throughput, zero committed-scope completion. That pattern does not mean the team is failing — it means the plan describes work nobody is actually choosing to do. Either the plan is aspirational and should be rewritten to match what gets picked up, or the plan is right and something has to change about how the week starts. Pick one. Carrying both is what produced 0/6.
  3. active_sprint_id is still 1. This was last Monday's #1 recommendation. Who owns closing Sprints 1–4 today, in the room?The ledger half of that recommendation shipped (7/28) and the results are visible all over this page. The bookkeeping half is a 2-minute edit that has now survived six sprint briefs. Proposed: close Sprints 1–4, move the 15 survivors to backlog, set active_sprint_id=5, and stop reconstructing sprint state from a June HTML page.
  4. James is carrying P0s aged 44–108 days, including the 15-minute migration that unblocks four others. Is he available this sprint, or do we hand the tunnel to Atlas?run-scientific-layer-migrations is 103 days old and is step 1 of the critical path. It needs a psql tunnel and a quarter of an hour. This is its fifth sprint. If there is genuinely no window, the honest move is to hand the credentials to Atlas rather than carry it a sixth time.
  5. Acct-v2 has 2 P0 date-range bugs sitting with Jim at 88 and 82 days. Is Jim in this sprint, or does Acct-v2 formally defer to Sprint 6?The HUD is off-limits to Atlas by standing rule, so these cannot be reassigned — only scheduled or dropped. Until they land, no multi-day HUD metric can be trusted, which blocks the multi-trader rollout entirely. A clean “deferred to Sprint 6” is worth more than a fifth silent carry.
  6. Two P0 decisions have been blocked on James for 6 days — SIP rebalance and the revbreak_long demotion. Can we close both in this meeting?Neither is work; both are a yes/no. sip-scoring-rebalance-decision and revbreak-long-demotion-decision each gate downstream tickets, and 6 days is already long for a decision that fits in a sentence. Cheapest two items on the whole board — take them first, before the re-scope conversation.
  7. Alex owns 3 tickets and has started none in 89 days. Roberto owns 2 and the classifier cron has no ticket at all. Are these real commitments?Two of Sprint 5's six items are Alex's Range Break chain; a third is Roberto's MTF-VP Path B, which the plan assigns to Roberto but the tracker assigns to claude. The classifier refresh cron — critical-path step 4 — still has no ticket six weeks after it was first flagged. Either get a verbal commit in the room today, or move all three out of the sprint and stop counting them as capacity.

Atlas recommendation for the room

Sprint 5 has 5 days left. Do not re-commit six items. Commit these, in this order:
#CommitOwnerTimeWhy this one
1Answer the 2 blocked P0 decisions (SIP rebalance, revbreak_long demotion) james10 minIn the room, today. They are sentences, not projects, and they gate downstream work.
2Close Sprints 1–4, move survivors to backlog, set active_sprint_id=5 claude2 minSixth brief carrying this. Until it lands, no sprint number on any page is real.
3James runs scientific_layer migrations 001–009 user15 min103 days old. Retires 4 P0s and unblocks the entire classifier → Exec chain.
4Atlas ships p0-freshness-dashboard MVP (property side) claude2h3 properties are stale right now and nothing is watching. Closes the Phase 0 freeze.
5The one real sprint item: Exec Trigger Engine MVP + Alert Channels in DEV clauderest of weekAlerts to humans only. Live Gr8Trade orders are Sprint 6 at the earliest — that chain cannot compress into 5 days.
Items 1–3 total under 30 minutes of human time and retire more blocked work than the last three sprints combined. Everything else in Sprint 5 scope — Gr8Trade live execution, the Range Break chain, Trader-of-the-Week, MTF-VP Path B — rolls to Sprint 6 with an owner named out loud, or gets dropped.