claude follow-on build work, not something waiting on the team.| Age | Project | Owner | Pri | Title |
|---|---|---|---|---|
| 0d | PinePB | claude | P1 | J3P — live smoke test: TV alert -> webhook -> indicator_alerts row (1 SIP name) |
| 0d | SIP | claude | P1 | Deploy J3P across SIP master_watchlist (TV layout + webhook alert per symbol) |
| 0d | Exec | claude | P1 | Backtest J3P plays (Focus-3/KITE) on SIP names — edge by playbook x grade x tier before hotkeys |
| 0d | Exec | claude | P1 | Wire setups.today.json -> hotkey-engine for J3P-graded entries (SIM -> forward-test) |
daily_summary view, the rule-based classifier path, and identity_fn DB writes. Unchanged all of Sprint 1 - still the single highest-leverage step, and it carries straight into Sprint 2 (“Classifier production + AMS Phase 1 sign-off”). Nothing downstream moves until it lands.main.users is what makes identity_fn return a non-zero user; D1-D7 unblocks the rest of the AMS Phase-1 build that Sprint 2 signs off on.p0-daily-summary-view, the rule-based classifier path, and identity_fn DB writes.
No movement today — the next-unblockable item is unchanged from this morning and from the start of
Sprint 1, and everything downstream still waits on it.