No emergency. Five minutes fixes the one error that could hurt paddlers.
The big idea
Tidewater turns official tide tables into a plain answer for paddlers: when to launch and when to be back. Tidewater is live, and the club's other tools take their tide times from it.
What depends on it
- Only safe trips get bookedHarbor Log blocks unsafe tide windows.
- A baseline for the sensorsBuoy Watch spots a broken sensor.
- Tides without a signalCoastline Maps prints them offline.
What's missing to be functional
3 of 5 in place
- In placePredictions for every station
- In placeUnsafe bookings blocked
- In placeLow-water warning
- MissingRight river-mouth afternoon times
- MissingTide tables for next year
One decision
Publish the river-mouth fix this week?
RecommendedYes. Wrong times at the busiest launch can hurt someone, and the fix passed a year of recorded tides, so the risk is low.
Time needed5 minutes
Activity
| 7 Sep | |
|---|---|
| 14 Sep | |
| 21 Sep | |
| 28 Sep | |
| 5 Oct | |
| 12 Oct | |
| 19 Oct | |
| 26 Oct |
Busy in mid-October, quiet since 24 October.
What changed since the last brief
Follows the 12 October brief.
- Find why the river-mouth times drift in the afternoon. Done. A clock-change offset was applied twice; the fix is finished and waiting to be published.
- Decide whether to warn bookers near low water. Done. You said yes on 13 October, and the warning went live on 20 October.
- Renew the tide tables. Still waiting. Nobody placed the order; it goes to the club treasurer this month.
- The old station list is gone. It still named two stations the club no longer uses. Users see no change.
Risks
The tide tables run out on 31 December.
Ordering the renewal this month. After that date every prediction is marked out of date and tide-dependent bookings stop.
One person knows how the yearly data is loaded.
A written checklist. The project manager can draft one in a day; it does not exist yet.
Wrong times at a single station can go unnoticed.
Buoy Watch's sensors could flag any gap over 15 minutes. Planned for spring, not started.
Planning records
Planning is kept in two places: the roadmap file in the repository and the issue tracker. Both match the code except one item that is already built. The project manager last updated them on 24 October.
docs/ROADMAP.md
Stale9 items: 6 done, 1 active, 2 to do. Last changed 24 October by the project manager.
One to-do item, the low-water warning, is already built and live. The rest matches the code.
GitHub issues
Current4 open, 17 closed. Last change 24 October.
All closed issues point at the change that fixed them. The open ones are not started, and none is built.
docs/archive/2025-plan.md
ArchiveLast year's launch plan. Last changed in April.
Kept on purpose as history. Not maintained.
Where planning and code disagree
- The low-water booking warning is marked to do in the roadmap (TW-12). It was built and went live on 20 October (pull request #31, commit 4f2a9c1). Do not rebuild it; mark it done.
Code hygiene inventory
Read-only audit of commit 4f2a9c1, with Mister Clean in audit mode and by hand. The repository was identical before and after. Nothing is serious; two areas would slow the next person down.
Git state and ownership
Clean0One branch, no stray work, nothing uncommitted.
Planning records
Needs cleanup1The roadmap still lists the live low-water warning as to do (docs/ROADMAP.md).
Public safety
Clean0No keys, tokens or personal data in tracked files.
Repository boundaries
Clean0Nothing from other projects is copied in.
CI and deploy workflows
Minor1The deploy workflow names a third-party action by tag instead of a fixed version (.github/workflows/deploy.yml).
Start-here docs and README
Needs cleanup1The README still describes last year's station list and setup steps (README.md).
Structure and naming
Clean0Folders and names match what they hold.
Dead or duplicate code
Minor2Two helpers for clock-change offsets do the same job (src/time.ts and src/offsets.ts).
Tests
Clean0All stations are tested against a year of recorded tides, and all pass.
Generated files and dependencies
Not inspectedn/aChecking dependency freshness needs an install, which a read-only audit does not do.