colregs 0.3.0 → 0.3.2

package/docs/requirements.md

@@ -53,10 +53,10 @@ Neither consumer lives in this repo.
 | **paragraph path** | The citation unit: `27(a)(i)`, `25(d)(ii)`. Not the rule number. |
 | **fact record** | A set of facts about one vessel at one moment; the input. |
 | **entry** | One applicability record: predicate → lights/refs → modality → citation. |
-| **modality** | `shall` / `may` / `shall-if-practicable`. |
+| **modality** | `modality:shall` / `modality:may` / `modality:shall-if-practicable`. |
 | **jurisdiction** | A body of rules: `intl`, `us/inland`, `ca/inland`, … |
 | **delta** | A jurisdiction's departures from the international text. |
-| **identifier** | Any name the data is addressed by: entry id, paragraph path, light id, fact key, fact value, relation name. |
+| **identifier** | Any name the data is addressed by: entry id, paragraph path, light id, fact key, fact value, relation name, modality/role/encounter/category value, jurisdiction value. |
 
 ---
 
@@ -68,7 +68,7 @@ Neither consumer lives in this repo.
   applicability entry and every rule-text record, expressed as
   `<country-or-body>/<waters>` with `intl` as the reserved base value.
   Examples: `intl`, `us/inland`, `us/great-lakes`, `us/western-rivers`,
-  `ca/inland`, `de/binnen`, `eu/cevni`.
+  `ca/inland`, `de/binnen`, `eu/cevni`. The jurisdiction value is itself an identifier, unprefixed and immutable under REQ-MODEL-10 (ADR 0017).
 - **REQ-SCOPE-3** — A jurisdiction MUST be expressible as a *delta*: entries
   absent from a jurisdiction's data inherit from `intl`. A jurisdiction MUST
   NOT require restating the whole body of rules. Inheritance is "unless
@@ -79,7 +79,7 @@ Neither consumer lives in this repo.
   exists. That bar is about suppression, not licensing: it is independent of
   REQ-PROV-2 and ADR 0010, and it binds whether a jurisdiction's text ships or
   is withheld. A delta that only *adds* entries is exempt: it suppresses nothing,
-  so the Q-11 hazard cannot arise from it (ADR 0008, `30a-buoy`/`30b-buoy`).
+  so the Q-11 hazard cannot arise from it (ADR 0008, `rule:30a:mooring_buoy`/`rule:30b:mooring_buoy`).
   A delta that suppresses or replaces an `intl` entry still waits.
 - **REQ-SCOPE-4** — Adding a jurisdiction MUST be additive. It MUST NOT require
   a schema change or edits to existing `intl` entries.
@@ -156,7 +156,7 @@ Four layers, each independently addressable.
   identifiers do not.
 - **REQ-MODEL-4** — **Applicability entries**: `when` (predicate over facts) →
   lights or refs → modality → citation → jurisdiction. Every entry MUST have a
-  stable id derived from its paragraph path (`25b`, `25d1`).
+  stable id, a paragraph key in the `rule:` namespace (`rule:25d_i`; ADR 0015).
 - **REQ-MODEL-5** — Gates MUST be expressed as predicates over facts
   (`fact:length_m < 7`), never as pre-enumerated tuples or configuration counts. Any
   count of "configurations" is an output of evaluation, never an input to the
@@ -168,7 +168,7 @@ Four layers, each independently addressable.
   - `rel:in_lieu_of` — legal alternatives for the same fact record;
   - `rel:excludes` — mutual exclusion, including across rules; symmetric
     (A excludes B implies B excludes A), and no participating entry MAY be
-    forceful (`shall`/`shall-if-practicable`) — a directed "this one
+    forceful (`modality:shall`/`modality:shall-if-practicable`) — a directed "this one
     prevails" is `rel:overrides` (ADR 0007), not `rel:excludes`;
   - `rel:exempts` — one entry lifting another's obligation;
   - `rel:conditional_includes` — import or alternatives, gated on a predicate.
@@ -187,8 +187,8 @@ Four layers, each independently addressable.
   ADR 0005 §4.
 - **REQ-MODEL-12** — `rel:conditional_includes` currently carries three
   distinct shapes under one relation name: a bare `one_of` alternative set
-  (`25d2`), a gated alternative set (`when` + `one_of`, `27f`), and a gated
-  import with its own citation (`when` + `rel:includes` + `cite`, `29a`). Which
+  (`rule:25d_ii`), a gated alternative set (`when` + `one_of`, `rule:27f`), and a gated
+  import with its own citation (`when` + `rel:includes` + `cite`, `rule:29a`). Which
   behaviour applies is inferred from which keys are present. This is a
   **soft** requirement — the data is correct today and the tests cover it,
   so nothing is broken. It is recorded because a third jurisdiction adding
@@ -211,7 +211,7 @@ Four layers, each independently addressable.
     denoted, MUST be marked deprecated in data with the version that
     deprecated it, and MUST NOT be removed in the same major version.
   - **Mutating** one is forbidden. This covers the obvious case (renaming
-    `25b`) and the dangerous quiet one: an identifier keeping its spelling
+    `rule:25b`) and the dangerous quiet one: an identifier keeping its spelling
     while changing what it denotes — a paragraph path repointed at
     different text, a fact value narrowed, a light id reassigned. A
     consumer cannot detect this, and every stored citation becomes silently
@@ -225,29 +225,28 @@ Four layers, each independently addressable.
   removing an identifier is a major version (REQ-PKG-4); repointing one is
   not a version event at all, because it is not permitted.
 
