Rumblings — Build Plan: Phase 1

See also: Architecture Blueprint | Roadmap

Period: March–May 2026
Hours: Tom 208h (80h March + 64h April + 64h May) + Tim 64h (32h April + 32h May)
Milestones: M1 (Done Feb 28) → M2 Demo Ready (May 31)
Weeks: W10–W22
Source of truth: build-plan-phase-1.md — HTML is generated from this.
Last updated: 2026-04-14

Phase 1 Overview

Phase 1 is the build phase. The intelligence layer IS the product — trend detection is table stakes. Every trend getting a ‘So What’ (sector context), a lite ‘Now What’ (basic vertical-level activation suggestions), and generated narrative is what makes Rumblings worth paying for. If the LLM outputs are generic or wrong, nothing else matters. March and April are dominated by making this layer genuinely good.

The revised sequencing: No pilots until June (free). No paid revenue until Q3/Q4. March is case studies + intelligence layer + data quality. Multi-tenancy pulled forward to W16 (Tim Goerner / Augmentra, 2 days/week) — freeing Tom’s May for /report skill + intelligence quality. Build the product that impresses while Tim builds the infrastructure in parallel.

Hour Budget

Monthly Hour Breakdown

March (80h)

April — Tom (64h) + Tim (32h from W16)

May — Tom (64h) + Tim (32h)

Work Streams (Updated 2026-04-10 — with Tim Goerner / Augmentra)

March (80h) — Case Studies + Intelligence Layer

March is the make-or-break month. Tom is pushing to 20h/week because this work directly determines whether the June pilot demo lands. Four parallel streams, all critical.

W10 (Mar 2–8): “Foundation Sprint” — 20h

Capacity: Tom 20h | AJ 4h | Jen 4h | Lori 8h

Day 1 — VPS: Pipeline Unblock

Day 2 — VPS: Data Quality + Audit

Day 3 — Case Studies + Intelligence

Parallel Tracks (Non-Tom)

AJ (0.5 days):

• Review case study shortlist — which resonate for potential clients?
• Confirm AG1 as second case study client or suggest alternative
• Write 1–2 cultural brief examples from Lounge Lovers lens

Jen (0.5 days):

• Write AG1 client profile (vertical, credibility zones, seed terms)
• Write 1–2 cultural brief examples (health/wellness vertical)
• Review existing 8 cultural brief examples for quality

Lori (1 day):

• Select her case study client (third vertical) — deadline this week
• Begin legal research: ToS template for SaaS trend intelligence
• Write 1 cultural brief example from her client’s vertical

W10 Success Criteria

• ✓ Write failures fixed — trends persisting (zero failures on reprocess) ✓ Day 1
• ✓ Full pipeline reprocessed with V2 scoring ✓ Day 1 (368 vectors, 670 trends)
• ✓ Google Trends enrichment working (urllib3 + n8n disabled fix) ✓ Day 1
• ✓ Intelligence layer architecture audit complete ✓ Day 1 (docs/INTELLIGENCE-LAYER-ARCHITECTURE.md)
• ✓ 3–5 case study candidates selected with rationale ✓ Day 1 (5 selected: Clean Girl, Balletcore, Dubai Choc, Brat, Hot Honey)
• ✓ VPS git state clean ✓ Day 1
• ✓ AG1 client profile drafted (Jen) ✓
• ✓ Lori’s case study client selected ✓ Bumble confirmed

W11 (Mar 10–14): “Collector Expansion + Dedup + Case Studies” — 20h

New scope (added 2026-03-03): Intelligence layer tasks pulled forward to W10, freeing W11 for collector expansion work. See collector-expansion-plan for full details and risk assessment.

Day 1 — Collector Expansion: HN + Trade Press + Pinterest

Day 2 — Data Quality: Dedup + GDELT Fix

Day 3 — Case Study Writing + Tumblr

W11 Success Criteria

• ✓ ‘So What’ generation producing sector-specific context for every scored trend ✓ Done in W10
• ✓ Lite ‘Now What’ generating basic vertical-level suggestions ✓ Done in W10
• ✓ Report narrative generation composing trend stories ✓ Done in W10
• ✓ HN Algolia seed term collector deployed ✓ Done in W10 (pulled forward from W11)
• ✓ Trade Press migrated to main seed terms sheet ✓ Done W10 (RSS consolidation)
• ✓ GDELT tone data flowing — lexicon expanded, EI denominator fixed ✓ Deployed commit 5b2931b
• ✓ Tumblr hybrid — trending tags + seed term search ✓ 8 discovery terms, 6,119 signals (verified Mar 16)
• ✓ Fuzzy dedup: design, build, integrate, verify — complete ✓ 20% term reduction, deployed
• ✓ First retrospective case study draft complete CUT — focusing on client case studies instead

