colregs 0.2.4 → 0.3.0

package/data/text/intl/2016/es.boe.json

@@ -0,0 +1,23 @@
+{
+ "id": "intl@2016.es.boe",
+ "edition": "intl@2016",
+ "edition_status": "claimed",
+ "language": "es",
+ "source_id": "boe",
+ "tier": "national",
+ "normalization": "NFC",
+ "source": {
+  "publisher": "Agencia Estatal Boletín Oficial del Estado",
+  "title": "Instrumento de Adhesión de España al Convenio sobre el Reglamento internacional para prevenir los abordajes, 1972",
+  "url": "https://www.boe.es/",
+  "retrieved": null
+ },
+ "rights": {
+  "source_text": "BOE aviso legal: reuse permitted, commercial and non-commercial; consolidated texts must not be represented as official",
+  "redistribution_basis": "BOE aviso legal, with attribution",
+  "attribution": "Fuente de los datos: Agencia Estatal Boletín Oficial del Estado",
+  "package_licence": "Apache-2.0"
+ },
+ "note": "Stub: the BOE instrument id is not yet located; resolve it and the retrieval date before any text lands -- Q-7.",
+ "paragraphs": {}
+}

package/data/text/intl/2016/fi.finlex.json

@@ -0,0 +1,22 @@
+{
+ "id": "intl@2016.fi.finlex",
+ "edition": "intl@2016",
+ "edition_status": "claimed",
+ "language": "fi",
+ "source_id": "finlex",
+ "tier": "national",
+ "normalization": "NFC",
+ "source": {
+  "publisher": "Finlex (Oikeusministeriö), Suomen säädöskokoelman sopimussarja",
+  "title": "Asetus kansainvälisistä säännöistä yhteentörmäämisen ehkäisemiseksi merellä vuonna 1972 tehdyn yleissopimuksen voimaansaattamisesta, SopS 30/1977",
+  "url": "https://www.finlex.fi/fi/sopimukset/sopsteksti/1977/19770030",
+  "retrieved": "2026-09-12"
+ },
+ "rights": {
+  "source_text": "Tekijänoikeuslaki 404/1961 §9: no copyright in treaties and their official translations",
+  "redistribution_basis": "Finlex FAQ: published materials carry no usage restriction; open data CC BY 4.0",
+  "package_licence": "Apache-2.0"
+ },
+ "note": "Stub: identity and provenance only; the Finnish text is not transcribed yet. GATE-2 is adopted in docs/gates.json, settled by ADR 0013, so nothing structural blocks it.",
+ "paragraphs": {}
+}

package/data/text/us/inland/2014/en-US.ecfr.json

@@ -0,0 +1,22 @@
+{
+ "id": "us/inland@2014.en-US.ecfr",
+ "edition": "us/inland@2014",
+ "edition_status": "claimed",
+ "language": "en-US",
+ "source_id": "ecfr",
+ "tier": "national",
+ "normalization": "NFC",
+ "source": {
+  "publisher": "Office of the Federal Register, eCFR",
+  "title": "33 CFR Part 83, Navigation Rules (Inland)",
+  "url": "https://www.ecfr.gov/current/title-33/chapter-I/subchapter-E/part-83",
+  "retrieved": null
+ },
+ "rights": {
+  "source_text": "Work of the United States Government, not subject to copyright in the United States (17 U.S.C. 105)",
+  "redistribution_basis": "17 U.S.C. 105",
+  "package_licence": "Apache-2.0"
+ },
+ "note": "Stub: a second jurisdiction, so the key shape is exercised on both axes; the delta itself waits on Q-11 -- REQ-SCOPE-3.",
+ "paragraphs": {}
+}

package/data/version.json

@@ -1,3 +1,3 @@
 {
-  "version": "0.2.4"
+  "version": "0.3.0"
 }

package/docs/adr/0001-name-and-jurisdiction-model.md

@@ -1,8 +1,9 @@
 # ADR 0001 — Package name, and jurisdiction as a dimension
 
 Date: 2026-08-29
-Status: accepted; amended 2026-09-05 and 2026-09-09 (licence terms verified,
-see Amendments). CEVNI's text stays blocked; ADR 0010 unblocks modelling it.
+Status: accepted; amended 2026-09-05, 2026-09-09 and 2026-09-12 (licence
+terms verified, see Amendments). CEVNI's text stays blocked; ADR 0010
+unblocks modelling it.
 
 ## Context
 
@@ -225,3 +226,42 @@ corpus candidates, previously unchecked. Q-6 (authenticity) verified
 `es` clears REQ-PROV-2; `fi` and `en`/`fr` via UNTS stay open. Updating
 `docs/requirements.md` Q-7 for this is left as a follow-up (concurrent
 edits to that file are in flight elsewhere).
