Morning Brief · ATLAS Standup

Thursday, July 16, 2026 · generated 8:13 AM ET by Atlas Scrum Master · all times ET
⏰ 16 min until standup (8:30–8:45 AM ET)

What shipped overnight tickets closed Wednesday 2026-07-15

Cross-check against last night's PM writeup: no net-new source code landed on 7/15 (confirmed empty across reports/, accountability-v2, scripts, indicators/src, ddl, db_reports). It was an output day: the 3rd consecutive live earn_gap_reclaim test session, all surfaces regenerated, all 3 MGP editions clean, LYNCH archive rebuilt (3 days / 4 picks / 3 SIP hits / 0 outcomes yet). Full writeup →

Pipeline health did the robots do their jobs?

✓ Nightly PM
Ran 2026-07-15 11:04 PM ET and wrote /todos/daily/2026-07-15.md. Healthy — no silent-failure repeat.
⚠ Morning Brief (this one)
Fired on 7/14 and 7/15 and published NOTHING both days — silent. Last brief on disk before today was 7/13. This page ends a 2-day gap.
✓ MGP (all 3 editions)
Morning 05:42 + v2 06:49, midday 11:30 + v2 11:38, recap 16:31 + v2 16:41 on 7/15. All emailed clean.

Freshness alerts 3 of 4 monitors not trustworthy

StateMonitorLast real updateAgeWhat it means
DEAD/system/freshness.json (the file this brief was spec'd to read)2026-05-07 21:38 ET69.4 daysFrozen for 70 days. Superseded and no longer written by anything. The /system/ hub still reads it, so the hub is showing 70-day-old data.
DARK/system/app-status.json (the replacement watchdog)2026-07-08 12:01 ET7.8 daysoverall_status was RED when it froze. Zero [WATCHDOG] emails in 8 days. This is the 8th consecutive day dark.
LYING/system/atlas-flow-status.json (quick-check twin)2026-07-10 15:00 ET5.7 daysWorst kind of stale: a nightly batch bumps the file mtime (touched 7/15 20:40) while the content stays frozen at 7/10 and RED 2-fail. Looks alive, is not.
GREEN/system/atlas-flow-full.json (FULL execution test)2026-07-15 20:30 ET11.7 h13/13 pass, 628s. This is the only freshness signal that is actually alive. It should be the canonical one.
Plain English: you have four smoke detectors. Three are dead — and one of the dead ones still blinks a green light, because a nightly job touches the file without refreshing what's inside it. Only atlas-flow-full actually works. The fix is a decision, not code: make atlas-flow-FULL the one canonical monitor, retire the other three, point the alert email at it.

Today's standup focus top 3 of 107 open P0/P1, ranked by priority × age

1
Atlas 1/6 Data-freshness dashboard: /system/freshness.json + banner on hub
P0 · owner claude · open 90 days · weight 270 (priority × age)
Nightly PM has put this #1 three nights running and it still has not been done. It is also live right now: every freshness monitor except atlas-flow-FULL is dark, so the alarm that catches every other break is itself broken. Decide: make atlas-flow-FULL the one true monitor, retire app-status.json and the stale -status twin.
2
MultiTrader USER: run scientific_layer migrations 001–009 via psql tunnel
P0 · owner user · open 85 days · weight 255 (priority × age)
Critical-path step 1, and it is a 15-minute job. It has been waiting 85 days. Running it closes 4 P0s that belong to James and unblocks the daily_summary view, the rule-based classifier, and identity_fn DB writes. Nothing downstream moves until it runs.
3
Acct-v2 BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)
P0 · owner jimbo · open 70 days · weight 210 (priority × age)
Critical-path step 2 (Jim). Two date-range bugs mean no number on a multi-day view can be trusted, which blocks showing the HUD to any other trader.
How these were picked: weight = (P0 × 3, P1 × 1) × days open. Six Phase-0 tickets tie at the top (all 90 days, all P0, weight 270), so the tie was broken by the critical-path order on sprint-plan.html and by which items unblock the most other work. Full P0 spread is below.

Critical path · next step what unblocks the most