W12 (Mar 17–21): “V3 Case Studies + Entity Resolution + Collector Compliance” — 20h

Updated 2026-03-13: Restructured around V3 case study reports as #1 priority. All 3 founders reviewed V1/V2 and provided feedback — consolidated into 10 themes, 7 must-haves (see 06-Research/trend-report-feedback/v3-analysis/). V3 is a presentation + curation exercise, not a pipeline rebuild. Deep prompt iteration stays in W14. DataForSEO dropped — will attempt GT rate-limiting fix instead.

Updated 2026-03-22 (replan): W12 was consumed by infrastructure work — Steve Review (codebase audit, shared DB factory, API auth, god-file split), SessionStart hook fix, Todoist migration, CLAUDE.md surgery + quality gate hooks. All valuable but off critical path. 5 planned items carried to W13.

Day 1 — V3 Template + Entity Resolution

Day 2 — Collector Compliance + Pinterest Cleanup

Day 3–4 — V3 Report Generation + Manual Curation

W12 Unplanned Work (actually completed)

W12 Success Criteria

• ✓ Wikipedia seed term collector deployed (pageview spike detection) ✓ Done in W10 (pulled forward)
• ✓ Dashboard client-readiness audit completed (Workstream C) ✓ Done in W11
• ✓ Live tracking case studies initiated ✓ Done in W11 (Workstream C)
• V3 report template built [CARRIED W12→W13]
• V3 reports generated and published [CARRIED W12→W13]
• ✓ Entity resolution integrated during W11 build (confirmed W13, commit ca61688)
• Collector ToS compliance review [CARRIED W12→W13]
• ✓ Pinterest VPS cleanup complete ✓ Mar 16 — 17,473 records cleaned, 0 raw fields, both WFs disabled
• ✓ Tumblr trending tags deployed ✓ Mar 16 — 8 discovery terms, 6,119 signals verified
• Google Trends rate-limiting fix [CARRIED W12→W13]
• ✓ Unplanned: Steve Review — codebase audit, shared DB factory, API auth, dep cleanup ✓ Mar 21
• ✓ Unplanned: SessionStart hook + Todoist migration + CLAUDE.md surgery + quality hooks ✓ Mar 21

W13 (Mar 24–28): “W12 Critical Path Catchup” — 16.5h

Updated 2026-03-22 (replan): Restructured to absorb W12 spillover. Original W13 items (dashboard polish, demo prep, case study presentations, cultural briefs) deferred to W14 — they depend on V3 reports existing anyway.

Updated 2026-03-26 (replan): Day 1 (Tue) cleared all planned tasks plus major unplanned pipeline surgery (n8n upgrade 2.2.4→2.13.3, Code→noOp migration, API key fix, ghost trend archival, dedup run, V5 reports shipped). Day 2 (Thu) repurposed for pipeline verification, data quality cleanup, and W13 close-out. YouTube collector also deployed (10th source).

Day 1 (Tue) — Quick Wins + V3 Template + Entity Resolution

Day 2 (Thu) — V3 Reports + Google Trends

Day 3 (Fri flex) — ToS Review

W13 Unplanned Work (actually completed)

W13 Success Criteria

• ✓ V3 report template built — reflects all 7 must-haves from founder feedback ✓ Mar 24 (evolved to V5)
• ✓ Entity resolution deployed in pipeline — confirmed working (commit ca61688) ✓ Mar 24
• ✓ V3→V5 reports generated and published for all 3 clients ✓ Mar 24
• ● Google Trends rate-limiting fix — investigation in progress, documenting findings Mar 26
• ✓ Collector ToS compliance review complete ✓ Done W12 (triggered Pinterest cleanup)
• ✓ Pipeline API auth activated on VPS ✓ Mar 24
• ✓ GitHub auth fixed — SSH key configured ✓ Mar 24
• ✓ Bonus: n8n upgraded + pipeline workflows fixed ✓ Mar 25
• ✓ Bonus: YouTube collector deployed (10th source) ✓ Mar 25
• ✓ Bonus: Daily LLM QA system live ✓ Mar 24
• ✓ Bonus: 73K ghost trends archived, pipeline DQ significantly improved ✓ Mar 24

