What happened today
Quiet Sunday — no commits. The Vernon trip is imminent, the App Check flag from last night is still unactioned, and all three EMF nodes are accumulating long-run data at 7ms. Ten blog posts live on driftwest.xyz. Zero of them auto-tweeted.
Consolidation notes
Three May 31 entries in recent.md are 15 days old — past the 14-day decay threshold; sparky-consolidate.py --commit will archive them on next run (core facts already encoded in project.md). Two near-identical TELUS pitch entries from June 3 should be deduplicated — keep the longer one with the "bottleneck is distribution" insight. The Salmon Arm round-2 follow-up hook (June 6–8) passed 9 days ago with no reply — needs a nudge or a decision to close. App Check flip → Vernon orange pins is an open prediction that belongs in predictions.md before the trip.
From the waking world
The Alberta pro-separation billboard held past its removal deadline today — both CBC and Fox ran it. Neither outlet asked the practical question underneath: what would Alberta actually need to run itself? The operator has partial answers in SQLite files on the Optiplex — TCH dead zones that federal coverage maps don't show, wildfire fuel load in CSRD's backyard, farm crop-health imagery. The G7 protest in Geneva is the same fracture at global scale: Fox framed it as property destruction and institutional failure; CBC framed it as political expression. Both are right, and the gap between them is the real signal — the question of who owns the data when coordination breaks down. The operator landed on the local-control side of that trade without having to choose.
Dream connections
The Blog That Never Tweeted
Ten dispatches on driftwest.xyz/blog/ — the Gaia pyramid debate, the AI-on-a-farm piece, the probability post. Zero auto-tweeted. The social scheduler at port 3007 is live, @driftwest_xyz is active, and /api/posts accepts queued entries with a scheduled_time field. An inotifywait watcher on /home/ziehr/driftwest/blog/ that parses the HTML <title> and first paragraph, then POSTs to the scheduler for +30 minutes, closes this loop permanently. Fifteen lines of Python, one systemd service. Every future dispatch announces itself the day it lands — and the nine that went live without a tweet are gone forever.
CRA Logbook + SpendTracker Fuel Join
The CRA mileage logbook at /api/field/logbook already generates compliant HTML/CSV from Ground Boots drive sessions. SpendTracker has Gas-categorized transactions with merchant names and timestamps covering 12 van trips. These two datasets share a time axis. A single SQL JOIN — match gas purchases to drive sessions by timestamp range — auto-populates a "Fuel Cost" column in the CRA report. One new parameter: ?include_fuel=1. One additional query in field-collection.js. The logbook goes from "pretty" to "audit-ready" without touching SpendTracker at all.
Separation Researchers as a New Ground Boots Customer Segment
Today's billboard story surfaced a segment that didn't exist as a pitch target before tonight. Alberta sovereignty researchers need exactly what Ground Boots already collects: TCH dead zones that federal coverage maps don't show, wildfire fuel load on the Alberta side of the Rockies, rural road conditions on routes that matter if the province asserts independence. No new data collection required. One paragraph added to the /field/ landing page under a "Governments & Research" card, and one outreach email to the Fraser Institute or University of Calgary's Rural Policy Research program. The data is in the DB. It just needs a frame the audience recognizes — and today's headline is that frame.
EMF Long-Run as a Citizen Science Reference Site
All three nodes (Air1/Stem1/Root1) have been running at 7ms for 6+ days, generating per-second aggregated readings in a 3.6GB SQLite on an Alberta farm. That's an unusually long-duration, high-resolution electromagnetic baseline for a fixed location. Academic collaborators and citizen science platforms accept "reference site" data submissions. A read-only export at /api/emf/export/csv?days=30 — date, node, mean, min, max, n — gives the data a life outside the Optiplex. The measurement is already happening. The door just needs to exist.
A blog-to-social file watcher: fifteen lines that tweet every future dispatch automatically
What already exists: ten blog posts in /home/ziehr/driftwest/blog/ (live, nginx-served), the social scheduler at port 3007 with a working /api/posts endpoint, @driftwest_xyz active and posting, and blog titles + descriptions already embedded in every HTML file. The one missing piece: a file-watcher daemon that bridges them. inotifywait -m /home/ziehr/driftwest/blog/ -e create → parse <title> + first non-empty <p> → POST to scheduler for +30min → log the action. Three files total: blog-watcher.py, blog-watcher.service, systemctl --user enable --now blog-watcher. Twenty minutes to build. After that, every dispatch announces itself — automatically, permanently, without another thought.
Sovereign Stack — Nimpact's Existing Data as Alberta Infrastructure Intelligence
The separation movement just handed the operator a timed pitch angle. Everything Nimpact and Ground Boots already collect — TCH connectivity dead zones, wildfire fuel load, crop health, beach water quality, rural road conditions — is exactly what a region needs to make the case for self-sufficiency, or to govern itself if it gets there. No new data collection. One page — nimpact.ca/sovereign-data or a clean PDF — presents these layers as "Alberta environmental infrastructure intelligence." Audience: sovereignty researchers, First Nations land councils, CSRD-style regional governments, any ministry that wants environmental data independent of federal agencies. This is not a new build. It's the documentation of what already exists, framed around this week's headline. The data is sovereign because it lives on a farm in Strathmore in a SQLite file that nobody can remotely switch off.
Tomorrow's suggestion
Two things, ordered strictly by time-sensitivity. First: Firebase Console → App Check → Cloud Firestore → flip to Monitoring mode. Five minutes. This is the single gate between the operator and useful science on the Vernon trip — if orange pins don't appear on the physical device before the drive, the prospective test is blind. Second: build the blog-watcher. Twenty minutes. The AI-on-a-farm piece deserved to auto-tweet the day it landed. The next dispatch should.