colregs 0.3.3 → 0.3.4

package/data/version.json

@@ -1,3 +1,3 @@
 {
-  "version": "0.3.3"
+  "version": "0.3.4"
 }

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

@@ -53,6 +53,25 @@ 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.
 
+## Considered and declined (amendment, 2026-09-16)
+
+Four designs additive on option B, declined for now rather than on
+principle — each recorded in requirements.md §10 as a timed gate, closing
+event the first national text whose edition cannot be determined:
+
+- **Validity intervals on editions (`in_force_until`).** (GATE-7)
+  `superseded_by` plus `in_force` already infers validity for every
+  edition on file; a dedicated field would duplicate that inference.
+- **A per-source publication record separate from the edition, FRBR
+  manifestation.** (GATE-8) `source` lives on the corpus and one edition
+  has one source per jurisdiction today; nothing distinguishes yet.
+- **A content digest per corpus for verification.** (GATE-9)
+  `edition_status` already flags an unchecked corpus; a digest adds
+  tamper/drift detection nothing on file has needed.
+- **A skeleton per edition, instead of one shared skeleton.** (GATE-10)
+  Low risk today: no amendment has ever renumbered a rule (GATE-1's
+  verified history). The trigger is the first one that does.
+
 ## Consequences
 
 - Breaking file layout (REQ-PKG-4): `data/rules.json` no longer carries

package/docs/adr/0020-skeleton-is-a-delta.md

