Morning Brief · ATLAS Standup

Wednesday, August 5, 2026 — published 8:22 AM ET · on schedule (7:53 AM ET cron, 29 min build) · all briefings →
⏰ 8 minutes until standup (8:30 AM ET)
4
shipped overnight
29
stale blockers
39
open P0
78
open P1
190
open total
2 / 2
monitors dead
8
days decisions stuck
✔ Nightly PM fired on time — fourth night running. nightly-project-manager ran 2026-08-04 11:04 PM ET. /todos/daily/2026-08-04.md was written (5.4 KB, 11:22 PM ET) alongside the HTML edition (10.9 KB, 11:23 PM ET), and todos.json was rewritten 11:40 PM ET. No silent-failure pattern this cycle. Its own note flags that the HUD/trading-dev subtree scan ran past the 5-minute foreground window and landed after the writeup was first rendered — the HUD entry below is the late finding.

What shipped overnight completed 2026-08-04 ET · 4 items

Three of four are claude-owned; the fourth is a file-timestamp observation, not a closed ticket. Zero human-owned work was actually completed overnight — the eighth straight publishing day that produces the unchanged 29-row blocker table below.

Today’s standup focus 3 picks · see ranking note

#1 · Decide in the room · P0 · blocked 8 days · the alibi is gone
Demote revbreak_long — yesterday removed the only argument for keeping it
For a week this call stalled on one fact: the play kept having the occasional green day, most recently Monday (+$219 on 15 trades). Yesterday it went 2 of 18 for −$1,129 — the worst play on the board for the day, and the lower bound moved the wrong way again: LB-90 −0.41 → −0.42 on n=332, both-halves check still failing. There is now no green-day counterweight to point at. It is a one-sentence call and it fires again every day it stays in the validated set.
james · revbreak-long-demotion-decision-2026-07-28
#2 · Decide in the room · P0 · blocked 8 days
SIP top-10 rebalance — pick one of the three options
Unchanged since Monday because nothing can change it but you. Catalyst contributes 21.6–36.0 pts against mover 1.5, rrg 2.2, liquidity ≤10, so technical scanner hits (PVP / PBS / GAPMA / LYNCH) cannot reach the top-10 on their own. Options: (1) reserve ~3 of 10 slots for the best non-catalyst technicals, (2) cap catalyst at ~22 with earnings-over-PR tiering, (3) add a scanners component at +6 per family capped at 18. Second day in a row this appears here with no new evidence to add — that is the point.
james · sip-scoring-rebalance-decision-2026-07-28
#3 · 15 minutes of your time · P0 · open 105 days
Run scientific_layer migrations 001–009 via the psql tunnel
Still step 1 of the critical path, and it has now been step 1 on every brief since the chain was written. Retires 4 user-owned P0s in one go and unblocks p0-daily-summary-view, the rule-based auto-classifier path, sizing-calculator DB wiring and identity_fn DB writes. Highest ratio of unblocked-work to minutes-spent anywhere on the board, and it has been that for 105 days.
user · MultiTrader · run-scientific-layer-migrations
Ranking note — where I departed from the formula, again. Straight priority×age now returns a six-way tie at 333: the Phase-0 items 1/6 through 6/6, all 110 days old, none of which has moved in nearly four months. That is the third consecutive brief where age-weighting stops discriminating. I ranked instead by what can actually change between 8:30 and 9:00 AM ET: two P0 decisions that need one sentence each from James — and #1’s deciding evidence landed at 4:30 PM ET yesterday — plus the 15-minute critical-path item that retires four P0s. The Phase-0 six are still open and still counted in the 39.

Freshness alerts no working freshness signal on the hub · day 2 confirmed

⚠ /system/freshness.json — frozen 90 days. Last generated 2026-05-07 9:38 PM ET by a manual PowerShell run. Every property inside it still reads "status":"fresh", which is false for all of them. Its own fix ticket — “Cron /system/update_freshness.py to keep the freshness strip auto-refreshing” — is a P1 that has now been open 91 days.
⚠ /system/app-status.json — the replacement monitor, frozen 28 days. Last probe 2026-07-08 12:01 PM ET from DESKTOP-AKU8I62. It reports overall_status: RED with 2 of 12 sources red — Playbooks (38.7 h vs a 30 h threshold) and Param Surface (DB) (340.7 h vs 30 h) — but those ages are themselves 28 days old, so the panel is measuring nothing today. The 30-minute watchdog meant to keep it alive is not firing.
⚠ I said I would fix this yesterday and I did not. Yesterday’s brief closed with: “the freshness dashboard MVP … is the highest-value thing on my own queue today, and I will take it unless standup redirects me.” p0-freshness-dashboard is still pending at 110 days — not started. Overnight went to the AMSB playbook, the Stockbee pair and the SIP CSV instead. Either it gets committed in the room this morning or I stop putting it in the brief.
⚠ todos-scan-twice-daily cron — now 7 fires behind. Last run 2026-08-01 5:05 PM ET; scheduled 5 AM and 5 PM daily, so it has missed roughly seven consecutive fires and todos_snapshot.md delta tracking is four days stale. Every other Atlas cron (nightly PM, MGP ×6, morning brief, EOD brief, multi-tf daemon launcher) fired on schedule in the last 24 h.
⚠ Two real findings from last night were never ticketed. (1) The scorecard commission model — the 6 PM brief showed its flat $0.01/share assumption billing $110 against a real $72.44 and flipping the sign of James’s day (scorecard −$2.58 vs actual +$36.18 net). It was called a new P1 in the brief; there is no matching ticket on the board this morning. (2) Duplicate MGP sends — every edition emailed twice on both 8/3 and 8/4 (06:48/08:35, 11:38/11:43, 16:40/16:44, all ET); idempotency is not suppressing the second fire. Noise rather than damage, but also unticketed. Both are in the prose of last night’s note and in neither the ledger nor any Gantt.

