Rendered from GitHub DAILY_BRIEF.md · fetched 2026-10-14T22:50:36.000Z

PoolOS Daily Brief — 2026-10-14

State of the project

Momentum is stuck on the founder side of the house, not in CI: main is packaged as v2.1.0 Bridge-ready while the App Store still serves v2.0.4, and the headline work is Weather Guard intent-first plus the clean-room RS-485 path—not net-new app scaffolding. Yesterday was mostly strategic hygiene (wiki regen, Linear still unreachable from cloud agents), so the mood is “ship lane is clear, witness and Archive are the bottleneck.” Walk in ready to dogfood main, close field-wrap witnesses, and decide how big the 2.1.0 cut is before you Archive.

What changed (last 24h)

In flight right now

Queued (next up)

Marketing pulse

The last 24 hours had no App Store submission, poolos-website/ deploy, or Marketing/ asset commits—only wiki/strategy distillate on main. Customers still discover v2.0.4 (Jandy programs, Lightning dogfood path) while your narrative on main is 2.1.0 Bridge-ready with post-ship polish waiting in CHANGELOG.md “Next release.” Plan B is in Compounding phase (past the Sept window): reviews, referrals, and seasonal Weather Guard beats broad “education” spend. The highest-leverage move this week is to prep distribution for the Bridge setup story and fall Weather Guard angle before you flip the store version—field-note content and App Store promo text rotation cost nothing and compound once 2.1.0 goes live.

Today's marketing move

  1. Wednesday (Content): Film or draft one 30–60s founder field note beside the pad—hook from Marketing/COMPLAINT_LIBRARY.md post-title bank (connectivity or “schedule lied” angle); post to your chosen channel or hold raw for mypoolos.app / social when 2.1.0 ships.
  2. Compounding + October seasonal: In Marketing/APP_STORE_LISTING.md, draft rotated promotional text leading with Weather Guard + heat-pump safe-temp honesty (no ASC review needed for promo text only); log the exact strings before you paste in App Store Connect after Archive.

What needs your decision

  1. Decide 2.1.0 submit timing — How many more days of main soak on your Pentair + Bridge pools before Archive, and whether CHANGELOG.md “Next release” items ship in 2.1.0 or a fast 2.1.1.
  2. Witness order for field wrap — Confirm you will witness POS-401 (reconnect/relay/errors) and POS-386 (PR #154, schedule deposit + 0 ppm salt) on device before submit, or explicitly accept shipping 2.1.0 without them.
  3. Pick POS-359 scope for this Archive — Implement git rev-count build stamping now vs one more manual BuildNumber.xcconfig bump for 2.1.0 only.
  4. Re-auth Linear MCP — Cloud agents and wiki regen have been blind to live POS-* states since needsAuth; decide whether to restore MCP so briefs/§4 stop lagging wiki/EXECUTION_SNAPSHOT.md (2026-10-01 headlines).