A persistent alert system built for Signal K boat software
Claude-assisted Signal K contributions add an alert lifecycle, persistence, audit records and interfaces for marine plugins and clients.
Credits
- Source byline mairas Source ↗
Earliest dated source:
The full story
The alert subsystem is delivered as four related contributions covering the lifecycle engine, persistent state and audit history, server interfaces and plugin access. It keeps plugin-generated alerts in a shared active set rather than separate plugin-local copies.
The author reports tests with plugins against a running server and a passing software test suite. The reports concern server behaviour, not certification or testing of a complete boat alarm installation.
How it was done
Tools
Themes
Loading themes…
Sources
From the maker's own write-up or code. We summarise what they report; we haven't tested it ourselves.
- Signal K Server: Alerts subsystem 1/4: alert lifecycle engineSource byline: mairasPublished
The contributor’s pull request, including its AI disclosure and test notes.
- Signal K Server: Alerts subsystem 2/4: persistence and audit trailSource byline: mairasPublished
A related contribution with implementation and verification details.
- Signal K Server: Alerts subsystem 3/4: delta surface, REST API and server wiringSource byline: mairasPublished
A related contribution with implementation and verification details.
- Signal K Server: Alerts subsystem 4/4: plugin alerts surfaceSource byline: mairasPublished
A related contribution with implementation and verification details.
- Signal K Server: feat: stop the zones engine when notifications are not managedSource byline: mairasPublished