# SPRINT.md — Day-by-day plan to pilot launch **Pilot launch:** Monday, May 26, 2026 **Cadence:** Daily (build-fix-deploy-test rhythm; ship overnight, test all day) **Started:** Day 20 (Friday, May 8, 2026) This is the canonical day-by-day plan. Replaces XJobs-Day-N-MASTER docx pattern. ## How to read this file This file is append-only at the day-card level. Each working day, the agent appends today's card at the bottom (newest at the bottom — chronological reading top-to-bottom). Day cards are NOT edited after close. If a planned item slips, the next day's card explains it. This protects the audit trail. Cadence rule: daily. One production deploy per day max, end of working day or overnight. Testers test all day against today's deployed build. No mid-day surprise deploys without founder approval. Slack rule: 30% of each working day is reserved for the unexpected. Discovered bugs get triaged to the appropriate day, not stuffed into today's leftover time. --- ## Day 20 — Friday, May 8, 2026 **Build at session start:** 30ac9a5 **Production HEAD at session start:** 30ac9a5 ### Plan for the day Three time blocks: **Morning (capacity: 4 hours)** - File-system housekeeping: rm ~/Downloads/app_*.html (the F180 foot-cannon) - Move tonight's documentation deliverables into repo locations - XJobsFinder-Tester-Test-Plan-v2.docx → Documentation/Tests/ - XJobsFinder-Regression-Matrix.xlsx → Documentation/Tests/ - XJobsFinder-Test-Execution-Guide-v2.docx → Documentation/Tests/ - XJobsFinder-Untested-Bugs-Discovery-Protocol.docx → Documentation/Tests/ - XJobs-Tester-Preview.html + .pdf → Documentation/Dashboard/ - XJobs-Day-19-MASTER-2026-05-07.docx → Documentation/Weekly/ (last of its kind) - AGENT-ONBOARDING-Day19.docx → Documentation/Weekly/ - Create Documentation/Tests/ directory if not present - Single commit + push for all artifact moves - Begin Part C of F186 housekeeping: user-scope the 6 untagged resume writes (lines 4557, 6486, 10597, 14544, 14553, 14562, 14571, 14580, 14853) plus 4 gmail writes **Afternoon (capacity: 3 hours)** - F184 — enforce signup gate (resume upload required before dashboard). Pre-pilot blocker. - F185 — dashboard handles missing resume gracefully (likely closed by F184 fix as side effect) - Smoke-test all of Day 19's fixes once more on production after Part C deploy **Slack (capacity: 2 hours, reserved)** - Tester re-engagement message draft for Oli + Oscar — target Friday afternoon send - Triage anything unexpected from morning work - If slack runs unused: begin Discovery Protocol Investigation 1 (F73 + F91 dual-mount mapping) ### Deploy decision rule for today Deploy ONCE at end of working day, only if: - F186 Part C verified locally - F184 fix verified locally - Production smoke test passes against new build before push Otherwise hold. Tonight's local-only state is acceptable; rolling back yesterday's clean deploy for partial work is not. ### Open threads carried in Five from end of Day 19: 1. Day 19 housekeeping (rm ~/Downloads/app_*.html) 2. Tester re-engagement (Oli + Oscar) 3. F186 Part C 4. F184 enforce signup gate 5. Phase 1.5 carry-forwards (F1, F5, F7, F9, F10, F11, F13) --- ## Day 21 — Saturday, May 9, 2026 **Plan (provisional, refined at end of Day 20):** - Morning: Send tester re-engagement to Oli + Oscar (if not done Friday). Begin Discovery Protocol Investigations 1-3 (HIGH priority backend investigations). - Afternoon: Address any feedback from morning's tester signals. Begin Phase 1.5 zombie deletions (F5, F9, F11, F13). - Slack: 2 hours reserved. - Deploy: end of day if material change. --- ## Day 22 — Sunday, May 10, 2026 (rest / light day) **Plan:** - No deploys. Light day reserved for thinking, not coding. - Catch up on tester reports submitted Friday/Saturday. - Update SPRINT.md plans for week 2 based on tester signal. - If pilot prep is on track: actually rest. --- ## Day 23 — Monday, May 11, 2026 **Plan (provisional):** - Morning: Discovery Protocol Investigations 4-7 (MEDIUM priority backend). - Afternoon: Tester rotation 2 — invite a 3rd or 4th tester to widen the geography pool if Oli + Oscar reports are clean. - Slack: 2 hours reserved. --- ## Day 24 — Tuesday, May 12, 2026 **Plan (provisional):** - Morning: F7 paradigm consolidation decision (pick canonical resume builder, mark others zombies). - Afternoon: B2 reg-wall text polish, F18 interview stubs decision. - Slack: 2 hours reserved. --- ## Day 25 — Wednesday, May 13, 2026 **Plan (provisional):** - Morning: F1 quota meter consolidation. F2/F6/F10 zombie panel removal. - Afternoon: Stripe test mode API key rotation (long-pending). - Slack: 2 hours reserved. --- ## Day 26 — Thursday, May 14, 2026 **Plan (provisional):** - Morning: Discovery Protocol Investigations 8-14 (LOW priority backend) — only if tester signal stays clean. Otherwise triage. - Afternoon: First end-to-end full-build retest. All 4 scenarios from Test Execution Guide v2 against current production. - Slack: 3 hours reserved (pre-weekend buffer). --- ## Days 27-29 — May 15-17 (weekend + Monday) **Loose plan:** - Day 27 (Friday May 15): Polish day. Whatever surfaced from Day 26 retest. - Day 28-29 (weekend): Light. Tester rotation 3 if appropriate. - Generate XJobs-Week-2-Summary.docx Saturday. --- ## Days 30-34 — May 18-22 **Loose plan:** - Pre-launch hardening. DMARC, npm audit, security review. - Soft-launch prep — pilot invitation list, comms. - Final bug bash with all testers parallel. - No new features. Polish only. --- ## Days 35-37 — May 23-25 (final weekend) **Loose plan:** - Day 35 Friday: feature-freeze declared. No code changes except critical security. - Day 36 Saturday: final smoke test marathon. Production end-to-end verification. - Day 37 Sunday: rest. Pre-launch mental prep. Pilot invitations sent. --- ## Day 38 — Monday, May 26, 2026 — PILOT LAUNCH **The day:** - Morning: monitor production. Live tester support. - All-day: respond to issues as they surface, with full audit/HANDOFF discipline. - Evening: Day 38 close + Week 3 summary docx. - This file (SPRINT.md) closes with a final post-launch entry. --- ## Post-launch (May 27+) SPRINT.md closes. New cadence document opens (or this file is renamed to PRE-LAUNCH-SPRINT.md and a new POST-LAUNCH-SPRINT.md begins). Phase 4 (frontend modularization) explicitly deferred per Day 13 strategic decision. ## Post-pilot consideration: document-monitoring agent Discussed Day 19 PM very-late close. Founder raised the idea of an agent that monitors Documentation/ for new files, runs diffs to identify the latest version of related documents, and updates URL aliases automatically. Decision: deferred to post-pilot. Pre-pilot, the recent-docs endpoint already provides 'show me the latest' discoverability via the dashboard. Document accumulation may become a real friction post-pilot when feature work resumes; revisit then. Trigger to revisit: if more than two distinct 'find me the latest X' moments occur in a single sprint.