feat: rewrite docs

spec/08-fidelity.md

@@ -69,6 +69,7 @@ Self-hosted deployments sign with team keys or a private Sigstore deployment; th
 
 A receipt's items are `["node", id, node_hash]` for each listed node, in order, followed by its `records`.
 The root follows RFC 6962: a leaf hash is SHA-256 of the byte 0x00 and the item's canonical JSON; an interior hash is SHA-256 of 0x01 and the two child hashes; a list of *n* > 1 items splits after the largest power of two less than *n*.
+RFC 6962 has since been replaced by RFC 9162, which defines the same tree.
 A root over one item is that item's leaf hash; a receipt with no items is invalid.
 The tree allows a proof that one node was covered without revealing the others; `merkle.jsonl` gives roots for one to seven items.
 
@@ -91,7 +92,7 @@ It is valid when its signature verifies and its signer is the revoked receipt's
 
 The roster, `scienting-roster/1`, lists the keys that may sign: each with an `id`, a `person`, a `scheme`, its `public` key (Base64 for Ed25519), its `purposes` (`sign`, `spot-check`, `export`), `registered_at` and `revoked_at`.
 A package MAY carry the roster its receipts need as `roster.json`, so its receipts verify without the store.
-The roster is meant to be the same one Lode verifies; see the [rationale](../docs/rationale.md#limits-worth-knowing).
+The roster is meant to be the one a store verifies against; see the [rationale](../docs/rationale.md#known-limits).
 
 ## 8.8 Spot-checks
 
@@ -118,7 +119,7 @@ A QA report, `scienting-qa-report/1`, states for each reviewer who signed a deli
 
 ## 8.10 Targeted F3
 
-The target set of a document is every node that a Lode extract, a dataset value, a confirmed `claim-link`, a draft quotation or a pinned citation anchors, plus every display equation, plus every sentence with a digit in a `text` or `math` run.
+The target set of a document is every node that an extract, a dataset value, a confirmed `claim-link`, a draft quotation or a pinned citation anchors, plus every display equation, plus every sentence with a digit in a `text` or `math` run.
 Digits in `cite`, `xref` and `fnmark` runs do not count.
 A project sets the digit rule to `all`, `anchored-sections` (only sentences in a section that holds an anchored node) or `none`.
 Neighbors shown for context are not in the set, and nothing new comes to rest on a node below F3 without the node joining the set.