Stale blockers 29 rows · owner ≠ claude · pending · P0/P1 · age ≥ 7 d

AgeProjectOwnerPriTitle
110 dAtlasuserP06/6 indicator_alerts DDL audit: dump schema, commit as ground truth
109 dMultiTraderuserP0USER: 3 steps to finish journal persistence
109 dMultiTraderuserP1Re-run gen_scorecard.py ON a2 (or via tunnel) and confirm enrichment populates
106 dAtlasuserP1Deploy z_activity_scanner.py on each Windows machine via Task Scheduler
105 dMultiTraderuserP0USER: run scientific_layer migrations 001–009 via psql tunnel — critical-path step 1
91 dAtlasuserP1Cron /system/update_freshness.py to keep freshness strip auto-refreshing
91 dMultiTraderuserP1Trader-of-the-Week scorecard review session (Nolan / Preston / Brian / Thomas)
91 dMultiTraderuserP1First-scorecard feedback session with each of the 4 traders
91 dStratLibalexP1Codify Range-Break strategy rules from Alex’s Notion (entry / stop / target / best-when)
91 dStratLibalexP1Range-Break: walk-forward backtest published at /backtests/range-break/
91 dStratLibalexP1Register Range-Break in /strategies/ Strategy Library + canonical catalog
91 dClassifierrobertoP1Live Classifier HUD: auto-refresh classify/<SYMBOL>.json during market hours — critical-path step 4
91 dClassifieruserP1Review Roberto’s Claude artifact + slot his real work into the right property
90 dAcct-v2jimboP0BUG: Risk Bump Progress bar ignores the selected date range (always 5-day rolling) — current_priority_id
90 dAcct-v2jimboP1Move accountability-v2 Node services from nohup → Windows Task Scheduler
90 dAcct-v2jimboP1Wire v1 fills-poller to also POST into v2 /api/ingest.php (dual-write transition)
90 dAcct-v2userP1Upload AccountabilityTickBridge.py to KITE forward-test + verify ticks flow into marks_live
90 dAcct-v2userP1Trade Action Requests feature — finalize close/stop intent flow
90 dAcct-v2userP1Execute dev→prod promotion sequence per docs/PROMOTE-DEV-TO-PROD.md
89 dAtlasuserP1Test mklink workaround for Claude Code “suspicious path pattern” prompt on WebDAV projects
89 dAcct-v2userP1Decide whether Risk Manager HUD (/accountability/risk.html, mock) is redundant
84 dAtlasjamesP0Compliance follow-up: delete or hide historical MGP pages 4/17–5/12
84 dAcct-v2jimboP0BUG: Ticket Meter denominator doesn’t scale with date range (1901 / 30 on a 13-day MTD range)
82 dAtlasJamesP0BUG: MGP auto-fire skipped 5/14 mid-day + recap; 5/15 morning ran ~2h45m late
74 dAtlasjamesP0Nightly PM daemon went dark 5/20–5/22 (3 consecutive missed fires) — fix wake/launch
46 dAMSuserP0AMS: seed main.users with trader rows so identity_fn returns non-zero
46 dAMSuserP0AMS: resolve 7 open decisions D1–D7 (domain / auth stack / DB strategy / sharing / risk)
45 dPinePBuserP0TradingView setup guide for James — paste Pine script, configure alerts, test
45 dPinePBuserP0James pastes finalized Pine script into TradingView + configures the 3 alerts
Eighth straight publishing day at 29 rows: 29 in, 29 out, none retired, none added. Ten are P0. The oldest five have now been open longer than the entire Sprint 1–6 plan they sit in front of.

Open P0 by project 39 open · pending + in-progress + blocked

Sprint reality check: active_sprint_id is still 1 — a window that closed 2026-06-26 at 0 of 8 — while the calendar says Sprint 5, day 8 of 10, closing Friday 8/7. The only Sprint-5-tagged ticket on the board (exec-kore-live-j3p) is blocked pending firm-confirm of the Gr8Script/Kore call signatures. Sprint 5 will close without its goal.

Critical path · next step from /system/sprint-plan.html

Step 1 — still unstarted, day 105: you run scientific-layer migrations 001–009 via the psql tunnel
user · ~15 min. Nothing downstream on the seven-step chain has moved, because step 1 has not. It retires 4 user-owned P0s and unblocks p0-daily-summary-view, the rule-based auto-classifier path, sizing-calculator DB wiring and identity_fn DB writes. Steps 2 (Jim’s two Acct-v2 date-range bugs) and 4 (Roberto’s classifier refresh cron) are also untouched, at 90 and 91 days.

The one step Atlas can move without a human is still step 3 — the freshness dashboard MVP, property side, ~2 h. I named it yesterday and did not do it. Both monitors are confirmed dead for a second consecutive morning, so this is the same recommendation with one more day of evidence: give me the go-ahead in the room and it ships today, or cut it from the brief and stop tracking a freshness signal nobody maintains.