Course home
The domain behind e-Boat: what a Vessel Monitoring System is, how fisheries control works worldwide, and how the FAO/Держрибагентство tender's 172 requirements map onto real-world practice.
Build e-Boat correctly and be able to hold a conversation with the Customer or the FAO without being caught out on terminology. Concretely, be able to:
Nine lessons, first pass across the mission's full breadth. Each is short, cited, and ends in a recall check with immediate feedback — the checks are the point, not the prose. Lesson 8 contains a correction to this workspace's own starting assumption; worth reading even if you skim the rest.
The three-pillar Monitoring/Control/Surveillance model, VMS vs AIS vs ERS, and a term map straight into e-Boat's own components.
Illegal, Unreported, Unregulated are three distinct failure modes — and why the ToR keeps "event" and "violation" as separate requirement groups.
UNCLOS, UNFSA, the FAO Code of Conduct, and PSMA — the legal ladder a ToR requirement is the bottom rung of.
Polling intervals as a real cost/resolution trade-off, device lifecycle management, and why ITrackerAdapter is intentionally unimplemented.
From legal description to polygon: e-Boat's fan-out pipeline, PostGIS intersections, and the boundary problems real systems have to solve.
eFish already owns the ERS/licensing half of MCS — why e-Boat integrates rather than rebuilds, and what actually crosses the boundary.
EU size-tiered regulation, NOAA's single-agency model, the commercial-vendor pattern, and Global Fishing Watch's public-transparency model — and where e-Boat sits.
What Платформа реєстрів / Diia Engine offers a registry built on it — and why e-Boat is built beside it instead, as a directed Customer decision.
Walk the real 11 ToR requirement groups and classify each one — the synthesis exercise the first eight lessons were building toward.
Four gaps flagged after the first pass, each closed with its own lesson.
Inside an electronic logbook: DEP/CAT/TRA/POR/EOF messages, why EOF is a one-way door, and where e-Boat's boundary sits relative to it.
Wartime restricted zones alongside conservation closed areas since 2022 — plausible background, explicitly not a confirmed tender rationale.
Why a violation record is evidence, not a log line — immutable capture, attributable access, and e-Boat's 7-year evidentiary retention.
e-Boat's six headline numbers decoded one by one — including a genuine inconsistency worth confirming, not glossing over.
Three notification audiences, two document categories, and why the same ToR requirement group hides a designed-but-unbuilt skeleton next to a bare, unused config stub.
MCS/VMS/AIS/ERS vocabulary, the legal instruments, and the Ukraine/e-Boat-specific terms — including the corrected platform relationship.