1
James runs scientific-layer migrations 001–009 via psql tunnel NEXT · UNBLOCKED
user · ~15 min · open 85 days. Retires 4 user P0s and unblocks p0-daily-summary-view, the rule-based auto-classifier path, and identity_fn DB writes. This is the first item in the chain that nothing else is waiting on — it can be done today.
2
Jim ships the 2 Acct-v2 date-range bugs
jimbo · 2 P0s (70d / 64d). Until these land, no metric on a multi-day view can be trusted, which blocks any team rollout.
3
Atlas ships the freshness-dashboard MVP (property side)
claude · ~2h. Completes the Phase 0 freeze. Now overlaps with the live monitor outage above — the same decision closes both.
4
Classifier refresh cron ships (Roberto)
roberto · ~4h. classify/*.json must update every minute during RTH before the Trigger Engine can fire on live signals.

Open P0s by project 36 total · top 3 oldest each

Atlas 13 open P0
90d 1/6 Data-freshness dashboard: /system/freshness.json + banner on hub claude
90d 2/6 Pipeline orchestrator: run_nightly.py calls every generator, logs to one place, fails loud claude
90d 6/6 indicator_alerts DDL audit: dump schema, commit as ground truth user
SIP 7 open P0
26d Catalyst feed: Vital Dawn + Finnhub news + SEC 8-K + Benzinga RSS into per-symbol catalyst_score claude
26d Publish ranked watchlist.json + /sip/index.html (top 15-20 · refreshes pre-market + every 30m RTH) claude
26d Integrate SIP into Trigger Listener: gate alerts on watchlist · enrich payload with score + catalyst + RRG claude
MultiTrader 4 open P0
90d 3/6 main.daily_summary SQL view: kills duplicate computation claude
89d USER: 3 steps to finish journal persistence user
85d USER: run scientific_layer migrations 001–009 via psql tunnel user
AMS 4 open P0
90d 4/6 Identity function: resolve_user(account_id) -> (user_id, trader_name) claude
26d AMS: seed main.users with trader rows so identity_fn returns non-zero user
26d AMS: create main.remembered_devices table (migration 002) — Phase 1 hard dependency claude
PinePB 4 open P0
25d Codify VWAP Pull-In + Trend Trade + Backside Scalp rules in Pine-compatible terms claude
25d Write Pine v5 indicator combining all 3 playbooks with toggle inputs claude
25d TradingView setup guide for James — paste Pine script, configure alerts, test user
Acct-v2 2 open P0
70d BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month) jimbo
64d BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range) jimbo
StratLib 1 open P0
90d 5/6 Param Surface as strategy registry: /param-surface/ index + per-strategy grid pages claude
Classifier 1 open P0
39d Liberator minute_bars entitlement LOST (27->10 datasets) — Stage B mechanism backfill now BLOCKED on data claude

Stale blockers 29 items · not Atlas-owned · P0/P1 · open 7+ days

AgeProjectOwnerPriTitle
90dAtlasuserP06/6 indicator_alerts DDL audit: dump schema, commit as ground truth
89dMultiTraderuserP0USER: 3 steps to finish journal persistence
89dMultiTraderuserP1Re-run gen_scorecard.py ON a2 (or via tunnel) and confirm enrichment populates
86dAtlasuserP1Deploy z_activity_scanner.py on each Windows machine via Task Scheduler
85dMultiTraderuserP0USER: run scientific_layer migrations 001–009 via psql tunnel
71dAtlasuserP1Cron /system/update_freshness.py to keep freshness strip auto-refreshing
71dMultiTraderuserP1Trader-of-the-Week scorecard review session (rotating: Nolan / Preston / Brian / Thomas)
71dMultiTraderuserP1First-scorecard feedback session with each of the 4 traders
71dStratLibalexP1Codify Range-Break strategy rules from Alex's Notion (entry / stop / target / best-when)
71dStratLibalexP1Range-Break: walk-forward backtest published at /backtests/range-break/
71dStratLibalexP1Register Range-Break in /strategies/ Strategy Library + canonical catalog
71dClassifierrobertoP1Live Classifier HUD: auto-refresh classify/<SYMBOL>.json during market hours
71dClassifieruserP1Review Roberto's Claude artifact + slot his real work into the right property
70dAcct-v2jimboP1Move accountability-v2 Node services from nohup → Windows Task Scheduler (production-grade)
70dAcct-v2jimboP1Wire v1 fills-poller to also POST into v2 /api/ingest.php (dual-write transition)
70dAcct-v2userP1Upload AccountabilityTickBridge.py to KITE forward-test + verify ticks flow into marks_live
70dAcct-v2userP1Trade Action Requests feature — finalize (close/stop intent flow: hud-orderlab + migration 021 + trade-action.php)
70dAcct-v2userP1Execute dev→prod promotion sequence per docs/PROMOTE-DEV-TO-PROD.md
70dAcct-v2jimboP0BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)
69dAtlasuserP1Test mklink workaround for Claude Code 'suspicious path pattern' prompt on WebDAV-backed projects (unblocks nightly PM routine + agentic sessions)
69dAcct-v2userP1Decide whether Risk Manager HUD (/accountability/risk.html, mock) is redundant with Accountability HUD (/live-accountability-v2/hud/) — merge or retire
64dAtlasjamesP0Compliance follow-up: delete (or hide) historical MGP pages 4/17 through 5/12 — they still contain Vital Knowledge text
64dAcct-v2jimboP0BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)
62dAtlasJamesP0BUG: MGP auto-fire skipped 5/14 mid-day + recap; 5/15 morning ran ~2h45m late
54dAtlasjamesP0Nightly PM daemon went dark 5/20-5/22 (3 consecutive missed fires) — fix wake/launch
26dAMSuserP0AMS: seed main.users with trader rows so identity_fn returns non-zero
26dAMSuserP0AMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop)
25dPinePBuserP0TradingView setup guide for James — paste Pine script, configure alerts, test
25dPinePBuserP0James pastes finalized Pine script into TradingView + configures the 3 alerts