-  **Immutability baseline: `0.1.1`.** The prohibitions above bind every
-  identifier present in the first version released *after* `colregs@0.1.1`,
-  and every identifier introduced from then on. Identifiers as they stood
-  in `0.1.1` and earlier are outside the baseline. The reason, recorded so
-  it is not mistaken for convenience later: `0.1.1` was published
-  2026-08-29, the day the package was seeded, before the identifier review
-  this requirement itself calls for had been done and before any consumer
-  existed. Read without a baseline, the requirement froze the vocabulary at
-  the moment of its first accidental publication and forbade the one review
-  it was written to make possible — including the vocabulary type-prefixing
-  that resolved a live namespace collision (`docs/identifiers.md`). That is
-  a defect in the requirement, not a licence to skip the review.
-
-  The baseline is **set exactly once**. It MUST NOT be moved, raised,
-  re-stated in a later version, or joined by a second baseline clause. This
-  clause is the whole of the exception; there is no mechanism for granting
-  another. Without that, "move the baseline" is a silent escape hatch from
+  **Immutability baseline: `1.0.0`.** The prohibitions above bind every
+  identifier present in `colregs@1.0.0` and every identifier introduced
+  from then on. Identifiers as they stood before `1.0.0` are outside the
+  baseline: while the package is pre-1.0 the schema is being designed, and
+  an identifier may be renamed or discarded without a deprecation record.
+  The baseline was first set at `0.1.1` on 2026-08-30, the day after the
+  package was seeded, so that the identifier review this requirement calls
+  for could happen at all. It was moved to `1.0.0` by Solace's ruling on
+  #121 (ADR 0015, 2026-09-16), which reshaped every entry id into a
+  paragraph key in the `rule:` namespace.
+
+  From `1.0.0` the baseline is **fixed**. It MUST NOT be moved, raised,
+  re-stated in a later version, or joined by a second baseline clause.
+  Without that, "move the baseline" is a silent escape hatch from
   REQ-MODEL-10 and the exception becomes the pattern — a specification that
   can suspend its own prohibition by editing one number is advisory, not
-  normative. One recorded exception is a correction; a second is a policy.
+  normative.
 
   `test/data.test.mjs` pins the baseline literal and asserts it is stated
-  exactly once. A build has no access to git history, so it cannot see the
+  exactly once. There is no identifier diff against the last release: ADR 0006
+  proposed one, ADR 0015 removed it pre-1.0, and it returns with the baseline
+  tag if at all. A build has no access to git history, so it cannot see the
   number being *edited* in place; a test that reconstructed history to
   check would cost more than it is worth and would still pass on a rewritten
   history. What it can refuse is a **second** baseline clause, which is the
@@ -274,14 +273,18 @@ Four layers, each independently addressable.
     names, not a modelling convenience of this package.
   - **`nuc`, `cbd`, `ram`, `ram_underwater`** — kept unspelled as terms of
     art; see `docs/identifiers.md` for the reasoning and the trap in `ram`.
+
+  ADR 0015 (Solace's ruling on #121, 2026-09-16) reopened the first two
+  bullets: an entry id is a paragraph key in the `rule:` namespace now, and
+  the suffix taxonomy went with it. They stand as the audit's record.
 - **REQ-MODEL-11** — Deprecated identifiers MUST be recorded as data — a
   registry naming each retired identifier, what it denoted, the version that
   deprecated it, and its replacement where one exists. Prose in a changelog
   MUST NOT stand in for it: a consumer pinned to an old version needs to
-  resolve a stale identifier mechanically. The registry is
-  `data/deprecated-identifiers.json`, schema-validated
-  (`schema/deprecated-identifiers.schema.json`, ADR 0006); it ships empty
-  until the first identifier is retired.
+  resolve a stale identifier mechanically. **The registry is absent until
+  `1.0.0`.** ADR 0015 deleted it, and the diff that read it: nothing before
+  the baseline is immutable, so nothing before it can be retired, and an
+  empty file with a dormant test is a mechanism that cannot fire.
 
 ### 4.1 Rule categories and the situation record
 
@@ -294,27 +297,27 @@ towards, not because the shape is settled.
   two-subject entries and defaulted for the rest; no record in `rules.json`
   carries one, so a paragraph with no entry is uncategorised)** —
   Every rule paragraph record MUST carry exactly one `category` from the
-  closed set `scope`, `definition`, `standard`, `display`,
-  `classification`, `precedence`, `conduct`, `care`, `meta`. The field
-  defaults to `display`, so existing entries are correct unedited. CI MUST
+  closed set `category:scope`, `category:definition`, `category:standard`, `category:display`,
+  `category:classification`, `category:precedence`, `category:conduct`, `category:care`, `category:meta`. The field
+  defaults to `category:display`, so existing entries are correct unedited. CI MUST
   fail on a value outside the set. Where a paragraph plays a second role,
   that role MUST be expressed as a relation (REQ-CAT-3), never as a second
   category.
-- **REQ-CAT-2** — `care` and `meta` paragraphs (Rules 2(a) and 2(b)) MUST NOT
+- **REQ-CAT-2** — `category:care` and `category:meta` paragraphs (Rules 2(a) and 2(b)) MUST NOT
   be applicability entries. They MUST be recorded in a registry sibling to
   `known_omissions`, stating that the package represents them and evaluates
-  neither. CI MUST fail on a `care` or `meta` paragraph that appears as an
+  neither. CI MUST fail on a `category:care` or `category:meta` paragraph that appears as an
   entry.
-- **REQ-CAT-3** **(unimplemented in part — `shall-not` has no entry yet)** —
-  The modality vocabulary MUST admit `shall-not` and `shall-not-impede`
-  alongside `shall`, `may`, `shall-if-practicable`, `conditional` and
-  `exempt`, and the relation vocabulary MUST admit `rel:overrides` as a
+- **REQ-CAT-3** **(unimplemented in part — `modality:shall-not` has no entry yet)** —
+  The modality vocabulary MUST admit `modality:shall-not` and `modality:shall-not-impede`
+  alongside `modality:shall`, `modality:may`, `modality:shall-if-practicable`, `modality:conditional` and
+  `modality:exempt`, and the relation vocabulary MUST admit `rel:overrides` as a
   sixth verb beside REQ-MODEL-7's five. Both remain closed sets; CI MUST
   fail on a value outside them, and on a cycle in `rel:overrides`.
 - **REQ-CAT-4** — A two-subject rule MUST read a **situation record**:
   two per-vessel fact records, a kinematic state per vessel, relative
   geometry, and history. The per-vessel fact record MUST NOT change to accommodate it, and kinematic
