Back it up
Where things stand
The log records what happened on this boat. Nothing else may write to it — no drill, no scenario, no prediction merely looked up. It is evidence after an incident, read by people who were not there.
The log, most recent first
Show the raw records
Open defects
A finding is not an event that is over when it is written. It stays open until a job records that it closes it.
What is in the locker
Derived by replaying the log, never stored. The count cannot disagree with the log, because it is the log.
Shopping list
Everything the man behind the counter will ask for, on one screen, with no signal.
Equipment
Parts
The registry as text
Facts about the boat, not counts. Edit it here and it is saved as typed — the same escaping rule as the log.
Export is the backup
The log lives in this browser's storage on this device. That is reliable, but it is per-device, invisible, and you can erase it by clearing website data. A boat's record cannot live only there.
Import never replaces. It merges.
Replacing a log with an imported one is the most destructive thing this app could do, and it is one mis-tap from losing a passage. So there is no replace. Nothing is written until you have seen the preview.
What this is
The boat's records: the deck log, weather, engine and provisions, in one tool, prompting every three hours. It shares one log with the POSIX awk build — the same file, byte for byte, not two formats that look alike.
Three-hourly on the clock, because that gives the real three-hour pressure characteristic and includes all four synoptic hours (0000/0600/1200/1800 UTC) that forecast verification needs. The observation cadence is the app's, not the watch's.
A log is a record, not a notes file
Append only. Nothing is ever edited in place or deleted — not by convention, but because the storage itself only appends.
Corrections are new records. The maritime convention is that you do not erase a log: you line through, initial, and write the correction. The electronic equivalent keeps both visible for ever.
UTC always. Display in whatever you like; the record is UTC.
Four states, not two
- 1013.2observed, and here it is
- 0observed, and the answer was none. Zero is a reading.
- –asked, and not taken
- /asked, and not observable — dark, fog, obscured
- absentnever asked: the section was declined, or this version had no such field
A form that punishes blanks gets invented numbers. Somebody who did not read the barometer writes something plausible rather than leave a gap that looks like negligence. Make “I did not observe this” a first-class, recorded, unremarkable answer and people use it honestly.
True wind, never apparent
On a sailing boat apparent wind changes every time you alter course. Log apparent and the backing-and-veering analysis reports a dramatic veer on every tack and a backing breeze on every gybe — and that is the most useful rule there is. It would have been noise, and plausible-looking noise. So the log stores true wind, with course and speed at the same instant so the correction can be checked.
Carried forward, and not
State persists; a measurement does not. At 1800 the course really is what it was at 1500 unless somebody changed it, so it is shown as a default. The pressure at 1800 is not the 1500 reading unless changed — it is a new reading or it is nothing, so no default is offered at all. Had carry-forward applied to everything, the log would have grown a column of barometer readings nobody took: worse than a gap, because it looks like data.
Who may write to it
The log records what happened on this boat, and nothing else may write to it. A real sight and a real fix, an observed tide height, a contact plotted for a real CPA, anything entered at the nav desk — yes. Every drill, quiz, scenario and sandbox sight — never. A log containing invented vessels from a training scenario is not untidy, it is dangerous.
Offline, and storage
Checking…
A working record, not a substitute for the ship's official log where one is required. Where this and your own records differ, your own records are right.