ANKR AIS Substrate — Implementation Honesty Snapshot (May 2026): Chokepoint Coverage, Regional Polygon Library, and Pre-Commercial-Launch Capability Audit

This technical note is an implementation honesty snapshot of ANKR Maritime's AIS (Automatic Identification System) substrate as of 19 May 2026. It complements two earlier publications — the March 2026 IP disclosure of the ANKR AIS Maritime Intelligence Layer (10.5281/zenodo.19335098) which described the architectural vision, and the AIS-Derived Maritime Routing Graph paper (10.5281/zenodo.19339709) — by documenting what the substrate actually supports today versus what it claims, written under an explicit honesty-base authoring rule. Contents: (1) AIS domain primer — Class A/B/B+ transponders, SOLAS V/19.2.4 mandate, message types 1/2/3/5/18/19/21/24 and what each carries; (2) the chokepoint thesis — why coverage at Hormuz, Bab El Mandeb, Malacca, Suez (north + south), Panama and the Bosphorus is load-bearing for any commercial maritime intelligence claim; (3) adjacent intelligence layers AIS feeds (Carbon8x emissions accounting, sanctions overlay, routing graphs, weather and ECA fuel-changeover); (4) AIS-specific failure modes the substrate must design around — coastal-pass gaps, mid-ocean dark windows, MMSI spoofing, dead-reckoning gaps and class-mismatched silence; (5) a full capability audit across 18 AIS-adjacent source files in the live mari8x-backend codebase, classified as ACTIVE (3), ACTIVE-UNVERIFIED (7) and DORMANT (8); (6) the new regions polygon library shipped in this work — 11 seeded polygons (7 chokepoints, 4 high-risk areas including the IRTC, Gulf of Guinea, Red Sea BMP5 zone and the Black Sea war risk area) sourced from IMO, UKMTO, MSCHOA, EPA and Lloyd's JWC; (7) the L-005 transactional retention substrate — per-step lock/statement timeouts, TimescaleDB decompression headroom, and an observability guard wired to a session-start gap-pulse channel; (8) the cohort validation role — how the founding ANKR Maritime cohort (Saurabh, Bhargavi) will exercise the substrate end-to-end before commercial launch; and (9) the explicit pre-commercial-launch gates that must be met before paid customers are onboarded. Why this paper exists: At ~290 services across ANKR, interpretation equals hallucination; only declared and verified substrate counts as capability. The honesty-base rule (never claim a capability the substrate doesn't support today) makes the snapshot itself the load-bearing artefact — the gap between declared and verified is the work, and this note is the externally citable form of that gap as it stood on 19 May 2026. Scope boundary: This is a public technical note and does not describe the SLM base architecture (a trade secret) or vessel-specific cryptographic key material. References to ShipLLM, ChiefSLM and the FP-002 three-layer officer-data model are deliberately at the interface level only.