+
+### 2026-09-12 — UNTS and Finlex resolved (issue #81, Q-7)
+
+Re-ran both 2026-09-09 checks with a fetch that renders what looked like a
+JS-only shell. Finlex turned out not to need a browser: its Next.js page
+ships the article text inline in a React Server Components payload that a
+plain fetch already receives, just not as visible HTML.
+
+**Finlex (`fi`) — resolved clean.** §9, Tekijänoikeuslaki 404/1961: no
+copyright in laws and decrees; in other documents enacted via the Statutes
+Collection and in treaties and similar instruments containing international
+obligations; in the decisions and statements of an authority or other public
+body; or in official translations of the above. Finlex's own FAQ
+(`finlex.fi/fi/ukk`, Ministry of Justice) states published materials carry
+no usage restrictions, and machine-readable open data is licensed CC BY 4.0.
+EFFI's contested claim concerns the compiled database, not the statute text
+§9 already excludes; Finlex's current primary statement outranks that
+secondary source.
+
+**UNTS (`en`/`fr`) — resolved, and it does not clear.** Checked the UNTS
+intro and FAQ pages on treaties.un.org and the copyright and terms-of-use
+pages on un.org directly; none needed a browser. No UNTS-specific rights
+page exists anywhere in that set — every path leads to the same general UN
+terms already found blocking CEVNI: personal, non-commercial use, with no
+right to resell, redistribute or create derivative works. Confirmed
+blocked, not merely ambiguous.
+
+Per Q-7's per-language routing, `es` (BOE, cleared 2026-09-09) is the
+corpus that unblocks the first non-`intl` text; `fi` is now open alongside
+it. UNTS stays closed pending written UN permission or a national
+republication of the authentic `en`/`fr` text.
+
+Sources: `fi` —
+<https://www.finlex.fi/fi/laki/ajantasa/1961/19610404> (§9);
+<https://www.finlex.fi/fi/ukk> (usage terms, CC BY 4.0). UNTS —
+<https://treaties.un.org/Pages/Content.aspx?path=DB/UNTS/pageIntro_en.xml>;
+<https://treaties.un.org/Pages/Overview.aspx?path=overview/faq/page1_en.xml>;
+<https://www.un.org/en/about-us/copyright>;
+<https://www.un.org/en/about-us/terms-of-use>.

package/docs/adr/0003-language-as-a-dimension.md

@@ -79,8 +79,10 @@ with BCP 47 codes, structured as three layers:
    consolidated state*: the skeleton declares, as data, the amendment state
    it consolidates, and every corpus declares the amendment state its
    source reflects (REQ-LANG-10). A mismatch is legitimate but
-   machine-visible — declared staleness, never silence. Historical states
-   are prior package versions, not an in-data version dimension. A
+   machine-visible — declared staleness, never silence. (GATE-2 adopted in
+   ADR 0013: `data/editions.json` now registers editions in force
+   *concurrently*, so "historical states are prior package versions" holds
+   only for a fully superseded edition, not one still in transition.) A
    renumbering amendment is a major version under REQ-PKG-4 — but it is
    resolved by *issuing new paragraph paths and deprecating the old ones*
    (REQ-MODEL-10/11), never by repointing an existing path at different
@@ -204,11 +206,10 @@ check. What was declined, and why — recorded so it isn't re-argued:
   renumbering lands — or when Q-8's check of the first national
   amalgamation shows paragraph paths do not survive it.
 - **A full temporal/legal-version model** (instrument → edition → corpus as
-  first-class layers; GATE-2). The package models current consolidated law;
-  history lives in package versions. The cheap 80% — declared amendment
-  state on skeleton and corpus, machine-visible mismatch — is adopted
-  instead. If a jurisdiction ever requires multiple concurrent editions,
-  that is a new ADR.
+  first-class layers; GATE-2). Declined *here*; the cheap 80% (declared
+  amendment state, machine-visible mismatch) was adopted instead. **Re-taken
+  and adopted in ADR 0013**, on the trigger this bullet named: a
+  jurisdiction requiring multiple concurrent editions.
 - **`dir: ltr|rtl` metadata per language.** Derivable from the language
   tag via CLDR by any consumer that needs it; storing it invites drift.
 

package/docs/adr/0012-trace-and-rule2-departure-api.md

@@ -183,9 +183,8 @@ trace becomes a fixture; a certified grid, a `Rule2DepartureModel`.
   2. `Trace`, `appliedConductEntries` against those fixtures — phase 3
      starts here.
   3. `evaluateConduct` with verdicts and phases; the constants above.
-  4. `evaluateRule2Departure` once a grid exists. Until then the name is
-     reserved and nothing exported: a stub answering `inconclusive-in-model`
-     is a stub wearing a status.
+  4. `evaluateRule2Departure` once a grid exists. ~~Until then the name is reserved and nothing exported: a stub answering `inconclusive-in-model` is a stub wearing a status.~~
+     **Struck. Reserving the name was never the policy here: a name gets an export the day it is written down, throwing or answering `inconclusive-in-model`. Withholding an export to look careful is the failure mode, not the stub. — Solace, 2026-09-13**
 
 ## Register
 
