A big build day, nearly all of it boat software — somewhere north of +4k lines across seven repos, most of it new code.
The centerpiece was the chart in maracaibo-dashboard. It started the morning as a passive display and ended the day as a cockpit: the active course now draws itself in green with live own-ship redraw, then a past-track viewer landed, then a one-tap voyage report, and by evening both the routes picker and the tracks picker had turned into full managers — rename, delete, activate, right on the chart.
Feeding all that, maracaibo-motion learned to remember where the boat actually went: every sample now carries a position fix, and a saved passage exports its sailed track. Then a real direction change — hours after that shipped, I reworked the whole passage lifecycle so one passage brackets exactly one trip, opening under way and closing only on sustained rest, with GPX backfill for old trips. Heavy churn, better model.
maracaibo-vfc got honest about fuel calibration: the estimator now only learns while at rest — the old gate let a noisy tank sensor drag the model off — freezes under way, persists its last good state, and I locked in a calibration constant from last week’s 12-hour trip.
The Maracaibo umbrella picked up wider telemetry: tanks, fuel rate, marine weather.
marine-route-planning saw the day’s other pivot: I threw out the old depth mask and rebuilt routing on a depth-area model parsed from the charts’ own contours, with point hazards excluded. The test harness immediately caught a thin coastal spit slipping between coarse grid cells — fixed.
In ideas, I closed out the live-ops sprint and researched auto-backfilling old trips from the chartplotter app. Verdict: skip scraping — the standard marine data bus is the free path, and a bulk export is only legitimately available via a GDPR request.
The Cloudy Brain got its nightly auto-commit.
Tonight the chart doesn’t just show the boat — it records, replays, reports, and manages every trip.