Sprint Status Brief

Atlas Scrum Master · Monday pre-planning · 2026-06-22 ET · Sprint Plan · PM Cockpit
Time until Sprint Planning
83 min
Planning starts 8:30 AM ET
Brief generated 2026-06-22 7:07 AM ET
Sprint 1 · 2026-06-22 → 2026-06-26 ET
27
shipped last week
3
slipped into sprint 1
8
sprint 1 committed
33
P0 open (all)
231/385
total done
6
properties stale >48h

1Previous week review completed Mon–Fri 6/15–6/19 ET · 27 tickets

Sprint 1 is the first formally-scoped sprint (starts today). The week below is the pre-Sprint-1 work that closed Mon–Fri last week, grouped by project codename.
Atlas17 shipped
MultiTrader4 shipped
StratLib4 shipped
Classifier2 shipped

2Slippage — carried into Sprint 1 created before last Monday, still pending

3 of Sprint 1’s 8 committed tickets are carryover — they predate last Monday and never closed:
Wider backlog context: 115 pending tickets were created before last Monday and remain open — 20 P0, 46 P1, 13 P2. This is the aged debt the sprint cadence exists to drain.

3This sprint’s goal Sprint 1 · 2026-06-22 → 2026-06-26 ET

Foundation hardening + AMS unblock
Close Phase 0 gaps. Seed AMS users so onboarding stops being painful. Fix Acct-v2 date-range bugs.

4This sprint’s backlog 0/8 shipped · live from todos.json

StProjectTicketOwnerPri
○Atlas1/6 Data-freshness dashboard: /system/freshness.json + banner on hubclaudeP0
○Acct-v2BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)jimboP0
○Acct-v2BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)jimboP0
○AMSAMS: seed main.users with trader rows so identity_fn returns non-zerouserP0
○AMSAMS: create main.remembered_devices table (migration 002) — Phase 1 hard dependencyclaudeP0
○AMSAMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop)userP0
○AMSAMS: write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md (Phase 3a baseline shipped, what's left)claudeP1
○BackupBackup: mirror scheduled-task SKILL files from domino-1 to jimdo via scpclaudeP1

5Dependencies no depends_on field — inferred from notes + critical path

TicketStateWhat blocks / readies it
Atlas1/6 Data-freshness dashboard: /system/freshness.json + banneREADYProperty-side MVP has no hard blocker (schema + update_freshness.py already scaffolded). DB-source half waits on scientific_layer migrations.
Acct-v2BUG: Risk Bump Progress bar does not respect the selected daBLOCKEDOwner Jim. Needs Jim’s availability this sprint — open 46d.
Acct-v2BUG: Ticket Meter denominator doesn't scale with date range BLOCKEDOwner Jim. Same date-range root cause as risk-bump bug — open 40d.
AMSAMS: seed main.users with trader rows so identity_fn returnsBLOCKEDOwner you. Blocks identity_fn returning non-zero rows → gates the entire AMS Phase-1 chain.
AMSAMS: create main.remembered_devices table (migration 002) — READYIdempotent CREATE TABLE, claude-actionable now. Logically gated by D3 (DB strategy) decision but can ship to _dev.
AMSAMS: resolve 7 open decisions D1-D7 (canonical domain · authBLOCKEDOwner you. D3 (DB strategy) shapes migration-002 + Phase-1 approach. Pure decision, ~30 min.
AMSAMS: write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md (PhREADYDepends only on reading git log. claude-actionable now.
BackupBackup: mirror scheduled-task SKILL files from domino-1 to jREADYssh jimdo / scp verified working (changelog). claude-actionable now.

6Critical-path stack top 7 from sprint-plan.html, sorted by readiness

1
Atlas ships p0-freshness-dashboard MVP (property side)
Completes Phase-0 freeze. DB-source half follows once migrations land.
READY
claude · 2h
2
Backup warm-runner online (heartbeat + delay/skip + liveness)
Critical BEFORE Exec goes live. If domino-1 dies, jimdo keeps alerts firing.
READY
claude · 3 days
3
You run scientific_layer migrations 001–009 via psql tunnel
Retires 4 user P0s; unblocks daily-summary view, rule-based classifier, identity_fn DB writes.
BLOCKED
user · 15 min
4
Jim ships the 2 Acct-v2 date-range bugs
Without these, no metric on a multi-day view can be trusted — blocks any team rollout.
BLOCKED
jimbo · 2 P0s
5
Classifier refresh cron ships (Roberto)
classify/*.json must update every minute during RTH for the Trigger Engine to fire.
BLOCKED
roberto · 4h
6
Exec Trigger Engine + Alert Channels in DEV
First half of the execution arm. Alerts to humans only at this stage.
DOWNSTREAM
claude · 1 wk
7
Exec Gr8Trade adapter enabled in prod with caps
The milestone where the system starts paying for itself. Real money — caps mandatory.
DOWNSTREAM
claude+jim · 2 wks

7Velocity trend tickets completed per week (Mon–Fri), last 4 weeks

▂▄▆█
2
5/25–5/29
13
6/1–6/5
21
6/8–6/12
27
6/15–6/19
Trend: +6 WoW (21→27). Velocity is accelerating — but see Q4: every one of these closures is claude-owned.

8Stale alarms P0 owner=human >14d · properties stale >48h

6 human-owned P0s aged >14 days
6 properties stale >48h (per app-status.json, probed 2026-06-22T07:01 ET · overall RED)

9Pre-meeting questions answer these in planning

Q1.AMS carries 4 P0s and 2 are owned by you (seed main.users + resolve D1–D7). Both gate the entire AMS Phase-1 chain. Can you commit ~30 min this sprint, or do we descope AMS Phase-1 sign-off to Sprint 2?
Q2.Acct-v2 has 2 date-range P0 bugs owned by Jim, open 40–46 days. Is Jim available this sprint — or do we reassign them to claude so the team-rollout blocker clears?
Q3.The scientific_layer migrations (P0, owner=you, 61 days stale) are critical-path step 1 and unblock 4 downstream P0s — yet they are not in Sprint 1’s committed 8. Do we pull them in?
Q4.Velocity is climbing hard (2→13→21→27) but it is 100% claude-owned tickets — every human-owned P0 is stalling. What is the single task each human owner commits to this week?
Q5.6 properties are stale >48h (VWAP-bands registry/bar ~136h, Strategy Library 108h, MGP v2 86h). Are these dead pipelines we retire, or do they need a watchdog ticket this sprint?