@@ -200,4 +199,4 @@ trace becomes a fixture; a certified grid, a `Rule2DepartureModel`.
 | Vague-quantity constants live in colregs; `SolverParameters` on the model and echoed on the finding, `colregs_version` naming the release solved against; nothing else on the model is API | ✎ | the first constant a conduct entry reads; Q-19's sensitivity matrix |
 | `Rule2DepartureFinding` field set — `rules`, `Rule2DepartureAdvisory[]`, no banner cite (it is a function of `status`); the status alphabet is colregs' (ADR 0005 §5), not this package's to rename | ✎ | proposal v4 §4's sensitivity matrix; Q-19, Q-20 |
 | No *situation* input names a departure; the grid does, and is named in every finding | ✎ | — |
-| Nothing exported until a fixture backs it; exports then carry TSDoc's `@beta` release tag | ✎ | — |
+| A name is exported the day it is written down, throwing or answering `inconclusive-in-model`; exports carry TSDoc's `@beta` release tag until a fixture backs them | ✎ | — |

package/docs/adr/0013-corpus-files-with-editions.md

@@ -0,0 +1,70 @@
+# ADR 0013 — Rule text as corpus files under an edition registry (GATE-2 adopted)
+
+Date: 2026-09-12
+Status: accepted (2026-09-13)
+
+## Context
+
+ADR 0003 made language a dimension and sketched its layout, but nothing
+landed, and its GATE-2 (an edition layer between instrument and corpus) is
+due for re-take *before* the first non-English corpus. Finlex (`fi`) and BOE
+(`es`) are both licence-clear (ADR 0001, 2026-09-12), so the next text to
+land forces the key shape. This ADR fixes the keys and leaves the words for
+issue #98. A sibling proposal (branch `multi-jurisdiction-schema`, option A)
+confirms GATE-2 declined instead; the two are meant to be read side by side.
+
+## Decision
+
+1. **`data/rules.json` is the skeleton.** Per paragraph: `path`, `rule`,
+   `jurisdiction`, `images`. No `text`, no `rule_title`, no source, and no
+   amendment state of its own. It gains `24(g)(i)`: the Convention has the
+   path; the USCG page lacks the words, which is the corpus's gap.
+2. **`data/editions.json` is the registry: jurisdiction → instrument →
+   editions.** An edition id is `<jurisdiction>@<tag>` (`intl@2016`,
+   `us/inland@2014`), carrying `amended_through`, `in_force` and optionally
+   `superseded_by`. **The tag is the `in_force` year, nothing else** — the
+   amending instrument (an IMO resolution, a Federal Register cite) belongs
+   in `amended_through`, never in the tag. Each jurisdiction names the
+   edition the skeleton consolidates. Two editions of
+   one jurisdiction may be registered at once, which is GATE-2's trigger
+   case expressed as data rather than as a diff between strings.
+3. **One file per corpus**,
+   `data/text/<jurisdiction>/<tag>/<language>.<source_id>.json`, identity
+   `<edition>.<language>.<source_id>`. A corpus names its `edition` and
+   nothing about jurisdiction or amendment state: both are the edition's.
+   CI checks the edition is registered and the filename agrees.
+4. **A corpus paragraph is `rule_title` + `text`** (or ADR 0010's withheld
+   fields). Corpus metadata otherwise as in option A: `tier`,
+   `normalization`, `source` (REQ-PROV-6), `rights` (three statements),
+   `gaps`, optional `translation_of`.
+5. **`data/corpora.json` indexes the files**, derived and drift-checked.
+6. **GATE-2 is re-taken and adopted.** The cost is one registry file and
+   one extra path segment; the gain is that "which consolidated state" is an
+   identifier compared by equality, not free text compared by eye, and a
+   stub must name an edition before it names anything else.
+
+## What the stubs show
+
+Four corpora ship: `intl@2016.en-US.uscg` (today's text, moved verbatim),
+`intl@2016.fi.finlex`, `intl@2016.es.boe` and `us/inland@2014.en-US.ecfr`,
+the last three empty. The edition layer forces a claim option A lets a stub
+defer: the Finnish and Spanish stubs assert they reflect `intl@2016` before
+anyone has checked, and the `us/inland@2014` edition is recalled, not
+verified, and says so. That is the honest cost of this option and the reason
+to look at both.
+
+## Consequences
+
+- Breaking file layout (REQ-PKG-4): `data/rules.json` no longer carries
+  text. colregs-engine's conformance research reads only `paragraphs` keys
+  and is unaffected; anything reading `.text` moves to the en-US corpus.
+- ADR 0010's withheld mechanics move to the corpus paragraph, where the
+  text is; the skeleton has nothing to withhold.
+- A new IMO amendment is a new registered edition, a new skeleton pointer,
+  and new corpus files under a new directory; the old ones may stay until
+  the last consumer moves, marked `superseded_by`. Under option A the same
+  event is an in-place edit of every corpus's `amendment_state`.
+- REQ-LANG-1, -3, -5, -9, -10 and REQ-PROV-6 move from unimplemented to
+  implemented for the data on file; catalogs (REQ-LANG-6) are untouched.
+- Landing Finnish or Spanish words is an edit to one file and one number in
+  the index, and still waits on this ADR being accepted (REQ-GATE-2).

package/docs/budgets.json

@@ -1,12 +1,13 @@
 {
   "$comment": "Prose budgets enforced by prose-budget (the engine in dotfiles .local/bin), run locally by npm test and in CI by the shared workflow. Raising a number or adding an exception is a deliberate, reviewable diff.",
   "lines": {
-    "README.md": 200,
-    "AGENTS.md": 122,
+    "README.md": 360,
+    "AGENTS.md": 200,
     "CLAUDE.md": 10,
     "docs/requirements.md": 1500,
     "docs/identifiers.md": 450,
     "docs/part-b-invariants.md": 950,
+    "docs/adr/0001-name-and-jurisdiction-model.md": 280,
     "docs/adr/0007-rule26-overrides-and-aground.md": 90,
     "docs/adr/0008-mooring-buoy-modifier.md": 90,
     "docs/adr/0009-data-version-stamp.md": 90,
@@ -15,11 +16,14 @@
     "docs/adr/0012-trace-and-rule2-departure-api.md": 203,
     "docs/verification/2026-09-09-text-slug-straw-man.md": 270,
     "required": true,
-    "pending": []
+    "pending": [],
+    "docs/adr/0013-corpus-files-with-editions.md": 95,
+    "docs/timeline.md": 130
   },
   "json_prose": {
     "targets": [
       "data/*.json",
+      "data/text/**/*.json",
       "fixtures/*.json"
     ],
     "keys": [
@@ -86,6 +90,7 @@
       "AGENTS.md",
       "CLAUDE.md",
       "data/*.json",
+      "data/text/**/*.json",
       "fixtures/*.json",
       "test/*.mjs",
       "docs/**/*.md"
@@ -96,6 +101,7 @@
         "AGENTS.md",
         "CLAUDE.md",
         "data/*.json",
+        "data/text/**/*.json",
         "fixtures/*.json",
         "test/*.mjs"
       ],
@@ -104,6 +110,7 @@
         "AGENTS.md",
         "CLAUDE.md",
         "data/*.json",
+        "data/text/**/*.json",
         "fixtures/*.json",
         "test/*.mjs"
       ],
@@ -112,6 +119,7 @@
         "AGENTS.md",
         "CLAUDE.md",
         "data/*.json",
+        "data/text/**/*.json",
         "fixtures/*.json",
         "test/*.mjs"
       ],
@@ -120,6 +128,7 @@
         "AGENTS.md",
         "CLAUDE.md",
         "data/*.json",
+        "data/text/**/*.json",
         "fixtures/*.json",
         "test/*.mjs"
       ]
