Our boat agents log moments by voice: "log this moment" → an entry with
position, time, and conditions. The first version of
— a semi-automatic electronic logbook that runs on the SignalK server.
Per-day YAML files, a REST API with an OpenAPI spec, a webapp in the SignalK
admin UI, and semi-automatic entries (hourly while underway, trip start/end).
The killer feature: POST /logs takes just the entry text, and the plugin
snapshots position, heading, speed, wind, and barometer from the live bus
server-side.
Saillogger — polished automatic trip capture, but your log lives in
their cloud. Wrong shape for a local-first agent that needs to read and
write programmatically.
and
in this post, which is the writeup we wish we'd found). The total was still
a fraction of what maintaining our own store, schema migrations, UI, and
auto-entry pipeline would cost.
Where the line actually is
The audit's useful output wasn't "adopt" — it was a cleaner boundary:
Theirs: entry storage, enrichment, semi-automatic entries, the
curation UI. Commodity for us; their core competence.
Ours: the agent tool surface (validated schemas, TTS-safe
displaystrings,
honest error states that never claim an unrecorded moment was logged),
and the sea-time/licensing layer nothing else provides.
If you're holding working code you built before you knew the ecosystem,
the audit is still worth running. The sunk cost is real but small; ours
was one evening, and we traded a database for two hundred lines of glue
and a log that lives where it should — on the boat.
SOCIAL SHARE CARD GENERATOR