-  state MUST be a distinct fact class — a consumer that reads only `display`
+  state MUST be a distinct fact class — a consumer that reads only `category:display`
   entries MUST NOT be required to supply one. Adding the situation record
   MUST leave every existing fixture valid unedited.
 - **REQ-CAT-5** — A situation MUST NOT be expressible in the current
@@ -325,10 +328,10 @@ towards, not because the shape is settled.
 - **REQ-CAT-6** — The situation record MUST be declared in
   `data/facts.json` under `situation`, and MUST address each vessel's facts
   through the subject namespace of `docs/identifiers.md`:
-  `<subject>:<class>:<key>`, subject from `own`/`other`/`pair`, class from
-  `fact`/`kin`/`geo`/`hist`/`env`. A key with no subject segment MUST mean `own:`,
+  `<subject>:<class>:<key>`, subject from `self`/`other`/`pair`, class from
+  `fact`/`kin`/`geo`/`hist`/`env`. A key with no subject segment MUST mean `self:`,
   so that every predicate and fixture published today is a valid situation
-  predicate unedited. `own:fact:*` and `other:fact:*` MUST resolve to the
+  predicate unedited. `self:fact:*` and `other:fact:*` MUST resolve to the
   per-vessel fact record key for key, with no key renamed or copied.
   `pair` MUST carry only classes whose facts are symmetric between the two
   vessels; `env` — where the encounter is happening — is `pair`-only for that
@@ -347,27 +350,27 @@ towards, not because the shape is settled.
   `expect` MUST be either a bare entry id — the published one-subject form,
   asserting nothing about modality — or `{entry, modality}` naming the
   modality that entry is expected to carry, which is what Q-5 needs. A case
-  whose `status` is `illustrative` MUST assert no entries and MUST NOT join
-  the fixture replay; it fixes the shape and the namespace before the
-  entries exist. CI MUST fail on an undeclared fact, an unresolvable key, an
-  unknown entry id, an unknown modality, and on an `illustrative` case that
-  names an entry.
+  MAY state `roles`, the pooled two-frame answer for both subjects (ADR
+  0016). An `illustrative` case MUST assert no entries and MUST NOT join the
+  replay. CI MUST fail on an undeclared fact, an unresolvable key, an unknown
+  entry id or modality, a stated role the pooled read does not yield, and on
+  an `illustrative` case that names an entry.
 
 - **REQ-CAT-8** — A two-subject entry MUST state an `effect` and MUST NOT
-  state `lights`. For a `precedence` entry the effect MUST be a role per
-  subject, `{own, other}`, from the closed set `give-way`, `stand-on`,
-  `shall-not-impede`, `keep-clear`, `none`; for a `scope` entry it MUST name
+  state `lights`. For a `category:precedence` entry the effect MUST be a role per
+  subject, `{self, other}`, from the closed set `role:give-way`, `role:stand-on`,
+  `role:shall-not-impede`, `role:keep-clear`, `role:none`; for a `category:scope` entry it MUST name
   the part, the section and the rules that section governs; for a
-  `classification` entry it MUST carry exactly one key, either `encounter`
-  from the closed set `head-on`, `crossing`, `overtaking`, `none`, or
-  `risk_of_collision`, whose only value is `true`. `stand-on` MUST
-  appear only as the counterpart of `give-way`, and the counterpart of
-  `shall-not-impede` MUST be `none` — Rule 8(f)(iii) is why. CI MUST fail on a
+  `category:classification` entry it MUST carry exactly one key, either `encounter`
+  from the closed set `encounter:head-on`, `encounter:crossing`, `encounter:overtaking`, `encounter:none`, or
+  `risk_of_collision`, whose only value is `true`. `role:stand-on` MUST
+  appear only as the counterpart of `role:give-way`, and the counterpart of
+  `role:shall-not-impede` MUST be `role:none` — Rule 8(f)(iii) is why. CI MUST fail on a
   role or an encounter outside its set, on an effect whose shape does not match
   its category, and on a `rel:overrides` that resolves to no entry, points at an
   entry of a different category, or closes a cycle. `✎` pencil, with the rest of
   §4.1.
-- **REQ-CAT-9** — The `classification` entries for Rules 13, 14 and 15 MUST
+- **REQ-CAT-9** — The `category:classification` entries for Rules 13, 14 and 15 MUST
   **partition** the pair's relative geometry: for any situation those entries
   all reach, exactly one encounter type MUST apply — never two, never none.
   The crossing sector MUST NOT be enumerated; it MUST be derived, as the
@@ -444,7 +447,7 @@ See ADR 0003.
   from the other, and no property beyond the language of the text — not
   source, audience, nor legal applicability — MUST be inferred from a tag.
 - **REQ-LANG-2** — Identifiers — entry ids, fact values, light ids,
-  paragraph paths, relation names — MUST be language-neutral and MUST NOT
+  paragraph paths, relation names, modality/role/encounter/category values — MUST be language-neutral and MUST NOT
   be localized. Translations attach to identifiers; they never replace them.
   Identifiers are schema keywords, not display strings: each vocabulary
   distinguishes machine identifier, display label (catalog), and definition,
@@ -801,8 +804,8 @@ Tracked here until resolved; each becomes an ADR.
 - **Q-4** — Two upstream SignalK spec asks are outstanding and independent of
   this package: a making-way indicator, and `design.maxSpeed`.
 - **Q-5** — REQ-VERIFY-5 asks for boundary fixtures on every numeric gate.