March Deliverables

• ✓ Write failures resolved — pipeline processing 100% of trends ✓ W10
• ✓ Google Trends enrichment restored (rate limiting fix deployed W10, monitoring) — Note: relapsed Feb 25, investigation ongoing W13
• ✓ Intelligence layer: ‘So What’ + lite ‘Now What’ generating sector context ✓ W10
• ✓ NarrativeGenerator integrated with intelligence layer ✓ W10
• ✓ Fuzzy dedup live in pipeline ✓ W11 (20% term reduction)
• ✓ Entity resolution live in pipeline ✓ W11 build, W13 confirmation (commit ca61688)
• ✓ Collector expansion (8 items): HN Algolia ✓, Wikipedia pageviews ✓, GDELT tone ✓ W11, Tumblr trending ✓ Mar 16, Trade Press migration ✓, Pinterest interests ✓, YouTube ✓ W13 (7/8 done + GT in progress)
• ✓ Seed term coverage: 10 of 12 collectors using seed terms sheet (up from 6) — HN, Wikipedia, YouTube now seed-aware
• ✓ V5 case study reports — 3 client reports (AG1, Bumble, Lounge Lovers) shipped ✓ W13
• ✓ Live tracking case studies initiated ✓ W11 (Workstream C)
• ✓ Dashboard client-readiness audit completed ✓ W11 (Workstream C)
• ✓ Collector ToS compliance review with Grace ✓ W12 (triggered Pinterest cleanup)
• Demo flow + presentation materials (deferred to W14)
• ✓ Unplanned: Steve Review — shared DB factory, API auth, god-file split, dep cleanup ✓ W12
• ✓ Unplanned: Quality gate hooks, SessionStart fix, Todoist migration, CLAUDE.md surgery ✓ W12
• ✓ Unplanned: n8n upgrade 2.2.4→2.13.3 + Code→noOp pipeline fix ✓ W13
• ✓ Unplanned: YouTube collector (10th source) ✓ W13
• ✓ Unplanned: Pipeline DQ overhaul (ghost archival, contribution floor, entity gate, daily QA) ✓ W13
• ✓ Unplanned: V5 reports (5 iterations from V1→V5, shipped to all founders) ✓ W13

April (64h) — Intelligence Deep + Demo Ready

April is about quality. The intelligence layer exists from March — now it needs to be GOOD. Jen and AJ start reviewing outputs and providing feedback. The notification system gets built so pilots can receive intelligence via both Slack Connect and email from day one.

W14 (Mar 31–Apr 4): “V6 Report Quality — V5 Feedback Response” — 16h

Updated 2026-03-31 (replan): Rewritten after V5 founder feedback received (all 3 founders reviewed, synthesis in 06-Research/trend-report-feedback/v5/00-synthesis.md). V5 not client-ready — 8 must-fix blockers identified. V6 SOP system launched (Google Docs). Product vision interview added (Apollo Group reframes as business strategy tool). Dashboard polish, demo prep, case study materials, cultural briefs deferred to W15-W16 — intelligence quality is the bottleneck, not presentation.

V5 feedback synthesis: Scoring works, signal quality clean, data cleanup visible. Blockers: “Emerging” framing wrong, no plain-language descriptions, observation tone not authority, no prioritisation, bot spam in engagement, established-vs-emerging conflated, no fact-checking stage, factual errors.

Day 1 (Tue) — Vision + V6 SOP Iteration (Must-Fix Blockers 1-4)

Day 2 (Thu) — V6 SOP Iteration (Must-Fix 5-8) + Pipeline Work

W14 Deferred Items (moved to W15-W16)

W14 Success Criteria

• Product vision interview complete — Apollo Group positioning captured for Jen
• V6 SOPs updated with all 8 must-fix items from V5 feedback
• First V6 report generated using updated SOPs — ready for founder spot-check
• ✓ LL client context corrected, Bumble factual error fixed ✓ Mar 31
• Spam/bot filter filtering engagement signal noise
• Trend archaeologist stage designed (architecture, not full build)
• ✓ AG1 seed terms expanded (15 new terms across 3 categories) ✓ Mar 31
• ✓ PRD/TRD/feature gap matrices updated with V5 feedback + March builds ✓ Mar 31
• ✓ W13 campaign closed (dedup SQL applied, git commits pushed) ✓ Mar 31