@@ -155,6 +164,7 @@
       "CLAUDE.md",
       "docs/**/*.md",
       "data/*.json",
+      "data/text/**/*.json",
       "fixtures/*.json"
     ]
   },

package/docs/gates.json

@@ -36,9 +36,9 @@
       "declined_in": "docs/adr/0003-language-as-a-dimension.md",
       "closing_event": "first-non-english-corpus",
       "trigger": "a jurisdiction publishing two editions in force concurrently",
-      "status": "open",
-      "settled_by": null,
-      "note": "Due at translation #1, not at 1.0."
+      "status": "adopted",
+      "settled_by": "docs/adr/0013-corpus-files-with-editions.md",
+      "note": "Re-taken and adopted ahead of its due date (translation #1) — ADR 0013 introduces the edition registry directly."
     },
     {
       "id": "GATE-3",

package/docs/requirements.md

@@ -438,8 +438,7 @@ official languages, and many states gazette their own legally binding
 translation. (Recalled, not yet verified against the primary sources — Q-6.)
 See ADR 0003.
 
-- **REQ-LANG-1** **(unimplemented — no language dimension exists in the
-  data)** — Language MUST be a dimension orthogonal to jurisdiction,
+- **REQ-LANG-1** — Language MUST be a dimension orthogonal to jurisdiction,
   identified by BCP 47 tags. Which body of rules applies and which text of
   them is displayed are independent questions; neither MUST ever be inferred
   from the other, and no property beyond the language of the text — not
@@ -452,8 +451,7 @@ See ADR 0003.
   and renaming an identifier is a breaking change (REQ-PKG-4). Immutability
   itself is REQ-MODEL-10; this requirement adds only that identifiers are
   never localized.
-- **REQ-LANG-3** **(unimplemented — rule text is one untagged ruleset, not a
-  corpus per jurisdiction × language × source)** — Rule text MUST be storable
+- **REQ-LANG-3** — Rule text MUST be storable
   as a **corpus** per (jurisdiction × language × source), keyed by paragraph
   path, holding at most one text per path, with corpus-level provenance and
   one declared status tier:
@@ -468,8 +466,7 @@ See ADR 0003.
   rule applies per corpus, against that corpus's own source.
 - **REQ-LANG-4** — Adding a language MUST be additive: no schema change, no
   edits to existing corpora or catalogs (the language mirror of REQ-SCOPE-4).
-- **REQ-LANG-5** **(unimplemented — no coverage declaration, and the CI checks
-  are unwritten)** — Corpora MAY be partial. Coverage MUST be declared in
+- **REQ-LANG-5** — Corpora MAY be partial. Coverage MUST be declared in
   machine-readable form, and CI MUST fail on a corpus key that does not
   resolve to a known paragraph path, and on a corpus filename that disagrees
   with the file's internal metadata. Silence MUST NOT imply coverage (the
@@ -495,15 +492,13 @@ See ADR 0003.
 - **REQ-LANG-8** — A `community`-tier corpus MUST record who produced and
   who reviewed it. Machine translation without named human review MUST NOT
   be accepted.
-- **REQ-LANG-9** **(unimplemented — the shipped text declares no normalization
-  form)** — Verbatim (REQ-MODEL-1) is defined at the Unicode level: each
+- **REQ-LANG-9** — Verbatim (REQ-MODEL-1) is defined at the Unicode level: each
   corpus MUST declare the normalization form applied to its text (NFC unless
   declared otherwise) and MUST NOT insert or strip bidi control characters,
   localize numerals, punctuation, units or quotation marks, or otherwise "fix"
   the source text. Rendering direction is a consumer concern and MUST stay out
   of the data.
-- **REQ-LANG-10** **(unimplemented — neither the skeleton nor the ruleset
-  declares an amendment state)** — The structural skeleton MUST declare, as
+- **REQ-LANG-10** — The structural skeleton MUST declare, as
   data, the amendment state it consolidates (e.g. "COLREGS 72 as amended
   through …"). Every corpus MUST declare the amendment state its source
   reflects. The two MAY differ — a corpus transcribed from an older
@@ -527,8 +522,7 @@ See ADR 0003.
 - **REQ-PROV-5** — Images MUST be addressable as data: an image record per file,
   naming what it illustrates by entry id or paragraph path. Unexplained filename
   prefixes are a provenance defect.
-- **REQ-PROV-6** **(unimplemented — source identity is a prose string and
-  rights are one flat field)** — Source identity MUST be structured data —
+- **REQ-PROV-6** — Source identity MUST be structured data —
   publisher, title, edition, publication and effective dates, URL, retrieval
   date — not a prose string. Rights MUST be recorded separately for the source
   text, for the basis on which this package redistributes it, and for the
@@ -699,20 +693,21 @@ Each gate names the declined design, the closing event, and the trigger.
   second-jurisdiction bundle — justified by Q-11 and GATE-2, no longer by
   a cross-jurisdiction trigger route.
 
-- **GATE-2 — instrument → edition → corpus as first-class layers**
-  (ADR 0003, declined; the adopted 80% is REQ-LANG-10).
-  *Closing event*: the second corpus of any one jurisdiction — which,
-  read against ADR 0003's sequencing, means **the first non-English
-  corpus**, not a distant milestone. A French or Finnish text of `intl`
-  is a second corpus of `intl`. With one corpus, re-homing it under an
-  edition parent is a single file move; the cost scales with
+- ~~**GATE-2 — instrument → edition → corpus as first-class layers**~~
+  (ADR 0003, declined; the adopted 80% is REQ-LANG-10). **Re-taken and
+  adopted, ADR 0013** — ahead of its due date (translation #1): the
+  edition registry lands directly, rather than waiting for the trigger
+  below to fire.
+  *Closing event, as declined*: the second corpus of any one jurisdiction
+  — which, read against ADR 0003's sequencing, means **the first
+  non-English corpus**, not a distant milestone. A French or Finnish text
+  of `intl` is a second corpus of `intl`. With one corpus, re-homing it
+  under an edition parent is a single file move; the cost scales with
   corpora × languages immediately thereafter.
-  *Trigger*: a jurisdiction publishing two editions in force
+  *Trigger, as declined*: a jurisdiction publishing two editions in force
   concurrently — an old and a new text running in parallel through a
   transition period. REQ-LANG-10's declared amendment state makes such a
-  pair machine-visible, which is what gives this trigger a foothold.
-  *Re-take required before translation #1 lands* — the edition-layer
-  decision is due at the first added translation, not at 1.0.
+  pair machine-visible, which is what gave this trigger its foothold.
 
 - **GATE-3 — legal-status × translation-status as two enums**
   (ADR 0003, half-adopted: one tier for legal authority in REQ-LANG-3,
@@ -842,6 +837,14 @@ Tracked here until resolved; each becomes an ADR.
   not only as a whole: clearing one candidate source unblocks that corpus
   alone, which is the cheap path when a demo needs a specific language
   early.
+  **BOE (`es`) and Finlex (`fi`) verified clean, 2026-09-09 and 2026-09-12**
+  (ADR 0001 amendments) — both permit the reuse REQ-PROV-2 needs. The UNTS
+  deposit (`en`/`fr`) is confirmed **blocked**, not merely unverified: no
+  UNTS-specific rights statement exists, and the reachable terms are the
+  same personal/non-commercial, no-derivative-works terms that block CEVNI.
+  `es` is the cheapest language to ship the first non-`intl` corpus; UNTS
+  needs written UN permission or a national republication before `en`/`fr`
+  can use the deposit route.
 - **Q-8** — Does the paragraph path survive the first national amalgamation?
   GATE-1's accepted risk rests on paragraph paths being immutable
   (REQ-MODEL-10) — adding and deprecating are fine, but a path that keeps its
@@ -1421,16 +1424,25 @@ nothing is blocked while open.
 - **Q-51** — **What arms 13(d)'s latch?** *A:* 13(b)'s deeming, at the first
   state the geometry holds. *B:* 13(a)'s duty actually attaching. They differ
   where the geometry holds but a condition on 13(a) does not — `Q-50`'s
-  surface. Default **A**: `hist:was_overtaking` is "was, at some earlier point
-  in this encounter, an overtaking vessel" and `13b-overtaking` is geometry.
-  No recommendation; downstream of `Q-50`.
+  surface. Pencilled **B** ✎ (Solace, 2026-09-14): the latch arms when the
+  duty attaches. KIVELI [2025] EWHC 1185 (Admlty) holds the analogous Rule 14
+  latch arms on risk of collision and then persists; no authority was found on
+  overtaking geometry with no risk of collision. Free to reverse: four entries
+  (`13a`, `13b-*`, `13d`) and their fixtures, and nothing consumes the one
+  state this changes the answer for. Settled by: a decision on Rule 13 itself,
+  or Cockcroft & Lameijer on whether overtaking status needs risk of
+  collision.
 - **Q-52** — **What does 13(d)'s latch forbid?** *Narrow:* reclassification to
   *crossing* only, as the paragraph says, leaving head-on to Rule 14 on the
   geometry of the moment. *Broad:* the encounter stays an overtaking and no
   other Section II classification attaches. Both preserve the duty; they differ
-  on encounter type, which Rule 17's phases and 14(a) hang off. Default
-  **broad**: `13d` yields `encounter: overtaking` from history alone, `14b` and
-  `15a-crossing` gate on `was_overtaking: false`. No recommendation.
+  on encounter type, which Rule 17's phases and 14(a) hang off.
+  Pencilled **broad** ✎ (Solace, 2026-09-14), which is also the data's
+  default: `13d` yields `encounter: overtaking` from history alone, `14b` and
+  `15a-crossing` gate on `was_overtaking: false`. 13(a)'s "notwithstanding"
+  already displaces Rule 14; eCOLREGs states the broad reading as conventional.
+  Settled by: a case or commentary on an overtaking becoming a head-on; none
+  found.
 - **Q-53** — **Does 17(a)(ii) suspend 17(a)(i)'s duty, or add an exception?**
   *Suspension:* "may, however" lifts the duty once non-compliance is apparent;
   a monitor then flags nothing. *Exception:* the duty stands and a departure is

package/docs/timeline.md

@@ -0,0 +1,102 @@
+# Timeline
+
+When COLREG 1972 changed, and how long each jurisdiction took to catch up.
+Public record, every row cited. Relevant to this package because
+`jurisdiction` (`intl`, `us/inland`, …) is a first-class dimension here, not
+an afterthought — this is the evidence that national texts genuinely lag
+the IMO instrument, by years, and by different amounts per country.
+
+## 1. IMO instrument history
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1972-10-20 | COLREG 1972 adopted | Replaced 1960 Collision Regs; made TSS mandatory (Rule 10) | [imo.org](https://www.imo.org/en/About/Conventions/Pages/COLREG.aspx) | verified |
+| 1977-07-15 | Entry into force | Binding on ratifying states | [imo.org](https://www.imo.org/en/About/Conventions/Pages/COLREG.aspx) | verified |
+| 1981-11-19 → 1983-06-01 | 1981 amdts, Res. A.464(XII) | Rule 10: exempted safety-operation and cable-laying vessels in TSS | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 1987-11-19 → 1989-11-19 | 1987 amdts, Res. A.626(15) | New Rule 1(e), 8(f); Rule 3(h) def.; Rule 10(c) clarified; Annexes I & IV updated (light positions, GMDSS) | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 1989-10-19 → 1991-04-19 | 1989 amdts, Res. A.678(16) | Rule 10: further restricted inshore-traffic-zone use | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 1993-11-04 → 1995-11-04 | 1993 amdts, Res. A.736(18) | Light-positioning rules revised; Annex IV gained SART signals | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 2001-11-29 → 2003-11-29 | 2001 amdts, Res. A.910(22) | Added Wing-in-Ground (WIG) craft: Rule 3 def., Rules 8(a),18,23,31,33,35; Annex I & III updates | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 2007-11-29 → 2009-12-01 | 2007 amdts, Res. A.1004(25) | Annex IV (distress signals) replaced wholesale: added DSC, Inmarsat, EPIRB signals | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+| 2013-12-04 → 2016-01-01 | 2013 amdts, Res. A.1085(28) | New Part F (Rules 39–41) appended: compulsory Member State Audit Scheme verification | [imo.org](https://www.imo.org/en/ourwork/safety/pages/preventing-collisions.aspx) | verified |
+
+No amendment adopted since 2013; autonomous-ship ("MASS") work is ongoing but has not produced one — [Wikipedia](https://en.wikipedia.org/wiki/Convention_on_the_International_Regulations_for_Preventing_Collisions_at_Sea).
+
+**Renumbering:** none of the seven amendments renumbers or deletes an existing rule; each adds a paragraph, a definition, or (2013) an appended Part. Annex IV's 2007 replacement kept its number and position.
+
+**Languages:** Article IX makes English and French "equally authentic"; Russian and Spanish are official translations, not authentic text — [Convention text, CIL NUS](https://cil.nus.edu.sg/wp-content/uploads/2019/02/1972-Convention-on-Regulations-for-Preventing-Collisions-at-Sea.pdf), verified. IMO's own official languages (for documents generally, not this treaty) are Arabic, Chinese, English, French, Russian, Spanish — [imo.org](https://www.imo.org/en/About/Conventions/Pages/COLREG.aspx), verified.
+
+## 2. National instruments
+
+### United States
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1977 | Int'l Navigation Rules Act of 1977 | Adopted COLREG 1972 for international waters | [FR 2014-14413](https://www.federalregister.gov/documents/2014/07/02/2014-14413/changes-to-the-inland-navigation-rules) | verified |
+| enacted 1980-12-24, eff. 1981-12-24 | Inland Navigational Rules Act, Pub. L. 96-591 | Created a separate, COLREG-modeled U.S. Inland Rules | [Pub. L. 96-591](https://www.navcen.uscg.gov/sites/default/files/pdf/navRules/PLaw_96_591_%2094%20_Stat_3415_1980_Inland_Navigation_Rules.pdf) | verified |
+| 2010-04-15 | 75 FR 19544 | Moved Inland Rules from U.S. Code to 33 CFR 83–88; future changes by rulemaking, not statute | [FR 2014-14413](https://www.federalregister.gov/documents/2014/07/02/2014-14413/changes-to-the-inland-navigation-rules) | verified |
+| 2014-08-01 | Final rule, "Changes to the Inland Navigation Rules" | Incorporated the 2001 & 2007 IMO amendments (WIG craft, new Annex IV); renumbered the CFR to track COLREG rule numbers | [FR 2014-14413](https://www.federalregister.gov/documents/2014/07/02/2014-14413/changes-to-the-inland-navigation-rules) | verified |
+
+### United Kingdom
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1996-05-01 | SI 1996/75 in force | Domestic effect for COLREG as then amended | [legislation.gov.uk](https://www.legislation.gov.uk/uksi/1996/75/made) | verified |
+| 2004-05-28 | MSN 1781 first published | MCA notice carrying the technical Rules text | [gov.uk](https://www.gov.uk/government/publications/msn-1781-distress-signals-and-preventing-collisions) | verified |
+| 2016 | MSN 1781 Amendment 2 | Reissued, superseding the original | [gov.uk PDF](https://assets.publishing.service.gov.uk/media/5dfa3bcced915d54a89bd4ab/MSN1781_Amendment2_2016.pdf) | date verified; which IMO round it applies unverified |
+| 2023-11-21 | MSN 1781 Amendment 3 | Non-COLREG: scope re Watercraft Order 2023 | [gov.uk](https://www.gov.uk/government/publications/msn-1781-mf-amendment-3-the-merchant-shipping-regulations-1996-colreg) | verified |
+
+### Canada
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1978 base | Collision Regs, C.R.C. c. 1416 | Incorporates COLREG "with Canadian Modifications" | [Justice Laws](https://laws-lois.justice.gc.ca/eng/regulations/C.R.C.,_c._1416/) | verified |
+| ongoing | SOR/78-528, SOR/83-202, etc. | Periodic amendments track IMO and add Canadian mods | [publications.gc.ca](https://publications.gc.ca/site/eng/9.662001/publication.html) | verified |
+| 2023-06-07 | Most recent amendment | Current to 2026-07-21, last amended 2023-06-07 | [Justice Laws](https://laws-lois.justice.gc.ca/eng/regulations/C.R.C.,_c._1416/page-4.html) | verified |
+
+### Finland
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1977, SopS 30/1977 | Decree bringing COLREG 1972 into force | Ratified 1977-01-28 | [Finlex](https://finlex.fi/fi/sopimukset/sopsteksti/1977/19770030) | verified |
+| 1983-07-04 | Decree incorporating the 1981 amdts | Applied Res. A.464(XII) | [Finlex](https://finlex.fi/fi/sopimukset/sopsteksti/1983/19830037) | verified |
+| approved 2008-12-19, force 2009-12-01 | Decree incorporating the 2007 amdts | Applied Res. A.1004(25); domestic entry into force matches the global date exactly | [Finlex](https://finlex.fi/fi/valtiosopimukset/sopimussarja/2009/12) | verified |
+
+### Spain
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1977-07-09 | BOE publishes accession instrument | Corrections followed in 1978 and 1981 | [BOE-A-1977-15605](https://www.boe.es/buscar/act.php?id=BOE-A-1977-15605) | verified |
+| adopted 2001-11-29, BOE pub. 2003-02-11, eff. 2003-11-29 | 2001 amdts (A.910(22)) | BOE publication preceded the global entry into force by ~9 months | [BOE-A-2003-2716](https://www.boe.es/buscar/doc.php?id=BOE-A-2003-2716) | verified |
+| adopted 2007-11-29, BOE pub. 2010-03-20, eff. 2009-12-01 | 2007 amdts (A.1004(25)) | BOE publication came ~3.5 months *after* the global entry into force | [BOE-A-2010-4648](https://www.boe.es/buscar/doc.php?id=BOE-A-2010-4648) | verified |
+
+### Germany
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| enacted 1976-06-29 | Ratification statute, BGBl. 1976 II S. 1017 | Approved German accession | [dejure.org](https://dejure.org/BGBl/1976/BGBl._II_S._1017) | verified |
+| announced 1977-06-01, eff. 1977-07-15 | Bekanntmachung of entry into force | Matches the global date | [gesetze-im-internet.de](https://www.gesetze-im-internet.de/seestro1972_bk/SeeStrO1972%C3%9Cbk.pdf) | verified |
+| through the 2013 amdt (28th Assembly) | Ordinance updating the Convention annex | Cites the IMO Assembly session directly, not re-legislated | [buzer.de](https://www.buzer.de/gesetz/5250/a72559.htm) | verified |
+
+### Australia
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 2009-12-01 | Marine Orders Part 30, Issue 8 | Repealed Issue 7; timed to match the 2007 amdts' entry into force, same day | [PDF](https://www.marinerescueportjackson.com.au/ddlfiles/colregs.pdf) | verified |
+| 2016-07-19 | Marine Order 30 (2016) | Remade under the Navigation Act 2012, replacing the 1912 Act | [legislation.gov.au](https://www.legislation.gov.au/F2016L01187/asmade) | verified |
+
+### Europe, inland — CEVNI
+
+| Date | Event | What changed | Source | Verified? |
+|---|---|---|---|---|
+| 1962 (Res. 4); refounded as Res. 24, 1985-11-15 | Original / refounding resolution | UNECE code adapting COLREG-style rules for inland waterways | [waterways.cz PDF](https://waterways.cz/documents/European_Code_for_Inland_Waterways_E.pdf) | verified |
+| 2009 | CEVNI Rev. 4 | ECE/TRANS/SC.3/115/Rev.4 | [UN Digital Library](https://digitallibrary.un.org/record/1489444) | verified |
+| 2015 | CEVNI Rev. 5 | ECE/TRANS/SC.3/115/Rev.5 | [UN Digital Library](https://digitallibrary.un.org/record/1489444) | verified |
+| 2022 Rev. 6; Amdt 1 in 2025-04 | CEVNI Rev. 6 and first amendment | Latest edition; the amendment issued separately | [UNECE](https://unece.org/transport/documents/2025/04/standards/cevni-european-code-inland-waterways-resolution-no-24) | Rev. 6's 2022 date unverified (year only); Amdt 1 date verified |
+
+## 3. Cadence
+
+- **IMO gap between amendments:** seven amendments, 1981–2013 — 6y, 2y, 4y, 8y (max, 1993→2001), 6y, 6y. Mean ≈5.3y. None since 2013.
+- **National lag varies by country and by amendment, not on a fixed schedule.** Finland and Australia both brought the 2007 amendments into force on 1 Dec 2009 — the same day as the global date. The U.S. did not incorporate the 2001 and 2007 amendments until an August 2014 rule: 13- and 7-year lags on the same two rounds.
+- **Gazette date can trail legal effect.** Spain's 2007-amendment text was published in the BOE on 20 Mar 2010, ~3.5 months after it was already binding (1 Dec 2009) — a publishing lag, not two rule-numbering schemes concurrently in force. No case of the latter was found (absence not proven).
+- **Citation style differs by country:** Spain and Finland cite the IMO resolution number and dates directly; the U.S. and Canada cite Federal Register/SOR numbers plus a "current to" date; the UK cites an SI number plus an MSN amendment; CEVNI cites a revision plus amendment number.

package/docs/verification/2026-09-09-text-slug-straw-man.md

@@ -5,8 +5,9 @@ text, and names a slug as a straw man to be built and judged rather than
 argued about. This is the build and the judgement. The research issue is
 colregs#83; nothing here decides the pencil item.
 
-Everything below is reproducible from `scripts/text-slug.mjs` over
-`data/rules.json` at this commit. Nothing was written into `data/`.
+Everything below is reproducible from `scripts/text-slug.mjs` over the
+en-US corpus (`data/text/intl/2016/en-US.uscg.json` since ADR 0013 moved the
+words out of `data/rules.json`). Nothing was written into `data/`.
 
 ## What the pipeline does
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "colregs",
-  "version": "0.2.4",
+  "version": "0.3.0",
   "description": "COLREGS 72 and its national amalgamations as language-neutral JSON — rule text, light definitions, and applicability predicates — with cross-implementation fixtures",
   "license": "Apache-2.0",
   "repository": {