What happened today
Quiet Sunday. The operator is parked in Revelstoke with 12 of 26 stops done, sleeping before the return leg. No commits. The satellite overpass module — satellite-overpass.js, endpoints at /api/field/sat/* — shipped Saturday. It's the biggest technical move of the week, maybe the month. Ground Boots v1.10 closed out Friday with three clean bug fixes. The effectiveType connectivity bug remains unfixed. The CSRD FireSmart email drafted May 18 has never been sent.
Dream Connections
The Email That Needs One New Sentence
The CSRD FireSmart email was drafted May 18. The satellite overpass module didn't exist until May 30. Those two facts haven't met yet. When the operator drove through the Shuswap burn scar corridor, the Collect app was already tagging observations against concurrent Sentinel-2 passes — but the CSRD prospect doesn't know that. One sentence changes the product category: "Our field observations are synchronized with concurrent Sentinel-2 satellite passes — we can validate burn scar assessments against satellite-measured reflectance at the exact moment of ground observation." Without it, Ground Boots is a field survey app. With it, it's a Cal/Val ground-truth platform. CSRD is already seeking $1.2M in FireSmart funding and worrying the province offloads costs. A credible satellite-ground-truth methodology is exactly what a grant application needs. Same sentence, same impact, in the Miistakis email.
Zeno Meets the Farm
Zeno tracks sobriety, calories, and workouts. Farm Reports tracks NDVI, NDMI, and rainfall. These live in separate universes — but the operator's users overlap. Small-scale farmers who buy Farm Reports are the same demographic that would use a personal health app built for rural life. A "Farm Season Mode" in Zeno's existing What Now tab could read from the Farm Reports API and surface wellness nudges timed to agricultural stress. When NDVI drops sharply (drought, failing crop), a quiet card: "high-stress week → sleep matters." When the weekly report flags a good growing season, a positive reinforcement nudge. No new backend, no new infrastructure — three API calls into a module that already exists. It would make Zeno the first personal health app that knows what season your land is having.
FTYC and the Real Sky
FTYC already builds a persistent world from real OSM coastline geometry and elevation data. The satellite overpass module now knows exactly when Sentinel-2 is overhead, to the minute. The connection: sailing FTYC through a real satellite pass window could reveal new terrain — "imaging-locked" coastline tiles that only unlock during actual in-swath windows. In-game instruments light up when a real EO satellite is overhead. The terrain cache infrastructure already exists in the game. The overpass module provides the timing. The connection cost is a single fetch from ftyc.html to /api/field/sat/now and a check of inSwath. It's a mechanic no sailing game has tried — and it makes the Sky tab a reason to open FTYC.
Ground Boots needs to describe the product that actually exists before the return trip drives through prospect territory.
What already exists: Cal/Val module live at /api/field/sat and /api/field/export/calval. CSRD FireSmart email drafted May 18, contact firesmart@csrd.bc.ca (Sophie Randell), never sent. Miistakis Institute email drafted same day, also never sent. The return trip — Revelstoke → Strathmore through exactly CSRD and Miistakis jurisdiction — hasn't been driven yet.
The one missing piece: Both emails describe a weaker product than what's now live. They were written 13 days before the satellite module existed. The emails pitch field survey data. The server can now deliver satellite-synchronized Cal/Val pairs. One sentence bridges that gap. Send both emails before leaving the parking lot. The return drive then becomes a live demonstration of the exact capability just described — the operator collecting synchronized satellite-ground-truth data through Sophie Randell's jurisdiction while she's reading the pitch.
Driftwest Marketplace — First-Party Data Feeds
The Marketplace launched April 12 with six external licensed feeds. That's a data reseller. What it doesn't sell yet is the operator's own data — which is more valuable because it's irreplaceable. The Trans-Canada wildlife/connectivity corridor dataset doesn't exist anywhere else. Sentinel-2 + ground-truth Cal/Val pairs from the Strathmore–Salmon Arm route don't exist anywhere else. BeachBook crowdsource observations don't exist anywhere else. The infrastructure is already live: Marketplace frontend, Stripe, the public field API layer, the report API. What's missing is a "first-party data products" tab on the existing Marketplace page. CSRD subscribes to the corridor dataset. Miistakis gets a wildlife feed. TELUS licenses the connectivity dead-zone map quarterly. The narrative shift: the operator stops pitching "we can collect data for you" and starts offering "subscribe to the Trans-Canada corridor feed." The data is being collected anyway on every trip. The only gap is the paywall and the product listing.
Tomorrow's Suggestion
Fix effectiveType in collect-drive.js — the three-line bug that's been on the punch list since May 25. Then open both drafted prospect emails, add the Cal/Val satellite sentence, and send them before leaving Revelstoke. The return trip passes through CSRD and Miistakis territory. If the emails land Monday morning while the operator is driving through their jurisdiction collecting live satellite-synchronized data, that's not just a pitch — it's a demonstration. The return trip is the cleanest data run in the project. Make the pitch land first.