W15 (Apr 7–11): “V6 SOPs + Notification Design + Tim Prep” — Tom 16h

Updated 2026-04-10 (replan): Rewritten to reflect actual W15 priorities. V6 SOP iteration is the real bottleneck (V5 feedback: 8 must-fix blockers). Tim Goerner (Augmentra, $270/day, 2 days/week) starting W16. This week: prep his sprint spec, DB snapshot, and GitHub access.

Tom Day 1 (Tue) — V6 SOPs + Lori Session Prep

Tom Day 2 (Thu) — V6 SOPs + Tim Sprint Spec

W15 Success Criteria

• V6 SOPs updated with all 8 must-fix items from V5 feedback
• V6 prompts wired to new SOP architecture (at least started)
• Tim sprint 1 spec written (API contract + multi-tenancy task list)
• Sanitised DB snapshot prepared for Tim
• GitHub contributor access provisioned
• Notification abstraction layer designed
• Lori thinking partner skill set up for Monday session

W16 (Apr 14–18): “Tim Starts + Intelligence Quality” — Tom 14h + Tim 14h

Tim Goerner (Augmentra) starts this week. Tim works on multi-tenancy foundation while Tom focuses on V6 prompt wiring and intelligence quality. Slack Connect (#2541–2543) deferred to Phase 2 — email delivery via /report skill is sufficient for 2-3 free pilots.

Tom Day 1 (Tue) — Tim Prep + Intelligence Quality

Tom Day 2 (Thu) — V6 Prompts + Quality Review

Tom Evening — PRD Refactor + Social Research Planning

Tim Day 1 — Setup + Data Model Design

Tim Day 2 — Client Tables DDL

W16 Success Criteria

• Tim local dev environment working against DB snapshot
• Multi-tenancy DDL PR submitted (4 tables, raw SQL, follows init_schema.sql patterns)
• React portal tooling proposal submitted for Tom’s review
• V6 prompts wired to new SOP architecture
• First quality review completed with Jen/AJ
• ✓ Quality gate hooks fixed (11/11 scenarios passing)
• ✓ Vertical Intelligence Layer designed, PRD #2920 added
• ✓ PRD MECE refactor complete — 62→23 Tom items, 35 total active
• ✓ Thinking partner: 5 branches closed (case studies, email, notifications, onboarding, social research)
• ✓ Social scraping research brief written, pending co-founder review (#2935)

W17 (Apr 21–25): “V6 Wiring + Scoped Queries + Research Plan” — Tom 14h + Tim 14h

Restructured 2026-04-14 (MECE refactor): Email delivery removed (premature for pilots — manual delivery sufficient). Tom focuses on V6 prompt wiring (#2932), intelligence edge cases (#2922), and social research plan review (#2935). Tim continues multi-tenancy foundation.

Tom Day 1 (Tue) — V6 Prompt Wiring + Edge Cases

Tom Day 2 (Thu) — V6 Continued + PR Reviews

Tom Evenings — Social Research Execution Start

Tim Day 1 — Client-Scoped Query Layer

Tim Day 2 — Scoped Queries + Validation UI Backend

W17 Success Criteria

• V6 prompts wired to SOP architecture — first V6 report generated
• Intelligence edge cases handled (data sufficiency + confidence thresholds)
• GT enrichment expanded to all collector sources
• Social research plan reviewed by co-founders (gate for execution)
• Every intelligence query is client-aware (negative test cases pass)
• Validation feedback backend: FastAPI routes for confirm/reject/reclassify

April Deliverables

• V6 SOPs iterated — all 8 must-fix blockers from V5 feedback addressed
• V6 prompts wired to new SOP architecture (#2932)
• Intelligence layer quality-reviewed by Jen + AJ (#2551)
• Intelligence edge cases handled (#2922)
• GT enrichment expanded to all sources (#2924)
• ✓ PRD MECE refactor — 62→23 Tom items, 35 total active
• ✓ Social research brief written, co-founder review pending (#2935)
• Tim WS1: Multi-tenancy tables deployed (#3001)
• Tim WS1: Client-scoped query layer, data isolation verified (#3002, #3003)
• Tim WS1: Validation feedback UI backend (#3004)

May (64h Tom + 32h Tim) — /report Skill + Tim WS1 Completion + Pilot Prep

May splits into two parallel tracks. Tom builds the /report skill (the core client deliverable), polishes intelligence quality, and continues social research in evenings. Tim completes WS1 (auth, validation UI, onboarding, dry run). WS2 scope decided at trial gate (end W19). Email delivery deferred — manual for pilots, Tim’s WS2 (#3013) if needed later.

W18 (Apr 28–May 2): “Calendar Events + /report Design + Validation UI” — Tom 14h + Tim 14h

Tom Day 1 (Tue) — Calendar Events + Client Folders

Tom Day 2 (Thu) — /report Design + PR Reviews

Tom Evenings — Social Research Continues

Tim Day 1 — Validation UI Frontend

Tim Day 2 — Minimal Auth + Onboarding

W18 Success Criteria

• Calendar events table deployed with initial data
• 3 pilot client profiles created (AG1, Bumble, Lounge Lovers)
• /report skill architecture designed
• Validation feedback UI functional — Jen/AJ can use it
• Minimal auth implemented (API key + unique URL)
• Client onboarding script creates a client in under 5 minutes

W19 (May 5–9): “/report Foundation + WS1 Gate” — Tom 13h + Tim 14h

Tom Day 1 (Tue) — /report Foundation

Tom Day 2 (Thu) — /report Cont. + WS1 Review

Tim Day 1 — E2E Dry Run Prep

Tim Day 2 — WS1 Gate + WS2 Planning

W19 Success Criteria

• /report skill foundation working (reads client folder + SOPs + API data)
• End-to-end dry run passes (onboard → auth → scoped trends → validation feedback)
• WS1 trial assessed — decision on extension/scope

WS1 TRIAL GATE: End of W19 (May 9)

Evaluate: Does Tim’s code pass review? Does the dry run work? Can Tom maintain this?
Decision: extend to WS2 (scope TBD), redirect, or terminate.

W20 (May 12–16): “/report Build + Tim WS2” — Tom 14h + Tim 14h

Tim’s WS2 scope decided at trial gate. If WS2 proceeds: client folder tooling (#3010), API data layer (#3011), report template engine (#3012). If not: Tom absorbs remaining work.

Tom Days — /report Generation Pipeline

Tim (WS2 — scope per trial gate)

W21 (May 19–23): “Report Quality + Demo Prep” — Tom 14h + Tim 14h

Tom Days — Quality Reviews + Demo

Tim (WS2 continued)

W22 (May 26–30): “Pilot Dry Run + M2” — Tom 10h + Tim 10h

Tom Days — Full Dry Run + M2

Tim — Testing + Documentation

W22 Success Criteria

• Full end-to-end dry run passed (onboard → intelligence → report → deliver → validate)
• Demo environment clean, stable, no surprises
• Reports are client-ready quality (Jen/AJ reviewed)
• Pilot ops documentation complete
• Legal docs drafted
• All M2 criteria met

May Deliverables

• /report skill: generates per-client intelligence reports from SOPs + API data (#2914)
• Calendar events DB deployed with ~250 events (#2910)
• 3 pilot client profiles created (#2911)
• Demo environment + script ready for AJ/Jen (#2930)
• Pilot prep homework template built (#2934)
• Quality reviews passed — reports are client-ready (#2551)
• Legal docs suite drafted (#2928)
• Tim WS1: Minimal auth (API key + unique URL) (#3006)
• Tim WS1: Validation feedback UI functional (#3004)
• Tim WS1: Client onboarding automation (#3005)
• Tim WS1: End-to-end dry run passed (#3007)
• Tim WS2: Report template + email delivery (scope per gate) (#3012-3014)
• End-to-end pilot dry run completed (#2931)

Social Research (Parallel Track — Evenings/Flex)

• Co-founder plan review complete (#2935)
• Scraping execution + analysis (~3 weeks from start) (#2936)
• Deliverables: analysis doc + investor slides (#2937)

Dependencies (Updated 2026-04-14)

Chain 1: Data → Intelligence → Reports ✓ MOSTLY COMPLETE

Write Failures Fix → Reprocess → NarrativeGenerator → So What / Now What → V5 Reports ✓
                                                                            |
V6 SOPs (W15-W16) → V6 Prompt Wiring (W16-W17) → /report Skill (W18-W21) → M2

Chain 2: Google Trends Recovery ⚠ IN PROGRESS

Google Trends Fix (#1913) → V2 Data Quality Restored → GT Enrichment All Sources (#2924)

Chain 3: Intelligence → Report → Demo (Tom’s critical path)

V6 SOPs (W15-W16) → Prompt Wiring (#2932, W16-W17) → Quality Review (#2551, W17)
                                                              |
Calendar Events (#2910) + Client Folders (#2911) → /report Skill (#2914, W18-W21) → Demo (#2930, W21-W22) → M2

Chain 4: Multi-Tenancy → Auth → Dry Run → M2 (Tim’s critical path)

Multi-Tenancy DDL (#3001, W16) → Scoped Queries (#3002-3003, W17) → Minimal Auth (#3006, W18) → Dry Run (#3007, W19) → WS1 Gate
                                                                                                          |
Validation UI (#3004, W17-W18) → Onboarding (#3005, W18) ------→

Chain 5: Social Research (Parallel — not on M2 path)

Research Plan (#2935, W16) → Co-founder Gate → Execution (#2936, W17-W19) → Deliverables (#2937, W19-W20)

Full Critical Path (Parallel Tracks)

Tom Track:
V6 SOPs → Prompt Wiring (W16-W17) → Quality Review (W17)
                                           |
Calendar Events + Client Folders (W18) → /report Skill (W18-W21) → Demo + Dry Run (W22) → M2

Tim Track (parallel):
Multi-Tenancy (W16) → Scoped Queries (W17) → Auth (W18) → Dry Run (W19) → WS1 Gate
                                                |
Validation UI (W17-W18) → Onboarding (W18) ---’
                                                     | (if gate passes)
WS2: Client Folder Tooling (W20) → Report Templates (W21) → Email Delivery (W21-W22)

Research Track (parallel, not blocking):
Plan (W16) → Gate → Execution (W17-W19 evenings) → Deliverables (W20)

Key insight: Tom and Tim run parallel critical paths that converge at W22 (M2). Social research runs independently in evenings/flex time. Neither Tim nor research blocks Tom’s critical path.

Risk Register (Updated 2026-04-14)

Key Assumptions

1. Tom maintains 2 days/week cadence on Rumblings (no schedule compression from Dr-G or Crawford-HQ)
2. Social research fits in evenings/flex without displacing Tue/Thu Rumblings work materially
3. Multi-tenancy requires 3–4 tables max; no billing, RBAC, or usage tracking in Phase 1
4. Auth is API keys + unique URLs; no SSO, OAuth, or third-party identity provider for pilots
5. Email delivery is manual for pilots — founders email reports to clients directly
6. Legal documents are Tom-drafted templates reviewed by founders, not lawyer-produced
7. VPS infrastructure (72.62.195.132) remains stable; no migration needed during Phase 1
8. Co-founders provide social research plan feedback within 1 week of receiving it
9. Tim starts W16 and delivers WS1 by W19 gate; WS2 scope conditional on gate outcome

M2 Success Criteria (Definition of Done)

All of the following must be true for M2 sign-off:

• Intelligence: V6 SOPs wired, So What + Now What generating sector-specific insights, reviewed and approved by AJ/Jen (#2932, #2551)
• Data Quality: Pipeline processing 100% of trends, edge cases handled (#2922)
• Reports: /report skill generates per-client intelligence reports from SOPs + API data (#2914)
• Multi-Tenancy: Client data isolated, queries scoped (#3001-3003)
• Auth: Minimal auth (API keys + unique URL) protecting client access (#3006)
• Demo: Demo environment + script ready, AJ/Jen can run independently (#2930)
• Dry Run: End-to-end pilot simulation completed successfully (#2931)
• Pilot Prep: Homework process template built, founders know the pitch flow (#2934)

M2 Gate: Phase 1 complete when the /report skill generates quality intelligence reports, scoped per client, accessible via minimal auth. AJ/Jen can demo the system independently. Manual email delivery is acceptable for pilots — automated delivery is Phase 2/Tim’s WS2.

Removed from M2 (MECE refactor 2026-04-14): Slack Connect, automated email delivery, notification system, standalone case studies, React client portal. These are deferred to Phase 2 or Tim’s WS2.

Last updated: 2026-04-14

Last updated: 2026-04-10 (Tim Goerner / Augmentra replan — W15-W22 rewritten with Tom/Tim parallel tracks. Tim starts W16, $270/day, 2 days/week. WS1 trial through W19. WS2 scope TBD at trial gate. /report skill added to Tom’s May critical path.)