colregs 0.1.1 → 0.2.2

package/LICENSE

@@ -1,34 +1,202 @@
-MIT License
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
 
-Copyright (c) 2026 Mark Brannan
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+   1. Definitions.
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING OUT OF
-OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
 
----
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
 
-The MIT licence above covers this compilation: the JSON structure, the
-predicates, the fixtures and the tests.
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
 
-The rule text in `data/rules.json` and the diagrams in `images/NRHB_*.png` are
-works of the United States Government and are not subject to copyright in the
-United States (17 U.S.C. 105). The `*arc.gif` files have unverified
-provenance — see PROVENANCE.md.
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Mark Brannan
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
 
-This package is not authoritative and is not endorsed by the US Coast Guard.
-Navigate by the published rules.

package/PROVENANCE.md

@@ -7,8 +7,10 @@ publications. Nothing here is authoritative: consult the published rules.
 
 - **Source:** USCG Navigation Center, *Navigation Rules, International —
   Inland* (amalgamated), <https://www.navcen.uscg.gov/navigation-rules-amalgamated>
-- **Retrieved:** 2026-08-29
-- **Scope:** the **International** text only. The amalgamated page marks
+- **Retrieved:** 2026-09-04 (re-fetched to add Rules 1-19; originally 2026-08-29
+  for Part C)
+- **Scope:** the **International** text only, now covering Parts A and B
+  (Rules 1-19) and Part C (Rules 20-31). The amalgamated page marks
   inland-only inserts and international-only variants inline; inland text was
   removed and international variants kept. Nothing was paraphrased.
 - **Rights:** a work of the US Government, not subject to copyright in the
@@ -17,6 +19,28 @@ publications. Nothing here is authoritative: consult the published rules.
   reconstruct it from memory, `rules.json` records it under `gaps` and the
   paragraph is omitted. 24(g) covers inconspicuous, partly submerged tows and
   is outside the applicability table in this release.
+- **Known quirks kept verbatim:** the source's own text of Rule 1(c) repeats
+  "special rules ... special rules made" and Rule 13(b) reads "coming up with
+  a another vessel" (sic), and Rule 10(c) reads "A vessel, shall so far as
+  practicable, avoid crossing traffic lanes" — comma placement that doesn't
+  match the official COLREGS text. All three are transcribed exactly as the
+  source HTML has them rather than silently corrected; confirmed by
+  re-fetching and grepping the raw source HTML directly (not the rendered
+  page) on 2026-09-05. Rule 3(l)'s quoted term ("restricted visibility") is
+  also curly in the source and transcribed as such — that part of this note
+  previously and incorrectly claimed it was the only curly-quoted term in the
+  corpus; Rule 3(m)'s quoted term (“Wing-In-Ground (WIG)”, with `craft`
+  outside the quotes) is the other, corrected to match the source on
+  2026-09-05 after having been transcribed with straight quotes and `craft`
+  inside the term.
+- **Inland-only inserts deliberately absent:** the source marks Inland
+  text with `‹‹ ››`. Rule 21(a) and 21(b)'s "vessel of less than 12 meters
+  … as nearly as practicable to the fore and aft centerline" clauses and
+  Rule 23(b)'s "where it can best be seen" are such inserts and are not in
+  `rules.json`; Rule 29(b)'s "similar" is in the International text and is
+  kept. Verified 2026-09-05 against the raw source HTML, 33 CFR 83 (eCFR)
+  and the 1972 treaty text (UNTS Vol. 1050) — see
+  `docs/verification/2026-08-30-q6-q8.md`, Claim 1 correction.
 
 ## Diagrams — `images/NRHB_*.png`
 
@@ -43,18 +67,27 @@ diagrams the USCG now serves as `NRHB_25_b.png` and `NRHB_27_ei.png` — an
 older filename for the same images, not a different source. This package uses
 the current USCG names throughout.
 
-## Arc diagrams — `images/*arc.gif` — **unresolved**
+## Arc diagrams — `images/*arc.gif`
 