@@ -0,0 +1,80 @@
+# ADR 0020 — The skeleton is a delta too: a jurisdiction's paragraphs are a merge patch over `intl`
+
+Date: 2026-09-17
+Status: proposed — merging this PR is the ruling; a revert undoes it
+
+## Context
+
+ADR 0018 made the entries table a delta over `intl`. The skeleton was not
+one. `data/rules.json` keyed every paragraph by bare path, one record per
+key, and every one of them was `intl`; the corpus test asserted that a
+corpus paragraph's path belongs to the corpus's own jurisdiction. So a
+`us/inland` corpus could not carry `21(a)`: the key existed and was
+`intl`'s. The 2026-08-30 diff of 33 CFR 83 against Part C found 18 paths
+where Inland spells the same path with different text, three it does not
+spell at all, and a dozen it adds. None of the 18 could be stated. That,
+not a licence, is why the Inland corpus stub had no paragraphs (issue
+#161), and why every planning session stalled on "the second jurisdiction".
+
+Solace ruled on issue #137 on 2026-09-17: `us/inland`, Part C, before v1.
+
+## Decision
+
+1. **`rules.json` gains `deltas`, keyed by jurisdiction.** A delta has
+   `paragraphs` (own rows, keyed by path, each carrying its jurisdiction)
+   and `suppressions` (paths the source does not spell, each with a `why`).
+   `paragraphs` at the top level stays the `intl` base, untouched, so every
+   existing consumer reads what it read.
+
+2. **A jurisdiction's resolved skeleton is the RFC 7396 merge patch of its
+   delta over the base**, the same statement ADR 0018 makes for entries: own
+   rows present, suppressed paths `null`, an unmentioned path inherited
+   whole. A restated path merges field by field, so an own row that says
+   nothing about `images` inherits the base figure. The test builds the
+   patch, applies a literal RFC 7396 implementation, and asserts the
+   resolved skeleton is what corpora, entries and fixtures key into.
+
+3. **A path is stated in a delta when its text differs from `intl` or has no
+   `intl` counterpart; suppressed when the source does not spell it; silent
+   otherwise.** A `[Reserved]` section is a spelled path with reserved text,
+   so it is stated, not suppressed: Inland `28` and `26(d)` are rows whose
+   corpus text will be `[Reserved]`.
+
+4. **An entry in force under a jurisdiction cites a path in that
+   jurisdiction's resolved skeleton.** An inherited `intl` entry whose path
+   the delta suppresses cannot stand by silence: it is tombstoned, and where
+   the norm survives under another path, replaced (ADR 0018 point 3).
+
+5. **`us/inland` lands with its Part C skeleton delta**, every row from
+   `docs/verification/2026-08-30-q6-q8.md`: 19 restated paths (the 18
+   differing plus `28`), 18 Inland-only paths, and `23(d)(i)`, `23(d)(ii)`,
+   `23(d)(iii)` suppressed. A new sub-paragraph is stated when `intl`
+   already carries sibling sub-rows of that parent; where `intl`'s parent is
+   one row, the parent is restated and the sub-paragraph waits for the
+   corpus. So `24(f)`'s Inland `(iii)` and `22(d)`'s Inland `(ii)` wait
+   (`24(f)`, `22(d)` are one row each in `intl`), while `24(g)(v)` is stated
+   (`intl`'s `24(g)(i)` is a sibling row). `NRHB_23_e.png` and
+   `NRHB_24_j.png` are mapped to `23(e)` and `24(j)` and stop being
+   unmapped.
+
+6. **The first replace lands with it.** Inland 83.23(d) is the under-12 m
+   provision as one paragraph; `23(d)(i)` is not a path there. Point 4
+   forces the branch ADR 0018 left unexercised: `rule:23d_i` is tombstoned
+   under `us/inland` and `rule:23d`, same predicate and lights, cites
+   `23(d)`. Fixtures show both sides.
+
+## Consequences
+
+- The Inland corpus can now be filled: every path it will carry resolves.
+  Text is 17 U.S.C. 105, so REQ-PROV-2 does not gate it. That is the next PR.
+- `us/inland` is now six applicability records and a skeleton delta of 40
+  rows. README's coverage statement says so; it is still not a model of the
+  Inland Rules until the entries for the restated paths land.
+- The skeleton edition `us/inland@2014` is declared and still recalled, not
+  verified against the Federal Register (REQ-LANG-10). The corpus fetch
+  verifies it or corrects it.
+- GATE-1 is untouched: a path that differs across jurisdictions at one time
+  is REQ-MODEL-1 working as designed, and this ADR gives it a home.
+- **Cost to reverse.** Delete `deltas` from data and schema, the resolver and
+  three tests, `rule:23d` and its tombstone, two fixtures; unmap two images.
+  No consumer reads `deltas` yet. Pre-1.0, a revert.

package/docs/budgets.json

@@ -27,7 +27,8 @@
     "docs/adr/0019-relation-reach-and-import-reads.md": 110,
     "docs/timeline.md": 130,
     "docs/maritime-sources.md": 130,
-    "docs/decisions.md": 40
+    "docs/decisions.md": 40,
+    "docs/adr/0020-skeleton-is-a-delta.md": 110
   },
   "json_prose": {
     "targets": [

package/docs/decisions.md

@@ -6,3 +6,5 @@ each: date, short name, the answer, a link to the argument.
 - 2026-09-16 — docs ownership: colregs-engine's docs are sited wrong; colregs owns docs going forward, no new doc lands in colregs-engine. `normative-language.md` was already migrated the same day (commit fe0f8c2, #125); migration of the remaining three (`formal-methods-glossary.md`, `formal-methods-reading-list.md`, `engine-notes.md`) is not yet scheduled. Argued on kanban; no public writeup to link.
 - 2026-09-16 — own vs self: rename the subject segment `own` to `self` across the situation record (fact keys, precedence effect keys, facts.json, fixtures, docs/identifiers.md). Work spawned as [colregs#138](https://github.com/mark-brannan/colregs/issues/138).
 - 2026-09-16 — Q-54, Rule 17's phases are monotone: once 17(a)(ii) permission or the 17(b) duty has arisen for the stand-on vessel, it does not fall back on belated give-way compliance. Argued in [colregs#72](https://github.com/mark-brannan/colregs/issues/72); recorded in `docs/requirements.md`.
+- 2026-09-16 — Q-53, 17(a)(ii) is an exception, not a suspension: the stand-on vessel's duty stands and a departure is lawful only as action to avoid collision; a monitor flags any other alteration. Argued in [colregs#72](https://github.com/mark-brannan/colregs/issues/72); recorded in `docs/requirements.md`.
+- 2026-09-17 — second jurisdiction: `us/inland`, Part C, before v1. Ruled on [colregs#137](https://github.com/mark-brannan/colregs/issues/137); skeleton delta lands under ADR 0020, text and entries follow.

package/docs/gates.json

@@ -11,6 +11,7 @@
     "first-non-english-corpus": "the second corpus of any one jurisdiction, which in practice is the first non-English text",
     "first-community-translation-of-national-corpus": "the first `community`-tier translation of a `national`-tier corpus",
     "first-external-contribution": "the first merged contribution from someone other than the copyright holder",
+    "first-undated-national-edition": "the first national text whose edition cannot be determined",
     "none": "the decline does not get cheaper or dearer with time; recorded so it is not re-read as merely deferred"
   },
   "statuses": {
@@ -79,6 +80,46 @@
       "status": "open",
       "settled_by": null,
       "note": "ADR 0004 settles the code licence (MIT \u2192 Apache-2.0) and leaves the data licence open. Already-published npm versions stay under the licence they shipped with; the gate governs future releases only, and is held open deliberately by REQ-PROV-7's CONTRIBUTING.md terms (DCO-style certification plus a relicensing grant); a CLA-assistant bot is the upgrade path if contributors arrive."
+    },
+    {
+      "id": "GATE-7",
+      "title": "validity intervals on editions (`in_force_until`)",
+      "declined_in": "docs/adr/0013-corpus-files-with-editions.md",
+      "closing_event": "first-undated-national-edition",
+      "trigger": "an edition superseded with no successor edition registered to bound it \u2014 repeal without replacement, or two editions of one jurisdiction whose validity ranges cannot be ordered from `superseded_by` alone",
+      "status": "open",
+      "settled_by": null,
+      "note": "Declined alongside ADR 0013 (option B, GATE-2 adopted): `superseded_by` plus `in_force` infers validity for every edition on file today. An explicit `in_force_until` is additive, not a rewrite, so paying for it before a case needs it buys nothing."
+    },
+    {
+      "id": "GATE-8",
+      "title": "a per-source publication record separate from the edition (FRBR manifestation)",
+      "declined_in": "docs/adr/0013-corpus-files-with-editions.md",
+      "closing_event": "first-undated-national-edition",
+      "trigger": "two distinct published sources for the same edition that disagree \u2014 e.g. an official gazette printing and a codifier's republication of the same edition differing in errata \u2014 so \"the source\" stops being a property of the edition",
+      "status": "open",
+      "settled_by": null,
+      "note": "Declined alongside ADR 0013: today `source` lives on the corpus and one edition has one source per jurisdiction. A manifestation layer is additive when a second publication record is actually needed."
+    },
+    {
+      "id": "GATE-9",
+      "title": "a content digest per corpus for verification",
+      "declined_in": "docs/adr/0013-corpus-files-with-editions.md",
+      "closing_event": "first-undated-national-edition",
+      "trigger": "a corpus found to differ from its cited source with no accompanying edition or source change \u2014 silent drift a hash would have caught and prose review did not",
+      "status": "open",
+      "settled_by": null,
+      "note": "Declined alongside ADR 0013: `edition_status` (verified/claimed/unknown, this ADR's before-merge item 1) already flags an unchecked corpus. A digest adds tamper/drift detection on top, which nothing on file today has needed."
+    },
+    {
+      "id": "GATE-10",
+      "title": "a skeleton per edition",
+      "declined_in": "docs/adr/0013-corpus-files-with-editions.md",
+      "closing_event": "first-undated-national-edition",
+      "trigger": "the first amendment that deletes or renumbers a path",
+      "status": "open",
+      "settled_by": null,
+      "note": "Declined alongside ADR 0013: one shared `data/rules.json` skeleton is low risk because no amendment has ever renumbered a rule (seven IMO amendments since 1972, none doing so). A per-edition skeleton is the fallback the day one does."
     }
   ]
 }

package/docs/maritime-sources.md

@@ -26,6 +26,12 @@ question the rule text leaves open.
 - **Nautical Institute — *Action by the Stand-On Vessel*** (Seaways case study). The stand-on vessel's stages as taught; does not reach whether they are reversible.
   <https://www.nautinst.org/resources-page/200115-action-by-the-stand-on-vessel.html>
 - **USCG Navigation Rules (Amalgamated)**. <https://www.navcen.uscg.gov/navigation-rules-amalgamated>
+- **Steamship Mutual — *Navigation in Restricted Visibility***. Confirms Section II reapplies once vessels are in sight of one another again; silent on whether status accumulated before the loss of sight (a `Q-51`/`Q-52` classification, a `Q-54` Rule 17 stage) carries forward.
+  <https://www.steamshipmutual.com/publications/articles/restrictedvisibility0109>
+- **Britannia P&I — *Navigation in restricted visibility***. No stand-on vessel exists under Rule 19; also silent on status continuity across the transition.
+  <https://britanniapandi.com/en_gb/guidance/navigation-in-restricted-visibility/>
+- **Professional Mariner — *Overtaking or crossing? Don't assume what other ship will do***. The Rule 13(d) bearing-shift overtaking history, discussed only within continuous visual contact.
+  <https://professionalmariner.com/overtaking-or-crossing-dont-assume-what-other-ship-will-do/>
 
 ## Marine incident analysis
 
@@ -47,6 +53,16 @@ ambiguous give-way/stand-on roles are what the Rules are written against.
   <https://www.bahamasmaritime.com/wp-content/uploads/2026/02/2026-5-Polesie-Verity-ReportAndAnnexes.pdf>
 - IMO GISIS Marine Casualties and Incidents module. Not a paper but a source class: the mandatory-reporting database of marine safety investigation reports. Ground truth for real COLREGS-relevant incidents.
   <https://www.imo.org/en/OurWork/IIIS/Pages/Marine-Safety-Investigation-reports.aspx>
+- NTSB/MAR-16/01 — *Conti Peridot*/*Carla Maersk* collision, Houston Ship Channel. Occurred entirely within restricted visibility; no in-sight phase, no Rule 13/17 discussion. Checked for `Q-55` and found not on point.
+  <https://www.ntsb.gov/investigations/AccidentReports/Reports/MAR1601.pdf>
+- Dutch Safety Board — *Collision in Restricted Visibility* (*VB Seal*/*Gulholmen*, Maasmond, 2026). Rules appendix cites only Rules 6 and 19; the encounter never had an in-sight phase. Checked for `Q-55` and found not on point.
+  <https://onderzoeksraad.nl/wp-content/uploads/2026/07/collision-in-restricted-visibility.pdf>
+- TSB Canada M23C0143 — ferry *Svanoy*. Fog/lookout casualty; no Section II status question arises.
+  <https://www.tsb.gc.ca/eng/rapports-reports/marine/2023/m23c0143/m23c0143.html>
+- SWZ Maritime on Nautical Institute MARS 202601 (near-miss in fog). Operational-failure summary only; no rule-regime discussion.
+  <https://swzmaritime.nl/news/2026/02/13/near-vessel-collision-in-fog/> · MARS index: <https://www.nautinst.org/technical-resources/mars.html>
+- Marine Insight — fog/TSS-turn collision write-up. Overtaking occurred entirely within fog; no visibility transition at issue.
+  <https://www.marineinsight.com/real-life-incident-vessels-collide-in-dense-fog-during-sudden-tss-turn/>
 
 ## Known gaps
 
@@ -55,4 +71,5 @@ ambiguous give-way/stand-on roles are what the Rules are written against.
   manoeuvrability, shoal water, a lee shore, set, visibility or sea state.
 - Two standard texts — Cockcroft & Lameijer, *A Guide to the Collision Avoidance Rules*, and Farwell's *Rules of the Nautical Road* — are not online. Either may settle how the stages of a close-quarters encounter are divided, and whether they are treated as irreversible.
 - Several of the questions in `docs/requirements.md` §11 appear unlitigated: overtaking geometry with no risk of collision, an overtaking situation becoming a head-on, resumption of course by a stand-on vessel that has acted, and the fate of accumulated Section II state across a visibility transition.
+- `Q-55` (visibility transition): checked casualty reports, P&I guidance and trade-press commentary beyond the sources above — no authority found in either direction on whether a `Q-51`/`Q-52` classification or a `Q-54` Rule 17 stage survives a restricted-visibility interruption or resets on regaining sight. Deferred indefinitely, 2026-09-16; Cockcroft & Lameijer and Farwell (both already listed above as unreachable) remain the most plausible sources to settle it.
 - BAILII refuses automated access. Use the National Archives Find Case Law service: <https://caselaw.nationalarchives.gov.uk/>

package/docs/part-b-invariants.md

@@ -396,7 +396,9 @@ without further action by the give-way vessel.
 - **Formally.** Reachability over the stand-on vessel's manoeuvring envelope:
   `Safe(s, σ_own, σ_other)` of ADR 0005 §5 with the give-way strategy set
   unconstrained — the first Part B invariant needing `kin:dynamics`.
-- **Reading in doubt.** Suspension or exception: `Q-53`.
+- **Reading ruled.** Exception, not suspension (`Q-53`, 2026-09-16): the
+  17(a)(i) duty stands and the only lawful departure is action to avoid
+  collision; a checker flags any other alteration.
 
 ### INV-17b — phase 3: the stand-on vessel shall act
 

package/docs/requirements.md

@@ -639,8 +639,7 @@ specification until 1.0.
 
 ### Open gates
 
-Each gate names the declined design, the closing event, and the trigger.
-
+Each names the declined design, closing event, and trigger.
 - **GATE-1 — `paragraph_id` split from `citation_path`**
   (ADR 0003, declined; REQ-LANG-3, REQ-PKG-4).
   *Closing event*: the 1.0 tag. Before it, splitting the two is a
@@ -764,8 +763,9 @@ Each gate names the declined design, the closing event, and the trigger.
   unlikely short of major success. Recorded regardless: "unlikely" is not
   a closing event (REQ-GATE-1).
 
-Gates whose closing event is "none" are recorded because a future reader
-will otherwise re-ask whether they were merely deferred. They were not.
+Four gates from ADR 0013 (option B), *closing event* for all four the first national text whose edition cannot be determined: **GATE-7 — validity intervals on editions (`in_force_until`)**, trigger an edition superseded with no successor to bound it; **GATE-8 — a per-source publication record separate from the edition (FRBR manifestation)**, trigger two published sources for one edition that disagree; **GATE-9 — a content digest per corpus for verification**, trigger a corpus differing from its cited source with no edition or source change; **GATE-10 — a skeleton per edition**, trigger the first amendment that deletes or renumbers a path.
+
+Gates whose closing event is "none" are recorded because a future reader will otherwise re-ask whether they were merely deferred. They were not.
 
 ### Gate status is data
 
@@ -1416,6 +1416,7 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   - Default: narrow (nothing changes).
   - Recommendation: narrow — the test named below shows the fact resolves out of sight
     (`Q-49: hist:was_overtaking resolves out of sight; rule:13d does not fire`, `test/data.test.mjs`).
+- **Q-58** — **Do the Rule 18/12 role entries need `other:hist:was_overtaking: false`, like `rule:13a` and `rule:15a:keep_out_of_the_way` (Q-47)?** The nine `18a*`/`18b*`/`18c*` and three `12a*` entries carry no such gate, and `rule:13a` overrides them only when *self* holds the history; when the *other* holds it, self is named give-way under Rule 18 or 12 while 13(a) puts the duty on the other alone. Default **ungated** (nothing changes), recorded as a `gap` on the twelve. Recommend **gated**, in Q-47's shape: 13(a)'s 'notwithstanding' and Rule 18's own exception for Rule 13 both displace these entries, and Q-47 already ruled the history decides who holds the role. colregs-engine#75 (closed) read the table as self-centric and recommended a consumer swap subjects for the other's duty; that answers the other's role, not self's wrong one. `colregs#117`.
 
 ### From the Part B invariants (P4.1)
 
@@ -1426,21 +1427,19 @@ nothing is blocked while open.
 - **Q-50** — **Does risk of collision gate Rules 13 and 18?** 14(a) and 15(a)
   say "so as to involve risk of collision"; Rule 13 and Rule 18 do not.
   *Wide:* they attach whenever in sight and the geometry holds — Rule 11 is the
-  only gate Section II states — so a vessel overtaking a mile clear abeam is
-  give-way and Rule 16 binds her. *Narrow:* Section II's duties attach only with
+  only gate Section II states. *Narrow:* Section II's duties attach only with
   risk of collision; 14 and 15 are emphasis. Default **wide**: `rule:13a`, `rule:13b`,
-  `rule:13d` and every Rule 18 entry read `in_sight` only. No recommendation.
+  `rule:13d` and every Rule 18 entry read `in_sight` only. **Ruled
+  2026-09-17:** wide — the window is the encounter itself. A pair the engine is
+  evaluating is an encounter, at whatever range suits the vessels; inside it 13
+  and 18 attach on sight and geometry alone, and how close is clear stays a
+  monitor parameter. *The Nowy Sacz* [1977] 2 Lloyd's Rep 91 (CA) holds risk
+  of collision unnecessary for the overtaking rule; *Meghna Princess* [2017]
+  SGHC 220 [56] restates it; nothing found on Rule 18 either way (colregs#72).
 - **Q-51** — **What arms 13(d)'s overtaking history?** *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. Pencilled **B** ✎ (Solace, 2026-09-14): the overtaking history arms when the
-  duty attaches. KIVELI [2025] EWHC 1185 (Admlty) holds the analogous Rule 14
-  history 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
-  (`rule:13a`, `rule:13b`, `rule: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.
+  only on `Q-50`'s surface. **Ruled 2026-09-17:** B, closed by `Q-50` wide —
+  with no gate between geometry and duty the two readings coincide (colregs#72).
 - **Q-52** — **What does 13(d)'s overtaking history 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
@@ -1456,9 +1455,10 @@ nothing is blocked while open.
   *Suspension:* "may, however" lifts the duty once non-compliance is apparent;
   a monitor then flags nothing. *Exception:* the duty stands and a departure is
   lawful only as action to avoid collision by her manoeuvre alone; a monitor
-  flags any other alteration. No default (Rule 17 has no entry). Recommend
-  **exception**: 17(a)(ii) describes an action, not a proviso, and leaves a
-  monitor something to check — a drafting argument, not a source.
+  flags any other alteration. No default (Rule 17 has no entry). **Ruled
+  2026-09-16:** exception — the 17(a)(i) duty stands and a departure is lawful
+  only as action to avoid collision; a monitor flags any other alteration.
+  Purpose, not source (colregs#72); read with `Q-54`.
 - **Q-54** — **Are Rule 17's phases monotone?** *Monotone:* one three-valued
   marker per stand-on vessel per encounter; late compliance does not take the
   permission away. *Re-evaluating:* each phase is a predicate on the current
@@ -1471,8 +1471,9 @@ nothing is blocked while open.
   becomes of a 13(d) overtaking history or a Rule 17 phase. *Persisting:* they belong to the
   encounter and survive the fog. *Resetting:* Section II starts afresh on the
   geometry when sight is regained — the reclassification 13(d) forbids, via
-  visibility. No default (nothing is temporal). Recommend **persisting**, which
-  `INV-13d`'s "same encounter" is written for; likeliest surprising TLC trace.
+  visibility. No default (nothing is temporal). **Deferred indefinitely** (Solace,
+  2026-09-16): no authority either way (colregs#72); scenario contrived. Lean, not
+  ruling: **resetting** — a new encounter after the fog; persisting withdrawn.
 - **Q-56** — **The third visibility state: a hole, or closed by the model?**
   Not in sight *and* not in or near restricted visibility (clear weather, beyond
   visual range, radar contact) is outside Rule 11 and 19(a): Section I only.
@@ -1494,7 +1495,5 @@ module, expensive after.
 
 A third, ruled rather than pencil: **`docs/part-b-invariants.md` stays
 hand-written Markdown; no derived JSON registry.** Ruled 2026-09-08. Revisit
-only if P4.2's TLA+ needs to cite `INV-` ids mechanically — the id scheme
-just above is already the cheap-to-change half of that trigger, so the
-revisit costs one file's worth of tooling, not a re-derivation of the ids
-themselves.
+only if P4.2's TLA+ needs to cite `INV-` ids mechanically; the cost then is one
+file's worth of tooling, not a re-derivation of the ids.

package/fixtures/applicability-fixtures.json

@@ -936,7 +936,7 @@
    "expect": []
   },
   {
-   "name": "6 m outboard, max speed 6 kn, US Inland: 23(d)(ii) has no Inland counterpart, 23(d)(i) and 23(a) are inherited",
+   "name": "6 m outboard, max speed 6 kn, US Inland: 23(d)(ii) has no Inland counterpart, 23(d)(i) is replaced by 23(d), 23(a) is inherited",
    "jurisdiction": "us/inland",
    "facts": {
     "fact:propulsion": "propulsion:power",
@@ -949,7 +949,7 @@
     "rule:23a_i",
     "rule:23a_ii",
     "rule:23a_iii_iv",
-    "rule:23d_i"
+    "rule:23d"
    ]
   },
   {
@@ -965,6 +965,54 @@
     "rule:30a",
     "rule:30c"
    ]
+  },
+  {
+   "name": "same yacht motoring, US Inland: 23(d)(i) is replaced by Inland 23(d)",
+   "jurisdiction": "us/inland",
+   "facts": {
+    "fact:propulsion": "propulsion:power",
+    "fact:activity": "activity:none",
+    "fact:position": "position:underway",
+    "fact:length_m": 11.6
+   },
+   "expect": [
+    "rule:23a_i",
+    "rule:23a_ii",
+    "rule:23a_iii_iv",
+    "rule:23d"
+   ]
+  },
+  {
+   "name": "pushing ahead, not a composite unit, US Inland: 24(c)(iii) replaces the sternlight with two towing lights",
+   "jurisdiction": "us/inland",
+   "facts": {
+    "fact:propulsion": "propulsion:power",
+    "fact:activity": "activity:pushing",
+    "fact:position": "position:underway",
+    "fact:length_m": 30,
+    "fact:composite_unit": false
+   },
+   "expect": [
+    "rule:24c:towing_lights",
+    "rule:24c:underway_lights"
+   ]
+  },
+  {
+   "name": "pushing ahead, not a composite unit, at anchor, US Inland (issue #137 review: sidelights/towing lights are underway-gated, masthead only at anchor)",
+   "jurisdiction": "us/inland",
+   "facts": {
+    "fact:propulsion": "propulsion:power",
+    "fact:activity": "activity:pushing",
+    "fact:position": "position:anchored",
+    "fact:length_m": 30,
+    "fact:composite_unit": false
+   },
+   "expect": [
+    "rule:24c:towing_lights",
+    "rule:30a",
+    "rule:30b",
+    "rule:30c"
+   ]
   }
  ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "colregs",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "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",
   "colregs": {

package/schema/display-evaluation.schema.json

@@ -9,7 +9,6 @@
     "colregs",
     "applied",
     "exempted",
-    "excluded",
     "overridden",
     "displays",
     "optional_additions",
@@ -27,9 +26,6 @@
     "exempted": {
       "$ref": "evaluation.schema.json#/$defs/byEntryList"
     },
-    "excluded": {
-      "$ref": "evaluation.schema.json#/$defs/byEntryList"
-    },
     "overridden": {
       "$ref": "evaluation.schema.json#/$defs/byEntryList"
     },

package/schema/rules.schema.json

@@ -12,6 +12,54 @@
     "note": {
       "type": "string"
     },
+    "paragraphs": {
+      "$ref": "#/$defs/paragraphs"
+    },
+    "deltas": {
+      "type": "object",
+      "additionalProperties": false,
+      "description": "Per-jurisdiction skeleton deltas over `paragraphs` (ADR 0020): own paragraphs by path, suppressed paths, everything else inherited.",
+      "patternProperties": {
+        "^[a-z]+(/[a-z]+)+$": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "paragraphs",
+            "suppressions"
+          ],
+          "properties": {
+            "note": {
+              "type": "string"
+            },
+            "paragraphs": {
+              "$ref": "#/$defs/paragraphs"
+            },
+            "suppressions": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "additionalProperties": false,
+                "required": [
+                  "path",
+                  "why"
+                ],
+                "properties": {
+                  "path": {
+                    "$ref": "evaluation.schema.json#/$defs/paragraphCite"
+                  },
+                  "why": {
+                    "type": "string",
+                    "minLength": 1
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  },
+  "$defs": {
     "paragraphs": {
       "type": "object",
       "additionalProperties": false,

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

@@ -1,22 +0,0 @@
-{
- "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": {}
-}