End-of-Day Brief · ATLAS
Wednesday, July 15, 2026 · generated 6:00 PM ET by Atlas · retrospective from
todos.json
✓ Trading day closed · prep for tomorrow's standup (Thursday Jul 16)
⚠ Today's headline not on the board — found by cross-checking the schedulers
The morning brief published nothing again — two days running. There is still
no /system/briefings/2026-07-15-morning.html on the server. Yesterday's silent miss was an anomaly;
a second one in a row is a pattern. Two standups (Tue Jul 14, Wed Jul 15) have now gone in with no Atlas brief,
and nothing anywhere flagged either miss. The failure is invisible precisely because the thing that would surface it
— the freshness banner — is itself the ticket that never got built.
Yesterday's two recommended tickets were never filed. Last night's EOD said to file two
P0s “first thing tomorrow” — the silent morning-brief failure and the dark freshness monitors.
Zero tickets were created on the board today (created_at = 2026-07-15 → 0). Neither blocker
has a ticket. They are carried forward again below.
Both freshness monitors are still dark. The old app-status.json is frozen at
Jul 8 12:01 PM ET — now 7 days with zero watchdog emails — and the new
atlas-flow-status.json was last written Jul 14 8:40 PM ET (~21h stale). The new monitor only gets
written by the nightly PM pass, so it goes green for a few hours each night and dark all day. Nothing is watching the
pipeline during trading hours, which is exactly why two morning-brief failures in a row went unseen.
What did work. The atlas-eod-brief job you are reading fired on schedule, and the
nightly PM reconciliation ran last night at 2026-07-14 11:32 PM ET — it back-filled 2 completions dated Jul 14 after
yesterday's 6 PM snapshot had already recorded 0. That timing (EOD snapshot at 6 PM, ledger reconciled ~11:30 PM) is why
“shipped today” reads 0 on every EOD: it is a snapshot floor, not the final count.
Shipped today completed_at = 2026-07-15 ET, grouped by project
As of this 6 PM snapshot, nothing carries
completed_at = 2026-07-15, and todos.json has not been written today — last modified
2026-07-14 11:32 PM ET by last night's nightly PM. Read this as a floor, not a verdict: yesterday the same tile showed 0
at 6 PM, then the nightly pass added 2 completions for Jul 14 five hours later. If tonight follows the pattern, today's
real closed count lands around 11:30 PM ET — after this brief. The standing gap remains that engineering
work (MGP editions, scanner runs) closes without a matching ticket, so even the reconciled number understates the day.
In flight status = in_progress · note-edits today: none — todos.json untouched since 2026-07-14 11:32 PM ET
- Atlas P0Drop Vital Knowledge entirely: build independent ticker selection + intraday refresh so subscription can be cancelled owner: claude · 63d old
Decision 2026-05-13 (James): after the compliance strip, drop Vital entirely and redirect the subscription cost elsewhere. PHASED PLAN: (2a) build morning_tickers.py with pre-market gappers from KTI minute bars…
- SIP P0MGP brief reads stocks_in_play_daily from DB (no kti recompute) owner: claude · 23d old
Today's bug: gen_mgp.py:_build_and_render_sip() does live kti calls every rebuild. When kti rate-limits, the brief shows 'bar fetch failed' while the SIP page shows real picks (different sources of truth). Fix:…
- MTFVP P1Change-of-Character panel — timestamp + duration + severity-trend per row owner: claude · 23d old
James spotted that the /system/multi-tf-stack/ CoC summary lists symbols (IWM daily 2-2 -> 15m=1-3, SMH daily 2-2 -> 5m=3-1) without telling you WHEN the signature first appeared or how long it has been active.…
- Atlas P1Pass CREATE_NO_WINDOW on every kti/ssh subprocess.run across reports/ owner: claude · 23d old
James 2026-06-22: scheduled scripts must run headless — no console flash. continuation_breakout.py patched. Sweep needed across all other modules that call subprocess.run([kti, ...] or [ssh, ...]): chiphazzard.…
- Exec P1Backtest J3P plays (Focus-3/KITE) on SIP names — edge by playbook x grade x tier before hotkeys owner: claude · 19d old
v1 6/27 (11 SIP names, n=157). 6/28 EXPANDED to WIDE 52-name canonical (n=804) + James daily universe (37 names, n=411) + v2.3 (Dale-faithful + CBO expansion) variants -> 11 registered runs (/system/J3P_RUNS.ht…
- Atlas P2AMS Playbooks + System property dirs scaffolded (next ports beginning) owner: claude · 53d old
New playbooks/ + system/ directories appeared 23:12-23:13 ET 5/23 in both dev /trading/dev/ams/ and stage /trading/ams/ — likely the start of the next two AMS property ports (Playbooks + System hub) following C…
- MultiTrader P2Scorecards multi-trader migration — extract shared core generator owner: claude · 36d old
NEW dev dir. Refactor of the scorecard generator toward multi-trader: gen_scorecard_core.py (extracted shared core) + gen_scorecard_mt.py (multi-trader driver) + _verify.py + MIGRATION-NOTES.md + _genrun.log. I…
No “edited today” flag is possible from the data — tasks carry no updated_at field, and
todos.json's own mtime (2026-07-14 11:32 PM ET) confirms not one task was touched today. These 7 are the
standing in-progress set, carried unchanged.
New blockers raised today created_at = 2026-07-15 · P0/P1
Zero tickets were created on the board today. The two real
blockers from last night are still unticketed and now a day older — file these before tomorrow's standup:
- P0atlas-morning-brief publishes nothing — now 2 consecutive days
with no output; the cron leaves no error and no surface reports the miss. suggested owner: claude
- P0Freshness monitors dark during the day —
app-status.json
frozen 7 days; atlas-flow-status.json only written by the nightly pass, dark through all of trading hours.
suggested owner: claude
All 36 open P0s are carryover; the oldest is now
89d old.
What's open for tomorrow top open P0/P1 weighted by priority × age · ranked for Thursday Jul 16 standup
1
Atlas P01/6 Data-freshness dashboard: /system/freshness.json + banner on hub
owner: claude · P0 · age 89d · weight 267 (priority×age). Age 89d, top of the board since day one. For the second straight day the morning brief published nothing — this is the ticket whose freshness banner would have made that failure visible on the hub instead of invisible. It stopped being housekeeping a week ago. Start here.
2
Atlas P02/6 Pipeline orchestrator: run_nightly.py calls every generator, logs to one place, fails loud
owner: claude · P0 · age 89d · weight 267 (priority×age). Age 89d. The reason nothing self-reports when it breaks: every generator fires from its own scheduler with its own log, and no single place knows whether the whole set succeeded. Two consecutive silent morning-brief failures are the proof. One orchestrator, one log, fail loud.
3
MultiTrader P03/6 main.daily_summary SQL view: kills duplicate computation
owner: claude · P0 · age 89d · weight 267 (priority×age). Age 89d. Blocks the identity function and the daily_summary view, which in turn gate AMS Phase 1 and the MultiTrader rollout. Nothing downstream of it can close while it sits.
Critical-path next step first unblockable item · unchanged from yesterday
1/6 Data-freshness dashboard: /system/freshness.json + banner on hub
· ATLAS · owner: claude · 89d old
Nothing sits upstream of it — no dependency, no decision, no other
person — so it can be started cold tomorrow morning. The next-unblockable item did not change today, but its
case got stronger: a second silent morning-brief failure is the exact class of miss this freshness dashboard is
built to expose. Do this one, then 2/6 — the orchestrator that makes the whole pipeline fail loud.
Sprint progress active_sprint_id = 1
Sprint 1 (active pointer): 0 tickets done / 8 total
· 0% · window 2026-06-22→2026-06-26 ET (ended 19 days ago)
Goal: Close Phase 0 gaps. Seed AMS users so onboarding stops being painful. Fix Acct-v2 date-range bugs.
⚠ Sprint rollover still not done — carried on every EOD this week.
active_sprint_id is still 1, whose window closed 19 days ago at 0/8. By the calendar,
today is day 3 of Sprint 4 (2026-07-13→2026-07-24, “Exec Gr8Trade adapter + forward-test”).
Sprints 2 and 3 were never opened or closed. Advance the pointer to 4, close or carry S1–S3, run the Sprint 4
planning pull.
Ticket tagging is still thin. Only 21 of 440 tickets carry a sprint
tag (S1 = 8, all pending; S3 = 7; S4 = 5; S5 = 1). Burn-down cannot be trusted until the backlog is tagged to the sprint
that is actually running.
Stale user-owned blockers 29 open P0/P1 waiting on a human · age ≥ 7d · top 8 shown
| Project | Title | Owner | Age |
| Atlas | P06/6 indicator_alerts DDL audit: dump schema, commit as ground truth | user | 89d |
| MultiTrader | P0USER: 3 steps to finish journal persistence | user | 88d |
| MultiTrader | P1Re-run gen_scorecard.py ON a2 (or via tunnel) and confirm enrichment populates | user | 88d |
| Atlas | P1Deploy z_activity_scanner.py on each Windows machine via Task Scheduler | user | 85d |
| MultiTrader | P0USER: run scientific_layer migrations 001–009 via psql tunnel | user | 84d |
| Atlas | P1Cron /system/update_freshness.py to keep freshness strip auto-refreshing | user | 70d |
| MultiTrader | P1Trader-of-the-Week scorecard review session (rotating: Nolan / Preston / Brian / Thomas) | user | 70d |
| MultiTrader | P1First-scorecard feedback session with each of the 4 traders | user | 70d |
None of these are blocked on Claude. Each needs a person to
act — and all 29 have been waiting a week or more.