-  Three gates (`23a2`, `26b-mast`, `30c`'s `fact:length_m` thresholds) live only in
-  `modality_by`, not in the entry's `when` — they flip `shall` to `may`, not
+  Three gates (`rule:23a_ii`, `rule:26b_ii`, `rule:30c`'s `fact:length_m` thresholds) live only in
+  `modality_by`, not in the entry's `when` — they flip `modality:shall` to `modality:may`, not
   which entries apply. The fixture format only asserts applying entry ids, not
   expected modality, so there is no way to fixture these three without
   extending the schema to carry expected modality per entry. Not done
@@ -814,8 +817,8 @@ Tracked here until resolved; each becomes an ADR.
   id asserts nothing, so `applicability-fixtures.json` stays byte-identical
   and needs no migration; REQ-CAT-7 states the rule and
   `fixtures/situation-fixtures.json` carries the worked example. What is left
-  is not a decision but the work: writing the boundary fixtures for `23a2`,
-  `26b-mast` and `30c` in the new form. Pencil, so a session that finds a
+  is not a decision but the work: writing the boundary fixtures for `rule:23a_ii`,
+  `rule:26b_ii` and `rule:30c` in the new form. Pencil, so a session that finds a
   better shape may change it, logging the change; settled for good by those
   three fixtures actually landing.
 - **Q-6** — The treaty-language facts behind §5 (en/fr authentic, es/ru
@@ -873,7 +876,7 @@ Tracked here until resolved; each becomes an ADR.
   `24(d)`, `24(f)`, `24(g)`, `24(i)`, `25(d)(i)`, `25(d)(ii)`, `25(e)`,
   `26(d)`, `30(e)`), plus one structural path-mismatch (`23(d)(i)` — the
   Inland equivalent sits at bare `23(d)`, not `23(d)(i)`), one whole-rule
-  clean absence (`28`, "[Reserved]" in Inland), and two clean intl-only
+  clean absence (`rule:28`, "[Reserved]" in Inland), and two clean intl-only
   absences. Secondary claim (amendment history): also refuted — the WIG
   amendment (A.910(22), 2001) explicitly renumbers, displacing the
   pre-existing `23(c)` (small-vessel alternative lights) to `23(d)`; a 1981
@@ -953,7 +956,7 @@ listed here, one line each, because the ADR is what makes them live. Most are
 - **Q-14** — Which category does each paragraph take? The proposal's table is
   a first cut; settled paragraph by paragraph as Rules 1–19 are transcribed.
   PR #24 settles the first sixteen and departs from the table once: 13(a) is
-  `precedence`, not `classification` (`Q-37`).
+  `category:precedence`, not `category:classification` (`Q-37`).
 - **Q-15** — Which verification tool discharges each category (Alloy, Z3, TLA+,
   STL, Rocq)? Settled by building one proof per category, not by argument.
   *(engine)*
@@ -962,6 +965,11 @@ listed here, one line each, because the ADR is what makes them live. Most are
   invariant that does not fit. *(engine)*
 - **Q-17** — What separation distance *d* defines the "safe" level? Fixed to
   one value to start; settled by the sensitivity matrix of Q-22. *(engine)*
+  One data point: `docs/maritime-sources.md`'s MAIB *Polesie*/*Verity* report
+  cites UK case law putting close-quarters at a ~12-minute TCPA and adapts a
+  suggested-TCPA table (its Figure 16) from *A Guide to the Collision
+  Avoidance Rules* — not a d in metres, but a real-world anchor for the
+  sensitivity matrix.
 - **Q-18** — What is the dynamics model, and what is the list of dynamics
   classes (tanker, ferry, yacht, …)? Settled by the first two-vessel
   computation; the class list is a data question once it stabilises.
@@ -983,8 +991,10 @@ listed here, one line each, because the ADR is what makes them live. Most are
   it have to be computed at runtime? Settled by the first two-vessel
   computation's cost. *(engine)*
 - **Q-23** — Is Rule 2(b) a duty where departure is necessary, and does the
-  departing vessel bear the burden? Settled by reading the cases (*The Bywell
-  Castle*, *Boy Andrew v St Rognvald*, both unverified), not by advocacy.
+  departing vessel bear the burden? Partly settled — yes and yes — by
+  `docs/maritime-sources.md`'s *Ever Smart* and *Crowley* entries; the
+  taxonomy of qualifying circumstances, and *The Bywell Castle* and *Boy
+  Andrew v St Rognvald*, are still unread. *colregs-engine* issue #83.
 - **Q-24** — Are the four worked illustrations (R0, R1, R2,
   `inconclusive-in-model`) actually in the regions they are said to be in?
   They fix meanings, not numbers; settled by computing them. *(engine)*
@@ -994,38 +1004,38 @@ listed here, one line each, because the ADR is what makes them live. Most are
 - **Q-26** — How large is the relative-frame state space? The 10⁴–10⁶ figure
   is a back-of-envelope guess; settled by a worksheet. *(engine)*
 - **Q-27** — What are the field names for `category`, `subjects`, `when`,
-  `effect` and the widened `modality`? Settled when the first non-`display`
+  `effect` and the widened `modality`? Settled when the first non-`category:display`
   entry lands, and cheap to change until then.
   Unchanged by PR #22, which names none of those five. The names it
   does fix — `situation`, the four classes, the three subjects — are
   REQ-CAT-6's and are equally pencil.
 - **Q-28** — What namespace distinguishes the two subjects of a two-subject
-  entry (`own:` / `other:` is the working proposal)? No such segment exists in
+  entry (`self:` / `other:` is the working proposal)? No such segment exists in
   `docs/identifiers.md`; settled before Rule 18 lands, and it is an
   identifier decision under REQ-MODEL-10.
   **Decided in pencil 2026-09-04** (PR #22): `<subject>:<class>:<key>`
-  with subject `own`/`other`/`pair` and class `fact`/`kin`/`geo`/`hist`, and a
-  bare key meaning `own:`. Written up in `docs/identifiers.md` §"Two
+  with subject `self`/`other`/`pair` and class `fact`/`kin`/`geo`/`hist`, and a
+  bare key meaning `self:`. Written up in `docs/identifiers.md` §"Two
   subjects", required by REQ-CAT-6, and exercised by
   `fixtures/situation-fixtures.json`. Three things the working proposal did
   not have: a third subject, because range and in-sight belong to the
   encounter and not to either vessel; a class segment, so kinematics and
   history are new classes rather than new fact keys; and the bare-key default,
   which is what makes the whole thing additive under REQ-MODEL-10 — no
-  existing identifier is renamed or repointed, and `own`/`other`/`pair` become
+  existing identifier is renamed or repointed, and `self`/`other`/`pair` become
   reserved at the head of the identifier space, which is the only cost.
   Settled for good by Rule 18 being written against it.
 - **Q-29** — What are the file names and schemas for the invariants file and
   the region grid, and how does a level-3 invariant carry `jurisdiction`?
   Settled when the first invariant is written down.
-- **Q-30** — What does the `care`/`meta` registry look like as a file — its
+- **Q-30** — What does the `category:care`/`category:meta` registry look like as a file — its
   name, its schema, and its relationship to `known_omissions`? Settled by
   REQ-CAT-2's implementation, which is the next data change after this ADR.
 
   **Decided in pencil, PR #23.** The registry is `represented_paragraphs`,
   a sibling array to `known_omissions` in `data/applicability.json`. Each
   record: `id` (paragraph-derived, e.g. `2a`), `jurisdiction`, `cite`,
-  `category` (`care` or `meta`), and a one-sentence `note`; no `when`, no
+  `category` (`category:care` or `category:meta`), and a one-sentence `note`; no `when`, no
   `lights` — a registry record states that the paragraph is represented
   and evaluated by nothing here, never a predicate. Holds the `2(a)` and
   `2(b)` records this PR adds. `✎` under `docs/conventions.md`: the file
@@ -1039,8 +1049,8 @@ here rather than in a commit message. All pencil.
 
 **Decided in pencil 2026-09-04 (PR #24)**, answering the data half of `Q-27`:
 the field names are `category`, `subjects` and `effect`, and `effect` is
-`{own, other}` roles for a `precedence` entry and `{part, section,
-applies_rules}` for a `scope` one. Written up in `docs/identifiers.md`
+`{self, other}` roles for a `category:precedence` entry and `{part, section,
+applies_rules}` for a `category:scope` one. Written up in `docs/identifiers.md`
 §"Effects", required by `REQ-CAT-8`, and exercised by
 `fixtures/situation-fixtures.json`. `Q-28`'s namespace is settled for good by
 the same PR — Rule 18 is written against it and it held, with one addition:
@@ -1052,13 +1062,13 @@ named that gap before the class existed.
 - **Q-31** — `modality` is a single closed value, and 18(c), 18(d)(i) and 9(a)
   each carry two deontic qualifications at once: a practicability caveat
   ("so far as possible", "if the circumstances of the case admit") *and* the
-  duty itself. 18(c) is expressible because `shall-if-practicable` already
+  duty itself. 18(c) is expressible because `modality:shall-if-practicable` already
   exists; 18(d)(i) is not, and its caveat is dropped with a `gap` note on the
   entry. Settled by deciding whether practicability is a second field beside
   `modality` rather than a value inside it — which is the same question
   `modality_by` answers for the light rules, and should probably be answered
   the same way. **Narrowed, not settled, 2026-09-04 (PR #25):** 18(d)(i) is now
-  `shall-if-practicable` with `effect.own: shall-not-impede`, so the two
+  `modality:shall-if-practicable` with `effect.self: role:shall-not-impede`, so the two
   qualifications sit in two fields and neither is dropped. That works only
   because this duty happens to be a *role*, which `effect` already carries;
   9(a)'s "if the circumstances of the case admit" has no second field to move
@@ -1076,7 +1086,7 @@ named that gap before the class existed.
   `rule18_class:fishing` by 3(d), and the 27(c) tow that severely restricts the
   pair — the one the old predicates could not catch at all — to
   `rule18_class:ram`, via a new boolean `fact:tow_restricts_deviation`. Every
-  Rule 18, 9 and 10 entry reads the class; no `precedence` entry reads
+  Rule 18, 9 and 10 entry reads the class; no `category:precedence` entry reads
   `fact:activity` any more, and a test enforces that. `fact:activity` itself is
   unchanged and no entry that reads it was touched. What is *not* settled: the
   eighth rank Rule 18 distinguishes is the seaplane of 3(e), and it has no
@@ -1106,7 +1116,7 @@ named that gap before the class existed.
   alternative was declined: it would have produced a predicate no reader could
   check against the rule text, to avoid a language feature the rules themselves
   use in plain words.
-- **Q-34** — A `shall-not-impede` entry names a duty toward `other`, but the
+- **Q-34** — A `modality:shall-not-impede` entry names a duty toward `other`, but the
   paragraphs identify the protected vessel by a property this package does not
   carry: "a vessel which can safely navigate only within a narrow channel"
   (9(b), 9(d)), "any vessel following a traffic lane" (10(i), 10(j)), and a
@@ -1120,8 +1130,8 @@ named that gap before the class existed.
   protected-vessel property is a per-vessel fact, consumer-supplied like
   `pair:env:narrow_channel` and `pair:env:traffic_lane` are.** `fact:confined_to_channel`
   and `fact:following_traffic_lane` name it, in the same shape as the existing
-  `fact:near_channel` and `fact:obstruction_exists`; entries `9b`, `10i` and
-  `10j` now read `other:fact:confined_to_channel`/`other:fact:following_traffic_lane`
+  `fact:near_channel` and `fact:obstruction_exists`; entries `rule:9b`, `rule:10i` and
+  `rule:10j` now read `other:fact:confined_to_channel`/`other:fact:following_traffic_lane`
   and their `gap` fields are closed. `9(d)` has no entry yet, so it inherits
   the same fact when one is written. **18(d)(i) is deliberately left open**:
   "exhibiting the signals in Rule 28" is a display-compliance fact rather than
@@ -1129,40 +1139,40 @@ named that gap before the class existed.
   CLAUDE.md "Coverage") — settling it is a narrower, separate decision.
 - **Q-35** — 8(f)(iii)'s antecedent is "a vessel, the passage of which is not to
   be impeded" — the *output* of another norm, not a fact. A precedence
-  predicate reads only facts, so entry `8f3` reads the risk-of-collision half
+  predicate reads only facts, so entry `rule:8f_iii` reads the risk-of-collision half
   alone and applies to every pair with risk of collision. Settled by deciding
   whether a norm may read another norm's effect, which is the same question a
-  `conduct` monitor will ask about role and phase.
+  `category:conduct` monitor will ask about role and phase.
 - **Q-36** — Rule 18(a)(iv) and 18(d)(i) are both in force between a sailing
   vessel and a vessel constrained by her draught: the CBD vessel gives way, and
   the sailing vessel must not impede her. Neither overrides the other and the
-  model records both, so one subject holds `stand-on` and `shall-not-impede`
+  model records both, so one subject holds `role:stand-on` and `role:shall-not-impede`
   at once. The test suite pins it as a finding rather than asserting it away.
   Settled by reading 8(f)(ii) against the cases, not by picking a role.
-- **Q-37** — 13(a) is `classification` in ADR 0005 §1 and in the proposal's
+- **Q-37** — 13(a) is `category:classification` in ADR 0005 §1 and in the proposal's
   first-cut table, but it is the one paragraph of Rule 13 that assigns a role
-  and a `classification` entry has nowhere to put one. Entry `13a` is
-  `precedence` here, with 13(b)'s sector test left for the `classification`
+  and a `category:classification` entry has nowhere to put one. Entry `rule:13a` is
+  `category:precedence` here, with 13(b)'s sector test left for the `category:classification`
   entry that would set the `hist:was_overtaking` latch. Settled with the rest
   of `Q-14`, paragraph by paragraph.
 
   **Closed in pencil 2026-09-04 (PR #26).** 13(b) is now written, as *two*
-  `classification` entries rather than one — `13b-overtaking` and
-  `13b-overtaken` — because the encounter type belongs to the pair and reading
-  aspect alone classified the overtaken vessel's side of the same encounter as
-  a crossing. 13(a) stays `precedence`, and its predicate now carries both
+  `category:classification` entries rather than one — one per subject — because the
+  encounter type belongs to the pair and reading aspect alone classified the
+  overtaken vessel's side of the same encounter as a crossing. 13(a) stays `category:precedence`, and its predicate now carries both
   halves of "any vessel overtaking any other": the 13(b) sector and the 13(d)
   latch, as an `any_of`, which closes the gap the entry recorded. 13(d) is a
-  third `classification` entry, reading history and no geometry at all. The
+  third `category:classification` entry, reading history and no geometry at all. The
   split confirms the thing ADR 0005 §1 was really defending — one category per
-  paragraph — and costs one paragraph two entries, which the entry-id suffix
-  scheme was already built for.
+  paragraph. **Reversed in part, 2026-09-16:** ADR 0015 as rewritten makes
+  13(b) one symmetric entry, `rule:13b`, reading the same sector object on
+  either subject under `any_of`. 13(a) staying `category:precedence` is untouched.
 - **Q-38** — 9(d), 18(d)(ii), 18(e), 18(f)(ii), 1(a)–(e) and 20(b)–(c) are
   recorded in `known_omissions` rather than modelled: 9(d) needs the channel's
   axis, 18(e) needs a fact for being a seaplane, 20(b)–(c) need time of day,
   and 1(a)–(e) are addressed to an authority rather than to a vessel. Settled
   one at a time as the facts they need land; none blocks the rest of Part B.
-- **Q-39** — Rule 4's `scope` entry has an empty `when`, because "any condition
+- **Q-39** — Rule 4's `category:scope` entry has an empty `when`, because "any condition
   of visibility" is the absence of a condition. That makes it unfalsifiable —
   `REQ-VERIFY-3`'s "excluded by at least one fixture" half cannot be satisfied
   and the test exempts it explicitly. Settled by deciding whether an ungated
@@ -1171,19 +1181,19 @@ named that gap before the class existed.
 
 ### From the classification norms (PR #26)
 
-Rules 7(d), 12, 13(b)–(d), 14 and 15 are the first `classification` entries and
-the second family of `precedence` ones. All pencil. What the model expressed is
+Rules 7(d), 12, 13(b)–(d), 14 and 15 are the first `category:classification` entries and
+the second family of `category:precedence` ones. All pencil. What the model expressed is
 written up in `docs/identifiers.md` §"Effects"; what it could not is here.
 
-- **Q-40** — **Rule 12 is `precedence`, not `classification`.** ADR 0005 §1 and
-  the proposal's table both file it under `classification`; it produces a role
+- **Q-40** — **Rule 12 is `category:precedence`, not `category:classification`.** ADR 0005 §1 and
+  the proposal's table both file it under `category:classification`; it produces a role
   — "one of them shall keep out of the way of the other" — and a
   classification effect has nowhere to put one, which is `Q-37`'s argument
   applied a second time. Two sailing vessels are still in a head-on, a crossing
   or an overtaking; Rule 12 says which of them gives way, not what kind of
-  meeting it is. 12(b) is a `definition` and is the cite on `kin:wind_side`
+  meeting it is. 12(b) is a `category:definition` and is the cite on `kin:wind_side`
   rather than an entry. The second half of the question is narrower and worse:
-  12(a) says "two sailing vessels", which is 3(c), but entries `12a1`–`12a3`
+  12(a) says "two sailing vessels", which is 3(c), but entries the three Rule 12 entries
   read `rule18_class:sail` instead, so a vessel engaged in fishing under sail
   falls out of Rule 12 — because letting her in would have given her a give-way
   duty under 12(a) and a stand-on role under 18(b)(iii) with no override
@@ -1203,7 +1213,7 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   it: Rule 18's chapeau excepts Rules 9, 10 and 13 and no others, so every
   Rule 18 norm that can be in force between two sailing vessels — 18(b)(i)–(iii)
   from the ordinary sailing vessel's side, 18(c)(i)–(ii) from the fishing
-  vessel's — carries `rel:overrides` against `12a1`–`12a3`. 13(a), being
+  vessel's — carries `rel:overrides` against the three Rule 12 entries. 13(a), being
   "notwithstanding" the whole of Sections I and II, overrides them too, which
   it had to: two sailing vessels in an overtaking held 13(a)'s and 12(a)(ii)'s
   roles at once and nothing had noticed. Two fixtures and a sweep over sailing
@@ -1217,21 +1227,21 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
 
   **Decided in pencil 2026-09-05 (PR #46): Rule 15 reads 3(b), and Rule 18
   overrides it too.** The same question answered the other way for Rule 15.
-  `15a-give-way` kept the four Rule 18 ranks — NUC, RAM, fishing and WIG —
+  `rule:15a:keep_out_of_the_way` kept the four Rule 18 ranks — NUC, RAM, fishing and WIG —
   out of Rule 15 by negating them on both subjects in its own predicate; the
   negation is gone, both subjects gate on `fact:propulsion: propulsion:power`
-  which is 3(b), and `18a1`–`18a3`, `18c1`–`18c2` and `18f1` carry
+  which is 3(b), and the 18(a)(i)–(iii) entries, the two 18(c) entries and `rule:18f_i` carry
   `rel:overrides` against it. The gate was not merely the relation said in
   the wrong place. It produced the right roles wherever Rule 18 speaks and
   *no* role at all where Rule 18 is silent: two vessels engaged in fishing
   under power, and a vessel not under command crossing one restricted in her
   ability to manoeuvre under power, are pairs Rule 18 does not order, and
   neither vessel took a helm role from any entry. Both are fixtures now, and
-  both failed on the data before the change — `15a-crossing` classified the
+  both failed on the data before the change — `rule:15a:crossing` classified the
   encounter and nothing assigned a role. What it leaves is Rule 12's residue
   again: on those unordered pairs Rule 15 lays a give-way duty on a vessel
   that may be unable to discharge it, which is Rule 2's region and is
-  recorded, not gated. `13a` needs no override against `15a-give-way` — the
+  recorded, not gated. `rule:13a` needs no override against `rule:15a:keep_out_of_the_way` — the
   entry excludes every overtaking by the `hist:was_overtaking` latch and by
   13(b)'s sector — and a test pins that absence so it stays a reason rather
   than an oversight. The hand-list of six is asserted complete by a derived
@@ -1245,7 +1255,7 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   which is still how the fixtures are written and is what makes these six
   overrides observable rather than invisible.
 
-  The category half — Rule 12 as `precedence` — is unchanged and stays with
+  The category half — Rule 12 as `category:precedence` — is unchanged and stays with
   `Q-14`.
 - **Q-41** — **13(c) and 14(c) invert the absent-fact rule.** "When a vessel is
   in any doubt as to whether she is overtaking, she shall assume that this is
@@ -1272,7 +1282,7 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   judgement. Settled by deciding whether the vocabulary gains one — `Q-31`'s
   neighbour, not its duplicate.
 - **Q-43** — **The partition needs history to be present, and says nothing when
-  it is absent.** `14b` and `15a-crossing` are gated on `hist:was_overtaking`
+  it is absent.** `rule:14b` and `rule:15a:crossing` are gated on `hist:was_overtaking`
   being `false` on both subjects, which is 13(d)'s requirement and the only way
   the three encounter types stay disjoint once the latch is set. Because absent
   is absent, a situation that omits the fact is classified as *no encounter at
@@ -1306,27 +1316,26 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   the same question `Q-39` asks about an ungated norm, from the other end.
 
   **Decided in pencil 2026-09-05 (PR #36): the head-on classification cites
-  14(b), and 14(a) is `conduct`.** The question assumed 14(b) produced no
+  14(b), and 14(a) is `category:conduct`.** The question assumed 14(b) produced no
   effect of its own. It produces the only effect the entry has: "such a
   situation shall be deemed to exist when…" is the deeming test, and
-  `{"encounter": "head-on"}` is what a deeming test yields — exactly as
-  `13b-overtaking` and `13b-overtaken` cite 13(b), the deeming paragraph,
+  `{"encounter": "encounter:head-on"}` is what a deeming test yields — exactly as
+  `rule:13b` cites 13(b), the deeming paragraph,
   and not 13(a). 14(a) states the situation in words ("reciprocal or nearly
   reciprocal courses") and imposes the duty ("each shall alter her course to
-  starboard"); the duty is `conduct`, and the words are what 14(b) makes
-  checkable. So the entry is `14b`, cites 14(b), and reads nothing 14(b) does
+  starboard"); the duty is `category:conduct`, and the words are what 14(b) makes
+  checkable. So the entry is `rule:14b`, cites 14(b), and reads nothing 14(b) does
   not fix; 14(a) joins `known_omissions` as conduct beside 18(d)(ii), and
-  `14a` is retired in `retired_entry_ids` and, because v0.1.3 shipped it,
-  recorded in `data/deprecated-identifiers.json` with `14b` as its
-  replacement — the registry's first record (REQ-MODEL-11). The
+  the `14a` id it displaced is gone with the rest of the citation-derived ids
+  and leaves no record behind it (ADR 0015). The
   general question — whether a paragraph with no effect of its own gets an
   entry — is `Q-39`'s and is untouched; this paragraph turned out not to be an
   instance of it.
 - **Q-46** — **"Coming up with" is a comparison of two facts.** 13(b) deems a
   vessel to be overtaking when *coming up with* another from more than 22.5°
-  abaft her beam. That is `own:kin:sog_kn` against `other:kin:sog_kn`, and the
+  abaft her beam. That is `self:kin:sog_kn` against `other:kin:sog_kn`, and the
   predicate language compares a fact to a constant and never one fact to
-  another — the same wall `12a2` hits on "both have the wind on the same side",
+  another — the same wall `rule:12a_ii` hits on "both have the wind on the same side",
   which it gets over only because that comparison has two values to enumerate
   and this one has infinitely many. `pair:geo:tcpa_s > 0` stands in: the pair
   is closing, and closing from abaft the beam is coming up. It excludes the
@@ -1338,30 +1347,30 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
 - **Q-47** — **13(d)'s latch never clears.** The paragraph runs "until she is
   finally past and clear", nothing in the fact vocabulary carries that, and so
   in this model `hist:was_overtaking` is set by a consumer and cleared by a
-  consumer while entry `13d` classifies an overtaking for as long as it stands.
+  consumer while entry `rule:13d` classifies an overtaking for as long as it stands.
   Not approximated with a range or a bearing: past and clear is a seamanship
   judgement of the same kind as risk of collision, and a threshold for it would
   be a number invented rather than declared. Settled by whatever settles the
-  `conduct` monitors, which are the things that watch a duty end rather than
+  `category:conduct` monitors, which are the things that watch a duty end rather than
   begin.
 
   **Ruled 2026-09-08:** while one vessel holds the latch, 13(a)'s sector
   test is suppressed on the other, newly-gaining vessel — once overtaking,
   always overtaking, per 13(d)'s own text, so a geometry test that would
   newly name a second give-way vessel must not fire while the first still
-  holds the role by history alone. `13a`'s sector branch now also reads
+  holds the role by history alone. `rule:13a`'s sector branch now also reads
   `other:hist:was_overtaking: false`; the closing fixture in
   `fixtures/situation-fixtures.json` is the case this closes — a vessel
   drops back onto the latch-holder's own stern, and only the latch-holder
   gives way.
 - **Q-48** — **Nothing checks that a situation is geometrically possible.**
-  `own:geo:rel_bearing_deg`, `other:geo:rel_bearing_deg`, the two
+  `self:geo:rel_bearing_deg`, `other:geo:rel_bearing_deg`, the two
   `kin:heading_deg` and the two `kin:sog_kn` are six facts related by two
   equations, and the situation record enforces neither. A consumer — or a
   fixture — can state a pair of bearings that no two headings produce, and the
   entries will classify it without complaint. It bites in one visible place:
   where both vessels have the other on the starboard side, which cannot happen
-  on a collision course, `15a-give-way` applies to both of them and the "never
+  on a collision course, `rule:15a:keep_out_of_the_way` applies to both of them and the "never
   both give-way" property fails. The fixtures added here are built from a
   heading and a bearing so that they are consistent by construction, and the
   file says so; the model is not. Settled by deciding whether the record gains
@@ -1372,7 +1381,7 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   **Decided in pencil 2026-09-05: the record gains a consistency check,
   declared in data and enforced in the suite.** `data/facts.json` declares the
   equations under `situation.geometry.consistency` — the two relative bearings
-  are two readings of one line of sight (`own + own heading + 180 ≡ aspect +
+  are two readings of one line of sight (`self + self heading + 180 ≡ aspect +
   other heading`), positions reproduce range and both bearings, and the two
   headings and speeds reproduce CPA, TCPA and bearing rate — with tolerances,
   and `REQ-VERIFY-8` requires the suite to apply them. A quantity a record does
@@ -1384,12 +1393,12 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   and speeds. Two cases could not keep their story: the R1 head-on had both
   vessels with the other to starboard, which no speeds make a steady bearing,
   and is recast as one; the 13(d) latch case is 400 m abeam with the CPA
-  already past, and lost `7d1`. The partition sweep now constructs positions
+  already past, and lost `rule:7d_i`. The partition sweep now constructs positions
   and headings for every bearing pair and is consistent at every point. The
   "never both give-way" property is asserted over a sweep of steady-bearing
   geometries — every relative bearing, several speed pairs, both intercept
   solutions — where it is a theorem rather than an observation:
-  `u·sin(own bearing) = −v·sin(aspect)`, so the two bearings lie on opposite
+  `u·sin(self bearing) = −v·sin(aspect)`, so the two bearings lie on opposite
   sides and 15(a) can name only one vessel. The both-starboard counterexample
   is pinned as a record the check rejects. What is *not* settled, and is
   pinned too: the theorem is exact only at a bearing rate of zero, and
@@ -1401,12 +1410,12 @@ written up in `docs/identifiers.md` §"Effects"; what it could not is here.
   the relative quantities as derived facts stays open in the block's
   `settled_by`.
 
-- **Q-49** — **Must `13d`'s effect cross the Section II/III boundary for Rule 19(d)(i) to be expressible?**
-  - *broad* — drop `13d`'s `pair:geo:in_sight` gate so `encounter: overtaking` is visible in Section III; breaks the scope invariant.
-  - *narrow* — `13d` stays gated; a 19(d)(i) entry reads `own:hist:was_overtaking`/`other:hist:was_overtaking` directly, as `14b` and `15a-crossing` already do.
+- **Q-49** — **Must `rule:13d`'s effect cross the Section II/III boundary for Rule 19(d)(i) to be expressible?**
+  - *broad* — drop `rule:13d`'s `pair:geo:in_sight` gate so `encounter: overtaking` is visible in Section III; breaks the scope invariant.
+  - *narrow* — `rule:13d` stays gated; a 19(d)(i) entry reads `self:hist:was_overtaking`/`other:hist:was_overtaking` directly, as `rule:14b` and `rule:15a:crossing` already do.
   - 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; 13d does not fire`, `test/data.test.mjs`).
+    (`Q-49: hist:was_overtaking resolves out of sight; rule:13d does not fire`, `test/data.test.mjs`).
 
 ### From the Part B invariants (P4.1)
 
@@ -1419,8 +1428,8 @@ nothing is blocked while open.
   *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
-  risk of collision; 14 and 15 are emphasis. Default **wide**: `13a`, `13b-*`,
-  `13d` and every Rule 18 entry read `in_sight` only. No recommendation.
+  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.
 - **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
@@ -1428,7 +1437,7 @@ nothing is blocked while open.
   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
+  (`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.
@@ -1438,8 +1447,8 @@ nothing is blocked while open.
   other Section II classification attaches. Both preserve the duty; they differ
   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"
+  default: `rule:13d` yields `encounter: overtaking` from history alone, `rule:14b` and
+  `rule: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.
@@ -1468,7 +1477,7 @@ nothing is blocked while open.
   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.
   *Hole:* represent it; a fact for "in or near restricted visibility" is owed.
-  *Closed:* treat not-in-sight as Section III. Default **closed**: `19a` drops
+  *Closed:* treat not-in-sight as Section III. Default **closed**: `rule:19a` drops
   the second conjunct, recorded as a `gap`. Recommend **hole**: the default is
   safe for a switching consumer and unsafe for a traceability claim.
 - **Q-57** — **The baseline for "keep her course and speed"?** 17(a)(i) fixes