Sprint Status Brief
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
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
- ✓P1VCET Phase 0E param surface expanded — EMA4/9/20 trail variants + PARTIAL80 (80/20) exit sweeps2026-06-15 · claude
- ✓P2Multi-TF Index Stack v4 + supporting report scripts ran/refreshed for 6/152026-06-15 · claude
- ✓P2VWAP-bands param-surface monthly report regenerated (daily)2026-06-15 · claude
- ✓P1VCET CBO-context canonical validation + Phase 0A quality rerun + 2m CBO context page audit2026-06-16 · claude
- ✓P2VWAP-bands param-surface monthly report regenerated (daily)2026-06-16 · claude
- ✓P2Multi-TF Index Stack v4 + supporting report scripts ran/refreshed for 6/162026-06-16 · claude
- ✓P1VCET v0.1.2 expansion-gate TIMING study published2026-06-17 · claude
- ✓P2Scorecard real-time audit (Grade vs plan-ingest vs cockpit basis)2026-06-17 · claude
- ✓P2New /system/ focus3-plan + readiness pages published2026-06-17 · claude
- ✓P2VWAP-bands param-surface monthly report regenerated (daily)2026-06-17 · claude
- ✓P2Multi-TF Index Stack v4 + supporting report scripts ran/refreshed for 6/172026-06-17 · claude
- ✓First-entry timing analysis (account 14859, Apr-Jun)2026-06-18 · claude
- ✓Session-verdict engine (session_verdict.py + simulate harness)2026-06-19 · claude
- ✓Multi-TF stack daemon + /system/multi-tf-stack page2026-06-19 · claude
- ✓/system/readiness page built from 6/17 scaffold2026-06-19 · claude
- ✓/system/methodology page2026-06-19 · claude
- ✓VWAP research hub index (/gt_dev/db_reports/vwap-research)2026-06-19 · claude
MultiTrader4 shipped
- ✓P2Daily scorecard + you-vs-you regen for 6/152026-06-15 · claude
- ✓P2Daily scorecard + you-vs-you regen for 6/162026-06-16 · claude
- ✓P2Daily scorecard + you-vs-you regen for 6/172026-06-17 · claude
- ✓/scorecards/you-vs-you view2026-06-19 · claude
StratLib4 shipped
- ✓P1Strategy Views Consolidation: 3 views generated from canonical strategies.json master2026-06-16 · claude
- ✓P2Pocket-Pivot (PVP) scanner report rebuilt for 6/162026-06-16 · claude
- ✓P1Strategy views: canonical master promoted to LIVE /strategies/index.html2026-06-17 · claude
- ✓Top-5 VWAP-bands generator (gen_top5_bands.py)2026-06-18 · claude
Classifier2 shipped
- ✓/system/focus3-status page2026-06-19 · claude
- ✓VWAP state engine + chip-hazard classifier v42026-06-19 · claude
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:
- ○AtlasP01/6 Data-freshness dashboard: /system/freshness.json + banner on hubowner claude · 66d old · created 2026-04-17
- ○Acct-v2P0BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month)owner jimbo · 46d old · created 2026-05-07
- ○Acct-v2P0BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range)owner jimbo · 40d old · created 2026-05-13
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
| St | Project | Ticket | Owner | Pri |
|---|
| ○ | Atlas | 1/6 Data-freshness dashboard: /system/freshness.json + banner on hub | claude | P0 |
| ○ | Acct-v2 | BUG: Risk Bump Progress bar does not respect the selected date range (always shows 5-day rolling, even when range = full month) | jimbo | P0 |
| ○ | Acct-v2 | BUG: Ticket Meter denominator doesn't scale with date range (shows 1901 / 30 on 13-day MTD range) | jimbo | P0 |
| ○ | AMS | AMS: seed main.users with trader rows so identity_fn returns non-zero | user | P0 |
| ○ | AMS | AMS: create main.remembered_devices table (migration 002) — Phase 1 hard dependency | claude | P0 |
| ○ | AMS | AMS: resolve 7 open decisions D1-D7 (canonical domain · auth stack · DB strategy · sharing · risk_hud · 2FA · daily-stop) | user | P0 |
| ○ | AMS | AMS: write PHASE-3-STATUS.md mirroring PHASE-0-STATUS.md (Phase 3a baseline shipped, what's left) | claude | P1 |
| ○ | Backup | Backup: mirror scheduled-task SKILL files from domino-1 to jimdo via scp | claude | P1 |
5Dependencies no depends_on field — inferred from notes + critical path
| Ticket | State | What blocks / readies it |
|---|
| Atlas1/6 Data-freshness dashboard: /system/freshness.json + banne | READY | Property-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 da | BLOCKED | Owner Jim. Needs Jim’s availability this sprint — open 46d. |
| Acct-v2BUG: Ticket Meter denominator doesn't scale with date range | BLOCKED | Owner Jim. Same date-range root cause as risk-bump bug — open 40d. |
| AMSAMS: seed main.users with trader rows so identity_fn returns | BLOCKED | Owner you. Blocks identity_fn returning non-zero rows → gates the entire AMS Phase-1 chain. |
| AMSAMS: create main.remembered_devices table (migration 002) — | READY | Idempotent 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 · auth | BLOCKED | Owner 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 (Ph | READY | Depends only on reading git log. claude-actionable now. |
| BackupBackup: mirror scheduled-task SKILL files from domino-1 to j | READY | ssh 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
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
- ○AtlasP06/6 indicator_alerts DDL audit: dump schema, commit as ground truthowner user · 66d
- ○MultiTraderP0USER: 3 steps to finish journal persistenceowner user · 65d
- ○MultiTraderP0USER: run scientific_layer migrations 001–009 via psql tunnelowner user · 61d
- ○AtlasP0Compliance follow-up: delete (or hide) historical MGP pages 4/17 through 5/12 — owner james · 40d
- ○AtlasP0BUG: MGP auto-fire skipped 5/14 mid-day + recap; 5/15 morning ran ~2h45m lateowner James · 38d
- ○AtlasP0Nightly PM daemon went dark 5/20-5/22 (3 consecutive missed fires) — fix wake/laowner james · 30d
6 properties stale >48h (per app-status.json, probed 2026-06-22T07:01 ET · overall RED)
- ○VWAP-bands Strategy Bar 136h stale (threshold 30.0h) · 135.7h stale (threshold 30.0h, should refresh daily (no job found))
- ○VWAP-bands Strategy Registry 136h stale (threshold 30.0h) · 135.6h stale (threshold 30.0h, should refresh daily (no job found))
- ○Strategy Library 108h stale (threshold 30.0h) · 108.4h stale (threshold 30.0h, should refresh daily (no job found))
- ○MGP v2 86h stale (threshold 24.0h) · 86.3h stale (threshold 24.0h, daily editions)
- ○GAP MA scanner 85h stale (threshold 1.5h) · 85.5h stale (threshold 1.5h, live (extended hours 04:00-20:00 ET))
- ○PBS scanner 58h stale (threshold 1.5h) · 58.5h stale (threshold 1.5h, live (extended hours 04:00-20:00 ET))
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?