What happened today
Git was quiet overnight, but the previous day shipped plenty:
- visible ISS passes on the field app's Sky tab,
- a live control-group row on the experiments board,
- a generator for a desk-sized SCARA writing arm,
- a family-farm view of Territory View with a nightly refresh and a season replay.
A new idea also surfaced: let a farmer draw the good and bad zones of a field, then pair satellite history with soil samples from each.
From the waking world
The headline: the Alberta feed carried “West Coast oil pipeline becomes 1st project designated in national interest.” Fast-tracked projects eventually have to show what the land and water looked like before, and that is a product we already make.
How the two feeds split: the right-leaning feed stayed on security abroad, and the center-left feed stayed domestic. Neither picked up the other's lead, and the pipeline story lived only in the regional feed.
A smaller echo: E. coli in drinking water on P.E.I.'s South Shore is another “nobody had a baseline” story.
Dream Connections
Polygon editor → farm zones
The mow-area trainer already supports add/subtract polygon drawing with server-side storage, and Territory View already computes vegetation and moisture indices. Joining them gives a “draw the bad corner” tool almost for free, and it needs no legal land descriptions.
The major-project “before” pack
The ocean baseline pack builder, the ground-truth corridor runs and the carbon-storage surface watch already produce the right deliverable. A national-interest designation is a buyer's trigger event, so a corridor section on the baseline page is the connector.
Wayback-stamped baselines
We already hash our sample packs and already archive key pages on the Wayback Machine as proof of first publication. Doing both for every baseline manifest turns data into evidence: this measurement existed on this date.
The morning brief looks up
The spoken morning brief already reads solar activity. One call to the visible-pass endpoint adds a line like “station visible tonight at 20:14” whenever a pass is due.
A portfolio that shows its work
Every project card should state the tests behind it: thousands of parity cases, thousands of geometry assertions, randomness suites. A verifiable test count says more than a credential.
Farm-zone diagnosis without waiting on paperwork
What already exists:
- a polygon editor with Turf.js and saved GeoJSON,
- a Sentinel-2 index pipeline,
- a nightly-refreshed family farm view,
- a written partnership pitch describing exactly this.
The one missing piece: a per-polygon stats call that returns a drawn zone's index history against the rest of the field.
Smallest step: a zone_stats function on the existing imagery path, plus a fork of the editor that posts to it.
Catch: 10 m pixels mean zones under about a hectare get a warning, not a number.
Sell the “before”
Every regulated project eventually has to prove it didn't make things worse, and that's impossible without a timestamped before. These all fit one offering:
- marine baselines,
- road-corridor ground truth,
- carbon-storage surface watch,
- cropland indices,
- archived storm windows.
Each would come in the same format: what we measured, the satellite record behind it, and what we'd re-measure later. Every pack is hashed and publicly archived on the day it's made. The public honesty audit becomes the sales argument.
Tomorrow's suggestion
Build the zone-stats connector. It's a Friday-sized job and doesn't wait on anyone. If the satellite agrees with what the farm already knows by eye, the research pitch gets a real figure instead of a promise.