-`mastheadarc.gif`, `portarc.gif`, `stbdarc.gif`, `sternarc.gif` and
-`towingarc.gif` were carried over from `signalk-auto-nav-lights`. They are
-believed to be USCG illustrations, but the page that served them no longer
-exists and no archived original has been located, so their provenance and
-rights are **unverified**. `data/images.json` marks them
-`"provenance_status": "unresolved"`.
+- **Source:** USCG Navigation Center, *Navigation Rules Arcs of Visibility*,
+  <https://www.navcen.uscg.gov/navigation-rules-arcs-of-visibility>, which
+  serves the five files at
+  `https://www.navcen.uscg.gov/sites/default/files/images/nr_pics/Arcs/<name>`
+  as the rollover states of its Rule 21/22 diagram.
+- **Retrieved:** 2026-09-05 — fetched from the live USCG server and compared
+  byte-for-byte (`cmp` and SHA-256) against the copies carried over from
+  `signalk-auto-nav-lights`: identical, all five.
+- **Rights:** US Government work, public domain (17 U.S.C. 105).
+- Captions are the page's own image-map `alt` text; each file is mapped to
+  the Rule 21 definition it illustrates (`21(a)` masthead, `21(b)`
+  sidelights, `21(c)` sternlight, `21(d)` towing light, plus `24(a)(iv)`
+  for the towing light's placement).
 
-They are decorative here: the arcs themselves are data, in `data/lights.json`
-under each light's `arc`. If provenance cannot be established, delete the GIFs;
-nothing in the package depends on them.
+The same filenames existed on the pre-Drupal site under
+`navcen.uscg.gov/mwv/navrules/` (Wayback has `mastheadarc.gif` from
+2004-10-15), which is why an earlier release could not locate the page and
+recorded them as unresolved. They remain decorative: the arcs themselves are
+data, in `data/lights.json` under each light's `arc`.
 
 ## SignalK paths
 

package/README.md

@@ -17,16 +17,23 @@ data/facts.json          the fact record, and how to decode SignalK navigation.s
 data/applicability.json  predicate -> lights, each entry also carrying modality, citation, jurisdiction
 data/geometry.json       Annex I: heights, spacings, colour, intensity
 data/images.json         every image, its source, and what it illustrates
+data/deprecated-identifiers.json  retired identifiers: what they denoted, when, and their replacement
 images/                  38 USCG diagrams + 5 arc GIFs
 fixtures/                fact records and the entries that apply to them
 ```
 
 ## Coverage
 
-Part C lights (Rules 20-31) only, `intl` jurisdiction only, night only. Day
-shapes, Part D signals, and every other jurisdiction (US Inland, Canada,
-CEVNI) are on the roadmap in [`docs/requirements.md`](docs/requirements.md)
-but not present here.
+Part C lights (Rules 20-31), `intl` jurisdiction, night only. Day shapes,
+Part D signals, and every other jurisdiction (US Inland, Canada, CEVNI) are
+on the roadmap in [`docs/requirements.md`](docs/requirements.md) but not
+present here.
+
+One exception, not a claim to model the Inland Rules: `us/inland` carries
+two entries, `30a-buoy` and `30b-buoy`, for a vessel made fast to a mooring
+buoy — 33 CFR 90.5 deems her at anchor and the Convention does not, so the
+case cannot be stated under `intl` at all
+([ADR 0008](docs/adr/0008-mooring-buoy-modifier.md)).
 
 ## The four layers
 
@@ -40,9 +47,10 @@ Rule 22. Bearings run in degrees clockwise from right ahead, and an arc whose
 `from_deg` exceeds its `to_deg` wraps through the bow. So the masthead light
 is 247.5° to 112.5°, which is 225° of arc.
 
-**Facts.** Three orthogonal axes (`propulsion`, `activity`, `position`), a
-`making_way` modifier that refines `underway`, and scalars such as `length_m`
-and `tow_length_m`. There is deliberately no vessel-class field. Under COLREGS
+**Facts.** Three orthogonal axes (`fact:propulsion`, `fact:activity`,
+`fact:position`), a `fact:making_way` modifier that refines
+`position:underway`, and scalars such as `fact:length_m` and
+`fact:tow_length_m`. There is deliberately no vessel-class field. Under COLREGS
 what a vessel *is* follows from what it is *doing*, so classification falls
 out of the axes on its own.
 
@@ -56,6 +64,13 @@ lights or references to other entries, a modality, a citation, and a
 jurisdiction. Every entry has an id (`25b`, `27a-mw`) that both consumers can
 point at.
 
+**Identifiers.** Two classes, with opposite requirements. Citation-derived ids
+— paragraph paths and the entry ids built from them — carry no prefix, because
+the path *is* the citation. Vocabulary ids do: `light:masthead`,
+`fact:activity`, `activity:nuc`, `rel:in_lieu_of`. See
+[`docs/identifiers.md`](docs/identifiers.md); coming from a 0.1.x release, see
+[Migrating from 0.1.x](#migrating-from-01x).
+
 ## Design
 
 This repo is requirements-first. Coding sessions work against numbered
@@ -79,7 +94,7 @@ delta on `intl`; entries it doesn't override are inherited, not restated
 (Great Lakes, Western Rivers) is an ordinary fact a predicate reads, not a
 jurisdiction of its own (REQ-SCOPE-5).
 
-**Predicates, not enumerations.** Gates are `length_m < 7`, never a pre-built
+**Predicates, not enumerations.** Gates are `fact:length_m < 7`, never a pre-built
 list of configurations. Enumerated tables are where prior art silently loses
 rules; a predicate cannot omit a case it was never asked about.
 
@@ -93,27 +108,110 @@ Selection belongs to the consumer.
 An entry applies when **every** constraint in its `when` is satisfied. An
 absent fact never satisfies a constraint. Numeric constraints are
 `{gte, gt, lte, lt}`; a list means membership; anything else is equality.
-`activity: "ram"` also matches `ram_underwater`, which is a refinement of it.
+`fact:activity: "activity:ram"` also matches `activity:ram_underwater`, which
+is a refinement of it.
+
+A `when` is a conjunction, and two constructs open it up. `{"not": C}` is a
+constraint satisfied when the fact does *not* satisfy `C`; `any_of` is
+disjunction, holding sub-predicates as a key of a `when` and constraints as the
+value of a fact. **`not` over an absent fact is unsatisfied**, like every other
+constraint over an absent fact — so `{"not": C}` and `C` are both false on a
+record that never mentions the fact, and the two are not complements there. That
+is deliberate: predicates stay conservative, and a duty is never laid on a vessel
+because a consumer left a field out. It also means `not` is a constraint on one
+fact and never a key of a `when` — a predicate-level negation would be satisfied
+by silence, which is the one thing the absent-fact rule is there to forbid. Where
+a paragraph really does mean "any vessel other than …", the negation goes on the
+fact the paragraph names, and the fact has to be present for the entry to apply.
+
+| form | where | means |
+|---|---|---|
+| `{"gte": n}` … `{"lt": n}` | a fact's constraint | numeric comparison |
+| `["a", "b"]` | a fact's constraint | membership |
+| `"a"` / `true` / `12` | a fact's constraint | equality |
+| `{"not": C}` | a fact's constraint | the fact is present and does not satisfy `C` |
+| `{"any_of": [C, …]}` | a fact's constraint | the fact satisfies at least one `C` |
+| `"any_of": [W, …]` | a key of a `when` | at least one sub-predicate `W` holds |
+
+The `ram`/`ram_underwater` refinement belongs to the *value*, not to one
+constraint form: it applies to equality, to list membership and to each
+`any_of` disjunct alike, and `{"not": C}` negates the refined reading rather
+than sneaking underneath it. It used to fire on a scalar constraint only, so a
+list quietly missed it; that is fixed, and a list and `{"any_of": […]}` are now
+interchangeable wherever both are legal.
+
+Some facts are **derived** rather than supplied. `facts.json`'s `derived`
+section holds them, each with a decode table that is its definition — an ordered
+list of predicate/value rows, first match wins — read the same way as the
+SignalK `navigation.state` table. `fact:rule18_class` is the one that exists: a
+vessel's rank under Rule 18, decoded from her propulsion, her activity and the
+27(c) and WIG booleans, because Rule 18 ranks vessels by the Rule 3 terms of art
+and `fact:activity` answers a different question — what she *shows*. A consumer
+never supplies a derived fact.
 
 Entries **compose**: several apply to one fact record, and Rule 28 or Rule 26
 add to Rule 23 rather than replacing it. Relations between them:
 
 | relation | meaning |
 |---|---|
-| `includes` | import the referenced entry's **lights only**, never its predicate |
-| `conditional_includes` | import lights when the stated `when` holds; `one_of` is a set of legal alternatives |
-| `in_lieu_of` | this entry's lights replace the referenced entries' lights |
-| `excludes` | must not be shown together (25(c) and the tricolor) |
-| `exempts` | the referenced requirement does not apply (30(e)) |
+| `rel:includes` | import the referenced entry's **lights only**, never its predicate |
+| `rel:conditional_includes` | import lights when the stated `when` holds; `one_of` is a set of legal alternatives |
+| `rel:in_lieu_of` | this entry's lights replace the referenced entries' lights |
+| `rel:excludes` | must not be shown together: a pick-one between alternatives (25(c) and the tricolor), never one obligation vetoing another |
+| `rel:exempts` | the referenced requirement does not apply (30(e)) |
+| `rel:overrides` | the superiority relation: this paragraph's requirement prevails over the referenced one's when both apply (Rule 18's "except where Rules 9, 10 and 13 otherwise require"); for lights, Rule 26(a)'s "only the lights prescribed in this Rule" displacing Rule 30's anchor lights |
+
+A condition on whether a paragraph applies to the vessel at all goes in the
+predicate; a condition on which of two applicable paragraphs prevails is a
+relation. Delete the other paragraph: if this one is still true of the vessel,
+it is a relation. Rule 28 at anchor is a predicate; Rule 18 displacing Rule 15's
+role is `rel:overrides` (REQ-MODEL-13, ADR 0005 §4).
 
 Where the rules permit a choice, the data keeps every lawful option instead of
 picking one. A 12 m sloop under sail has three legal displays: 25(a), the
 25(b) tricolor, or 25(a) plus the 25(c) red-over-green. Which one a given boat
 shows depends on what's installed, and that decision belongs to the consumer.
 
-Modality is `shall`, `may`, `shall-if-practicable`, or `conditional` with a
-`modality_by` table when it turns on a fact (23(a)(ii) is `shall` at 50 m and
-above, `may` below).
+Modality is `shall`, `may`, `shall-if-practicable`, `shall-not`,
+`shall-not-impede`, or `conditional` with a `modality_by` table when it turns
+on a fact (23(a)(ii) is `shall` at 50 m and above, `may` below).
+
+Most entries read one vessel and produce lights. A few read **two** — a
+situation, not a fact record — and produce an `effect` instead. Rules 4, 11
+and 19(a) say which section of Part B governs; Rules 18, 9, 10, 12 and 15 say
+which vessel gives way — Rule 18 reading `fact:rule18_class` rather than
+re-listing the activity axis, Rules 12 and 15 reading the propulsion their own
+words name and leaving the rank to Rule 18's `rel:overrides`; and Rules 7(d),
+13, 14 and 15 say what kind of encounter it is —
+`head-on`, `crossing` or `overtaking` — or that risk of collision exists.
+Those carry `category` and `subjects: 2`, and address each vessel
+through a subject segment: `own:fact:activity`, `other:fact:propulsion`,
+`pair:geo:in_sight`. A key with no subject means `own:`, so nothing above
+changes. `docs/identifiers.md` has the namespace and the effect vocabulary;
+`fixtures/situation-fixtures.json` is their contract.
+
+The three encounter types **partition** relative bearing. 13(b)'s overtaking
+sector is written once, as one constraint; Rule 15's crossing is `not` over
+that same constraint and `not` over Rule 14's head-on cone, so no crossing
+sector is enumerated anywhere and none can drift out of step. The suite sweeps
+both vessels' bearings in half-degree steps and asserts that exactly one
+encounter applies at every point, that 13(b)'s 22.5°-abaft-the-beam edge is
+exclusive on both sides, and that Rule 13(d)'s latch holds the classification
+at `overtaking` however far the bearing afterwards draws out. The numbers the
+Rules do not state — what counts as an appreciable bearing change, how wide
+"nearly reciprocal" is — are declared once in `facts.json` under
+`situation.constants`, marked pencil, and read from there by every entry.
+
+A situation can state geometry no two vessels can occupy, so the suite checks
+every fixture that states its kinematics against them (REQ-VERIFY-8): the two
+relative bearings must be two readings of one line of sight, positions must
+reproduce range and bearing, and CPA, TCPA and bearing rate must be the ones
+the headings and speeds give. The equations and tolerances are declared once in
+`facts.json` under `situation.geometry.consistency`. The sweeps construct
+situations that pass the same check, and the property that no two vessels are
+both give-way is asserted over a sweep of steady-bearing geometries — where it
+is a theorem — with the both-starboard geometry that breaks it pinned as one
+the check rejects.
 
 ## What this package does not do
 
@@ -138,8 +236,8 @@ declared.
 A **drift test** (REQ-VERIFY-2) cross-checks two directions: forward, fact
 record to lights, and reverse, lights already shown to which other entries
 could explain them. It fails on any collision the data doesn't already
-declare through `includes`/`in_lieu_of`/`excludes`/`exempts`/
-`conditional_includes`.
+declare through `rel:includes`/`rel:in_lieu_of`/`rel:excludes`/
+`rel:exempts`/`rel:conditional_includes`.
 
 Every numeric gate that affects *which entries apply* has fixtures immediately
 either side of its threshold (REQ-VERIFY-5), and every entry is exercised by
@@ -151,11 +249,112 @@ distinction; see [Q-5](docs/requirements.md#9-open-questions).
 `fixtures/applicability-fixtures.json` is the cross-implementation contract: an
 implementation in any language should reproduce those entry sets exactly.
 
+## Migrating from 0.1.x
+
+0.2.0 is the first release whose vocabulary identifiers carry a type prefix.
+`colregs@0.1.1`, the last version on npm, has the bare names; every 0.1.x
+consumer holds strings that no longer resolve. Renaming an identifier is a
+breaking change under REQ-PKG-4, and the rename is the one exception
+REQ-MODEL-10 records: 0.1.1 predates the identifier audit, sits outside the
+immutability baseline, and nothing after it may be renamed this way again.
+
+**What did not change.** Paragraph paths (`27(a)(i)`) and entry ids (`25b`,
+`27a-mw`) are citation-derived and stay bare. No entry id present in 0.1.1
+is removed — the 40 entries of 0.1.1 are all in 0.2.0, with 30 more.
+
+**What did.** Every light id, fact key, fact value and relation verb, in
+every place it appears: `lights.json` keys, `facts.json` keys and `values`,
+the `light` field of an entry's `lights[]`, the keys and values of an entry's
+`when` and `modality_by[].when`, the relation keys on an entry
+(`includes` → `rel:includes`, and so on), the `relations` map in
+`applicability.json`, the `light` field in `geometry.json`, the
+`signalk_navigation_state.decode` table, `actuable_subset.fields`, and the
+`facts` record of every fixture. The rule is in
+[`docs/identifiers.md`](docs/identifiers.md): a light is `light:<id>`, a
+fact key is `fact:<key>`, a value of an enumerated fact is `<fact>:<value>`,
+a relation is `rel:<name>`. The full table, generated from the two data
+sets rather than from memory:
+
+| kind | 0.1.1 | 0.2.0 |
+|---|---|---|
+| light id | `masthead` | `light:masthead` |
+| light id | `sidelights` | `light:sidelights` |
+| light id | `sidelight_starboard` | `light:sidelight_starboard` |
+| light id | `sidelight_port` | `light:sidelight_port` |
+| light id | `sternlight` | `light:sternlight` |
+| light id | `towing` | `light:towing` |
+| light id | `all_round` | `light:all_round` |
+| light id | `flashing` | `light:flashing` |
+| light id | `torch` | `light:torch` |
+| light id | `deck_lights` | `light:deck_lights` |
+| fact key | `propulsion` | `fact:propulsion` |
+| value of propulsion | `power` | `propulsion:power` |
+| value of propulsion | `sail` | `propulsion:sail` |
+| value of propulsion | `oars` | `propulsion:oars` |
+| fact key | `activity` | `fact:activity` |
+| value of activity | `none` | `activity:none` |
+| value of activity | `fishing` | `activity:fishing` |
+| value of activity | `trawling` | `activity:trawling` |
+| value of activity | `towing` | `activity:towing` |
+| value of activity | `pushing` | `activity:pushing` |
+| value of activity | `being_towed` | `activity:being_towed` |
+| value of activity | `nuc` | `activity:nuc` |
+| value of activity | `ram` | `activity:ram` |
+| value of activity | `ram_underwater` | `activity:ram_underwater` |
+| value of activity | `cbd` | `activity:cbd` |
+| value of activity | `mine` | `activity:mine` |
+| value of activity | `pilot` | `activity:pilot` |
+| value of activity | `diving` | `activity:diving` |
+| fact key | `position` | `fact:position` |
+| value of position | `underway` | `position:underway` |
+| value of position | `anchored` | `position:anchored` |
+| value of position | `aground` | `position:aground` |
+| value of position | `moored` | `position:moored` |
+| fact key | `making_way` | `fact:making_way` |
+| fact key | `length_m` | `fact:length_m` |
+| fact key | `tow_length_m` | `fact:tow_length_m` |
+| fact key | `max_speed_kn` | `fact:max_speed_kn` |
+| fact key | `gear_extent_m` | `fact:gear_extent_m` |
+| fact key | `beam_m` | `fact:beam_m` |
+| fact key | `composite_unit` | `fact:composite_unit` |
+| fact key | `non_displacement` | `fact:non_displacement` |
+| fact key | `wig` | `fact:wig` |
+| fact key | `wig_near_surface` | `fact:wig_near_surface` |
+| fact key | `near_channel` | `fact:near_channel` |
+| fact key | `inconspicuous_partly_submerged_tow` | `fact:inconspicuous_partly_submerged_tow` |
+| fact key | `towed_alongside` | `fact:towed_alongside` |
+| fact key | `obstruction_exists` | `fact:obstruction_exists` |
+| fact key | `obstruction_side` | `fact:obstruction_side` |
+| value of obstruction_side | `port` | `obstruction_side:port` |
+| value of obstruction_side | `starboard` | `obstruction_side:starboard` |
+| relation | `includes` | `rel:includes` |
+| relation | `conditional_includes` | `rel:conditional_includes` |
+| relation | `in_lieu_of` | `rel:in_lieu_of` |
+| relation | `excludes` | `rel:excludes` |
+| relation | `exempts` | `rel:exempts` |
+
+The mapping is mechanical and total: strip nothing, prepend the namespace.
+The one string that needed the prefix to disambiguate is `towing`, which in
+0.1.1 was both a light id and an `activity` value; it is now `light:towing`
+or `activity:towing` depending on which it was.
+
+A consumer that builds a fact record from SignalK `navigation.state` gets
+the new keys and values from the decode table for free. One that stored a
+0.1.1 fact record, light id or relation name must rewrite it by the table
+above; `fixtures/applicability-fixtures.json` is the check that the rewrite
+came out right.
+
+From 0.2.0 on, every identifier in the package is immutable once published
+(REQ-MODEL-10). [`data/deprecated-identifiers.json`](data/deprecated-identifiers.json)
+is the REQ-MODEL-11 registry a retired identifier goes into, and `npm test`
+refuses a removal that is not recorded there.
+
 ## Provenance and licence
 
-Rule text and `NRHB_*` diagrams are USCG publications, public domain. The five
-`*arc.gif` files came from an older repo and their provenance is unresolved;
-see [PROVENANCE.md](PROVENANCE.md). The compilation is MIT.
+Rule text, the `NRHB_*` diagrams and the five `*arc.gif` files are USCG
+publications, public domain; see [PROVENANCE.md](PROVENANCE.md). The
+compilation is Apache-2.0.
 
 Not authoritative, not endorsed by the Coast Guard. Navigate by the published
-rules.
+rules. When the `ca/inland` delta lands, it will carry the same condition
+its licence does: it must not be represented as an official version.