rttp 1.2.6__tar.gz → 1.2.7__tar.gz

{rttp-1.2.6 → rttp-1.2.7}/CHANGELOG.md

@@ -1,4 +1,4 @@
-# Changelog — `rttp` (Python)
+# Changelog -- `rttp` (Python)
 
 All notable changes to the `rttp` package. Format follows
 [Keep a Changelog](https://keepachangelog.com/); versioning is
@@ -6,11 +6,40 @@ All notable changes to the `rttp` package. Format follows
 
 ---
 
-## [1.2.6] — 2026-09-19
+## [1.2.7] -- 2026-09-21
 
-**Version alignment — no code change.** Every module, byte layout and
+**Conformance surface grown; wire format untouched.** The shipped
+`rttp/vectors/rttp-conformance-v1.2.6.json` is now 13,460 bytes
+(`sha256 4b743e63...`) and the self-test replays every added case: **83 checks**
+in full, and **80 passed with 3 skipped** on a zero-dependency install -- a check
+that cannot be performed is reported as skipped, never as passed.
+
+### Added
+
+* **Nine fail-closed frame cases, one positive frame.** Each of the nine frames
+  must be rejected; the positive frame must be accepted with an empty action.
+* **The published Ed25519 envelope vector**, replayed three ways: the canonical
+  signing input byte for byte, `AID == SHA-256(public key)`, and the signature
+  itself (the third one skips without the optional primitive).
+
+### Changed
+
+* **Skipped checks are now counted and printed**, so a default install can no
+  longer look like a full pass.
+* Per-section counts are reported: 38 conformance, 16 envelope rules, 22 envelope
+  flow, 2 RFC 8032, 5 zero-dependency.
+
+### Note
+
+* PyPI and npm carry `1.2.7`; crates.io carries the same code as the pre-release
+  `1.2.8-alpha`. The registry version strings differ by publishing policy, not by
+  code -- the vectors and their `sha256` are identical everywhere.
+
+## [1.2.6] -- 2026-09-19
+
+**Version alignment -- no code change.** Every module, byte layout and
 conformance vector is identical to 0.1.2, and the self-test still reports the
-same 53 checks. Only the version string and the maturity classifier change.
+the same 53 checks (full set, i.e. with the optional Ed25519 backend). Only the version string and the maturity classifier change.
 
 ### Changed
 
@@ -20,23 +49,23 @@ same 53 checks. Only the version string and the maturity classifier change.
   The old `0.1.x` line was a package-maturity number that corresponded to
   nothing in the specification, and it made the same package look like two
   different releases on two registries.
-* **`Development Status` classifier: `3 - Alpha` → `4 - Beta`.** A
+* **`Development Status` classifier: `3 - Alpha` -> `4 - Beta`.** A
   non-pre-release version must not ship with an "Alpha" classifier; leaving
   the two in conflict invites the question "which one is true?".
 * Install command note: on crates.io every published version of this crate is
   a pre-release, so Cargo will not select it from a plain `rttp` requirement.
   Write `cargo add rttp@1.2.6-alpha` (or pin `rttp = "1.2.6-alpha"`).
 
-## [0.1.2] — 2026-09-18
+## [0.1.2] -- 2026-09-18
 
-**Metadata correction — no code change.** Every module, byte layout and
+**Metadata correction -- no code change.** Every module, byte layout and
 conformance vector is identical to 0.1.1, and the self-test still reports the
-same 53 checks.
+the same 53 checks (full set, i.e. with the optional Ed25519 backend).
 
 ### Fixed
 
 * **The distribution identity now matches the IANA registration.** The package
-  was authored as `RTTP Working Group` — a name that appears in no filing. The
+  was authored as `RTTP Working Group` -- a name that appears in no filing. The
   `rttp` URI-scheme registration on file with IANA (ticket `[IANA #1459939]`)
   names **`RTTP.COM Organization`** as the `Author/Change controller`, and every
   other public surface uses that same name. Both package manifests now say it
@@ -44,19 +73,19 @@ same 53 checks.
 
   | Field | Before | After |
   |:---|:---|:---|
-  | `pyproject.toml` → `authors` (PyPI) | `RTTP Working Group` | **`RTTP.COM Organization`** |
-  | `package.json` → `author` (npm) | `RTTP Working Group` | **`RTTP.COM Organization`** |
+  | `pyproject.toml` -> `authors` (PyPI) | `RTTP Working Group` | **`RTTP.COM Organization`** |
+  | `package.json` -> `author` (npm) | `RTTP Working Group` | **`RTTP.COM Organization`** |
 
   Package metadata cannot be edited after publication, so 0.1.0 and 0.1.1 keep
   the old string inside their own metadata; this is the version that carries the
   correction. Project pages display the latest version, so the visible author
   name becomes correct once this release is out.
 
-## [0.1.1] — 2026-09-18
+## [0.1.1] -- 2026-09-18
 
-**Documentation only — no code change.** Every module, byte layout and
+**Documentation only -- no code change.** Every module, byte layout and
 conformance vector is identical to 0.1.0, and the self-test still reports the
-same 53 checks.
+the same 53 checks (full set, i.e. with the optional Ed25519 backend).
 
 ### Fixed
 
@@ -64,7 +93,7 @@ same 53 checks.
   below said the JavaScript side "will publish under the `@rttp` scope". That
   scope **cannot be created at all**: npm already has a personal account named
   `rttp`, and an organization name may not collide with a user name. The
-  JavaScript side is published as **`@aicent/rttp`** — this project's own
+  JavaScript side is published as **`@aicent/rttp`** -- this project's own
   organization, with the package name itself still just `rttp`.
 * **README distribution table** now names the npm package exactly
   (`@aicent/rttp`), and gives `pip install rttp` for this package, matching the
@@ -74,74 +103,74 @@ same 53 checks.
 
 | Registry | Name | State |
 |:---|:---|:---|
-| PyPI | `rttp` | this package — `pip install rttp` |
-| npm | `@aicent/rttp` | **published 0.1.1** — 2026-09-18 |
+| PyPI | `rttp` | this package -- `pip install rttp` |
+| npm | `@aicent/rttp` | **published 0.1.1** -- 2026-09-18 |
 | crates.io | `rttp` | held by this project |
 
-## [0.1.0] — 2026-09-17
+## [0.1.0] -- 2026-09-17
 
 First release. Scope is deliberately narrow: **framing, addressing and sealing**,
 with zero dependencies and no transport.
 
 ### Added
 
-* **`rttp.pulse_header`** — `PulseHeader128` codec for the 128-byte
-  hardware-aligned frame header (RFC-002 §4.1), including the v1.2.6 extension
+* **`rttp.pulse_header`** -- `PulseHeader128` codec for the 128-byte
+  hardware-aligned frame header (RFC-002 sec. 4.1), including the v1.2.6 extension
   block:
-  * `SPEC_REV` `0x66` · `FLAGS` `0x67` · `ACTION_LEN` `0x68` · `ACTION` `0x69`(16B)
-    · `RESERVED` `0x79`(7B)
-  * bytes `0x00`–`0x65` are **not touched**, `VERSION_ID` stays 130 — readers
+  * `SPEC_REV` `0x66` - `FLAGS` `0x67` - `ACTION_LEN` `0x68` - `ACTION` `0x69`(16B)
+    - `RESERVED` `0x79`(7B)
+  * bytes `0x00`-`0x65` are **not touched**, `VERSION_ID` stays 130 -- readers
     that only understand the original layout remain conformant
-  * `build()` · `build_for_uri()` · `parse()` · `verify()` · `to_hex()` /
+  * `build()` - `build_for_uri()` - `parse()` - `verify()` - `to_hex()` /
     `from_hex()`
-  * strict verification (R1–R7): unknown `SPEC_REV` rejected, `SPEC_REV=0` with a
+  * strict verification (R1-R7): unknown `SPEC_REV` rejected, `SPEC_REV=0` with a
     non-zero block rejected, non-zero `RESERVED` rejected, unknown `FLAGS` bits
     rejected, `ACTION` padding must be zero, `ACTION_LEN` must agree with the
     payload
-* **`rttp.rttp_uri`** — validation, canonicalisation and `ROUTE_SHARD`
-  derivation for `rttp://` URIs (RFC-002 §10.2 / §10.3):
-  * `ROUTE_SHARD = SHA-256(ASCII(canonical_authority))[0:16]` — deterministic,
-    pure computation, **no DNS** (§10.5)
+* **`rttp.rttp_uri`** -- validation, canonicalisation and `ROUTE_SHARD`
+  derivation for `rttp://` URIs (RFC-002 sec. 10.2 / sec. 10.3):
+  * `ROUTE_SHARD = SHA-256(ASCII(canonical_authority))[0:16]` -- deterministic,
+    pure computation, **no DNS** (sec. 10.5)
   * hash-intent (`8lowhex`) and name-intent forms; open-set `action` vocabulary
   * fail-closed rejection of uppercase, `userinfo`, `port`, `query`,
     `fragment`, multi-segment paths, wrong segment counts, leading/trailing `-`,
     whitespace, and non-`rttp` schemes
-  * accepts both `rttp://` and `web+rttp://` — the second as a **tolerance** for
+  * accepts both `rttp://` and `web+rttp://` -- the second as a **tolerance** for
     the browser protocol-handler form, which RFC-002 no longer defines
     (2026-09-17). Not a conformance claim; see "Known gaps" below.
-* **`rttp.seal`** — managed profile: HMAC-SHA256 over a pre-shared key table,
-  bidirectional switch↔agent signing, `ts|nonce` with a 120-second skew window.
-* **`rttp.seal_asym`** — **sovereign profile**: Ed25519 seals with
+* **`rttp.seal`** -- managed profile: HMAC-SHA256 over a pre-shared key table,
+  bidirectional switch<->agent signing, `ts|nonce` with a 120-second skew window.
+* **`rttp.seal_asym`** -- **sovereign profile**: Ed25519 seals with
   `AID = SHA-256(public_key)`.
   * self-certifying: the envelope carries the public key, so a verifier
-    recomputes the identity instead of trusting a claim — **no issuance, no
+    recomputes the identity instead of trusting a claim -- **no issuance, no
     registry, no directory**
   * `ts` and `nonce` are **inside** the signed input, so they cannot be rewritten
     without breaking the signature
   * freshness enforced by default (`|now - ts| <= 120 s`); archival verification
     available explicitly via `check_freshness=False`
-  * lowercase-hex only — a case variant is rejected, not normalised
-  * `generate_keypair()` · `seal()` · `unseal()` · `verify_envelope()` ·
-    `verify_claims()` · `public_bundle()` · `signing_input()`
+  * lowercase-hex only -- a case variant is rejected, not normalised
+  * `generate_keypair()` - `seal()` - `unseal()` - `verify_envelope()` -
+    `verify_claims()` - `public_bundle()` - `signing_input()`
   * requires the `ed25519` extra; without it every call raises `SealError` with
     the install instruction rather than degrading to an unsigned path
-* **`rttp.aid`** — Autonomous Identity derivation (RFC-001), shared by both
+* **`rttp.aid`** -- Autonomous Identity derivation (RFC-001), shared by both
   profiles so an AID means one thing across the stack.
-* **`rttp.selftest`** — `python -m rttp.selftest`, **53 checks**:
-  * 25 conformance vectors (6 positive URIs · 15 rejections · 3 deterministic
-    frames · 1 `SPEC_REV=0` compatibility vector)
-  * RFC 8032 §7.1 TEST 1 / TEST 2, proving the signature backend is standard
-    Ed25519 — so a failure identifies *which* half broke
+* **`rttp.selftest`** -- `python -m rttp.selftest`, **53 checks with the optional Ed25519 backend (29 by default)**:
+  * 25 conformance vectors (6 positive URIs - 15 rejections - 3 deterministic
+    frames - 1 `SPEC_REV=0` compatibility vector)
+  * RFC 8032 sec. 7.1 TEST 1 / TEST 2, proving the signature backend is standard
+    Ed25519 -- so a failure identifies *which* half broke
   * 22 envelope checks, including a 14-case tamper matrix in which every single
     alteration must be rejected, and an explicit replay-window test
   * 4 static-scan checks proving the core modules import nothing outside the
     standard library
   * `--vectors` prints the deterministic envelope vector for the specification;
     `--quiet` prints the summary line only
-* **`rttp/vectors/rttp-conformance-v1.2.6.json`** — the published vectors, shipped
+* **`rttp/vectors/rttp-conformance-v1.2.6.json`** -- the published vectors, shipped
   as package data so the self-test runs from an installed wheel, offline.
 * Console entry point `rttp-selftest`.
-* **`MANIFEST.in`** — the source distribution carries `README.md`,
+* **`MANIFEST.in`** -- the source distribution carries `README.md`,
   `CHANGELOG.md`, `LICENSE`, `pyproject.toml` and the published vectors, and
   excludes virtual environments and build noise. Both the wheel and the sdist
   pass `twine check`.
@@ -149,51 +178,51 @@ with zero dependencies and no transport.
 ### Notes
 
 * **Zero dependencies** in the core, and that is a machine-checked claim rather
-  than a promise — see the static-scan section of the self-test.
+  than a promise -- see the static-scan section of the self-test.
 * The reference implementation evaluates the
   **`iqa`** namespace nowhere: this package is the `rttp` protocol only.
 * ~~Distribution: PyPI `rttp`. The npm name `rttp` is held by an unrelated,
   unmaintained project, so the JavaScript side will publish under the `@rttp`
-  scope.~~ — **corrected 2026-09-18.** PyPI `rttp` is now **published** (0.1.0,
+  scope.~~ -- **corrected 2026-09-18.** PyPI `rttp` is now **published** (0.1.0,
   2026-09-17). The npm name `rttp` is indeed held by an unrelated, unmaintained
-  project — but the **`@rttp` scope cannot be created at all**, because a
+  project -- but the **`@rttp` scope cannot be created at all**, because a
   personal account already holds that name. The JavaScript side is therefore
   published as **`@aicent/rttp`**: this project's own organization, with the
   package name still just `rttp`.
 
 ### Known gaps
 
-Tracked in `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md` §8 and §10. Deliberately listed
+Tracked in `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md` sec. 8 and sec. 10. Deliberately listed
 here so nobody has to discover them:
 
 * No transport and no client. The core encodes, addresses and seals; sending is a
   separate package's job.
 * No revocation, and no key rotation story. Both belong to RFC-003.
-* No replay **cache**: freshness (§3.4) bounds the window, but within it a replayed
+* No replay **cache**: freshness (sec. 3.4) bounds the window, but within it a replayed
   envelope still verifies unless the verifier keeps a short-lived nonce store.
 * No transport-origin binding: the seal proves who signed, not which connection
   delivered it.
 * Rust parity: the published `rttp` crate has no transport layer and no envelope.
   Python and Node are the conforming implementations so far.
-* ~~the browser-registration prefix is accepted because RFC-002 §10.6 requires
-  it…~~ — **superseded 2026-09-17.** That form was removed from both
+* ~~the browser-registration prefix is accepted because RFC-002 sec. 10.6 requires
+  it...~~ -- **superseded 2026-09-17.** That form was removed from both
   specifications and will never be submitted to IANA. `rttp_uri` still accepts it
-  as a **tolerance** — a browser hands the handler that string, and refusing it
-  would break the protocol-handler path — but the specification defines no such
+  as a **tolerance** -- a browser hands the handler that string, and refusing it
+  would break the protocol-handler path -- but the specification defines no such
   form, so the acceptance is **outside the specification** and a conforming
   third-party implementation is not required to reproduce it.
 * ~~**Open, and ours to fix:** the published vectors asserted things the
-  specification no longer said.~~ — **resolved 2026-09-18.** The generator now
+  specification no longer said.~~ -- **resolved 2026-09-18.** The generator now
   classifies every forward case explicitly:
-  * `positive_uris` — each entry carries `tolerance` (boolean) and `note`. The
+  * `positive_uris` -- each entry carries `tolerance` (boolean) and `note`. The
     case whose `uri` carries the browser-registration prefix is `tolerance: true`,
     with its reason recorded: it is accepted only because that is the scheme name
-    under which a handler is registered (RFC-002 §10.6) — never because the
+    under which a handler is registered (RFC-002 sec. 10.6) -- never because the
     specification defines it. It is **not** a conformance claim, and the 25-check
     total is unchanged.
-  * `negative_uris` — the two case-clause citations were corrected from
-    `(RFC-002 §10.2)` to **`§10.3`**, the clause that actually carries the
-    lowercase rule. §10.2 now appears nowhere in the vector set.
+  * `negative_uris` -- the two case-clause citations were corrected from
+    `(RFC-002 sec. 10.2)` to **`sec. 10.3`**, the clause that actually carries the
+    lowercase rule. sec. 10.2 now appears nowhere in the vector set.
   Regenerated (`SPEC/tools/conformance.py --generate`), replayed (`--check`,
   25/25), and mirrored byte-identically into both packages. After the change:
   Python self-test 53/53, Node runner 25/25.

{rttp-1.2.6 → rttp-1.2.7}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: rttp
-Version: 1.2.6
-Summary: RTTP reference implementation: PulseHeader128 framing, rttp:// addressing, and self-certifying Ed25519 seals (RFC-002 §4.1 / §10 / §11).
+Version: 1.2.7
+Summary: RTTP reference implementation: PulseHeader128 framing, rttp:// addressing, and self-certifying Ed25519 seals (RFC-002 sec. 4.1 / sec. 10 / sec. 11).
 Author: RTTP.COM Organization
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://rttp.com/
@@ -31,35 +31,45 @@ Dynamic: license-file
 128-byte `PulseHeader128` frame, `rttp://` intent addressing, and self-certifying
 Ed25519 seals.**
 
-[RFC-002 §4.1](https://rttp.com/RFC-002/) · [§10](https://rttp.com/RFC-002/) · §11 · v1.2.6
+[RFC-002 sec. 4.1](https://rttp.com/RFC-002/) - [sec. 10](https://rttp.com/RFC-002/) - sec. 11 - v1.2.6
 
 ---
 
-## Verify it in one command — no trust required
+## Verify it in one command -- no trust required
 
 ```console
 $ pip install rttp
 $ python -m rttp.selftest
-rttp 1.2.6 self-test
+rttp 1.2.7 self-test
 python 3.14.2 on win32
 ...
-[PASS] all 53 checks passed
+[PASS] all 80 checks passed (3 skipped)     # default install: the Ed25519 checks are skipped
+
+$ pip install rttp[ed25519]
+$ python -m rttp.selftest
+rttp 1.2.7 self-test
+python 3.14.2 on win32
+...
+[PASS] all 83 checks passed                 # with the optional Ed25519 backend
 ```
 
 That is the point of this package. A specification is worth exactly what an
-independent implementation can reproduce from it — so instead of asking you to
-believe a table of numbers, this ships the vectors and replays them locally:
-
-* **25 conformance checks** — `rttp://` parsing, fail-closed rejections, and the
-  URI → `ROUTE_SHARD` → 128-byte frame chain, bit for bit.
-* **2 RFC 8032 checks** — the Ed25519 backend is shown to be *standard* Ed25519,
+independent implementation can reproduce from it -- so instead of asking you to
+believe a table of numbers, this ships the vectors and replays them locally.
+The 83 checks below are the full set, i.e. with the optional Ed25519 backend
+installed; a default install runs 80 checks and skips 3.
+
+* **38 conformance checks** -- `rttp://` parsing, fail-closed rejections, and the
+  URI -> `ROUTE_SHARD` -> 128-byte frame chain, bit for bit.
+* **2 RFC 8032 checks** -- the Ed25519 backend is shown to be *standard* Ed25519,
   not a lookalike, so a failure tells you which half broke.
-* **22 envelope checks** — round-trip, self-certification, freshness, and a
-  14-case tamper matrix where every alteration must be rejected.
-* **4 zero-dependency checks** — a static scan proving the core imports nothing
+* **38 envelope checks** -- 16 rule-layer checks that need no primitive, plus
+  round-trip, self-certification, freshness and a 14-case tamper matrix where
+  every alteration must be rejected.
+* **5 zero-dependency checks** -- a static scan proving the core imports nothing
   outside the standard library.
 
-Offline. No account. No network. `[PASS]` or it is not.
+Offline. No account. No network. `[PASS]` or it is not. Every vector file shipped here is listed in `vectors.manifest.json` with its byte count and SHA-256, produced by a generator rather than typed by hand - recompute the hash yourself if you prefer.
 
 ---
 
@@ -73,7 +83,7 @@ pip install rttp[ed25519]     # + sovereign-profile seals (Ed25519)
 Python 3.9+. No compiled extensions in the core.
 
 The core deliberately has **no dependencies**. A protocol reference that cannot be
-read without resolving a dependency tree is not much of a reference — and an
+read without resolving a dependency tree is not much of a reference -- and an
 air-gapped reviewer should be able to check the frames.
 
 ---
@@ -82,13 +92,13 @@ air-gapped reviewer should be able to check the frames.
 
 | Module | What it does | Authority |
 |:---|:---|:---|
-| `rttp.pulse_header` | `PulseHeader128` codec — build / parse / verify the 128-byte hardware-aligned header, including the v1.2.6 extension block at `0x66`–`0x7F` | RFC-002 §4.1 + `SPEC/RTTP-FRAME-EXT-v1.2.6.md` |
-| `rttp.rttp_uri` | Validate, canonicalise and derive `ROUTE_SHARD` from an `rttp` URI | RFC-002 §10.2 / §10.3 ABNF |
-| `rttp.seal` | **Managed profile** — symmetric HMAC-SHA256 over a pre-shared key table | — |
-| `rttp.seal_asym` | **Sovereign profile** — Ed25519, self-certifying, no issuance and no registry | `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md` (draft) |
+| `rttp.pulse_header` | `PulseHeader128` codec -- build / parse / verify the 128-byte hardware-aligned header, including the v1.2.6 extension block at `0x66`-`0x7F` | RFC-002 sec. 4.1 + `SPEC/RTTP-FRAME-EXT-v1.2.6.md` |
+| `rttp.rttp_uri` | Validate, canonicalise and derive `ROUTE_SHARD` from an `rttp` URI | RFC-002 sec. 10.2 / sec. 10.3 ABNF |
+| `rttp.seal` | **Managed profile** -- symmetric HMAC-SHA256 over a pre-shared key table | -- |
+| `rttp.seal_asym` | **Sovereign profile** -- Ed25519, self-certifying, no issuance and no registry | `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md` (draft) |
 | `rttp.aid` | Autonomous Identity derivation | RFC-001 |
 
-Plus `rttp.vectors` — the published conformance vectors, shipped inside the wheel
+Plus `rttp.vectors` -- the published conformance vectors, shipped inside the wheel
 so the self-test works from an installed package with no repository checkout.
 
 ---
@@ -106,9 +116,9 @@ parsed["action"]             # 'verify'
 parsed["route_shard"].hex()  # 16-byte routing hash, pure computation
 ```
 
-Addressing is **DNS-free** (RFC-002 §10.5): the routing hash is derived from the
+Addressing is **DNS-free** (RFC-002 sec. 10.5): the routing hash is derived from the
 authority by SHA-256, so no registry, resolver or network is involved. Malformed
-input is rejected rather than normalised — a case variant is not a spelling
+input is rejected rather than normalised -- a case variant is not a spelling
 difference, it is a different string.
 
 ### Build a frame from a URI
@@ -126,9 +136,9 @@ len(raw)                          # 128
 pulse_header.verify(raw)["action"]  # 'verify'
 ```
 
-`build_for_uri` performs the mapping RFC-002 §10.4 promises: the URI's authority
+`build_for_uri` performs the mapping RFC-002 sec. 10.4 promises: the URI's authority
 becomes `ROUTE_SHARD`, its path becomes `ACTION`. Readers that only understand
-`0x00`–`0x65` keep working — the extension block occupies bytes that were already
+`0x00`-`0x65` keep working -- the extension block occupies bytes that were already
 zero, and `VERSION_ID` stays 130.
 
 ### Seal with your own identity
@@ -152,7 +162,7 @@ credentials to obtain, and no operator who could refuse to issue them.
 
 ## Two profiles, and when each applies
 
-| | **Managed** — `seal` | **Sovereign** — `seal_asym` |
+| | **Managed** -- `seal` | **Sovereign** -- `seal_asym` |
 |:---|:---|:---|
 | Primitive | HMAC-SHA256 | Ed25519 |
 | Key material | pre-shared table | self-generated |
@@ -161,7 +171,7 @@ credentials to obtain, and no operator who could refuse to issue them.
 | A stranger can participate | no | **yes** |
 | One leaked key | can forge any peer | forges one identity |
 
-Inside a set of symmetric secrets there is no such thing as a stranger — whoever
+Inside a set of symmetric secrets there is no such thing as a stranger -- whoever
 holds the shared key can mint anybody's seal. The managed profile is therefore for
 a closed organism, where a fixed set of roles genuinely do trust each other.
 
@@ -170,19 +180,19 @@ preference; it is the difference between a private system and a public one.
 
 ---
 
-## Scope — what this package is not
+## Scope -- what this package is not
 
 | | |
 |:---|:---|
-| ✅ **Framing** | Real, and specified. |
-| ✅ **Addressing** | Real, and specified. |
-| ✅ **Sealing** | Real, and specified (draft). |
-| ❌ **Transport** | **Not here.** This package encodes, addresses and seals. It does not open sockets, and there is no `send()` — a client and its transport belong to a separate package, so that the codec stays dependency-free and auditable. |
-| ❌ **Routing service** | Not here. `ROUTE_SHARD` is computed locally; delivering a frame to that hash is an operator's job, not the codec's. |
-| ❌ **Confidentiality** | Signing is not encryption. |
+| OK **Framing** | Real, and specified. |
+| OK **Addressing** | Real, and specified. |
+| OK **Sealing** | Real, and specified (draft). |
+| NO **Transport** | **Not here.** This package encodes, addresses and seals. It does not open sockets, and there is no `send()` -- a client and its transport belong to a separate package, so that the codec stays dependency-free and auditable. |
+| NO **Routing service** | Not here. `ROUTE_SHARD` is computed locally; delivering a frame to that hash is an operator's job, not the codec's. |
+| NO **Confidentiality** | Signing is not encryption. |
 
 **The seal is an envelope around the frame, not bytes inside it.** A reader that
-parses only the 128-byte header sees no seal at all — which is why the two
+parses only the 128-byte header sees no seal at all -- which is why the two
 concerns are specified separately.
 
 Unknown revisions, algorithms and malformed input **fail closed** everywhere.
@@ -193,7 +203,7 @@ Nothing in this package is ever accepted because a check could not be performed.
 ## Conformance vectors
 
 `rttp/vectors/rttp-conformance-v1.2.6.json` is generated, not hand-edited. Each
-vector is deterministic: fixed sequence numbers, fixed timestamp, fixed AID — so
+vector is deterministic: fixed sequence numbers, fixed timestamp, fixed AID -- so
 two implementations either agree byte for byte or they do not.
 
 The vector set is the intended deliverable for third-party certification: pass it
@@ -207,21 +217,21 @@ needing to trust the authors.
 | Ecosystem | Name | Status |
 |:---|:---|:---|
 | crates.io | `rttp` | held by this project |
-| PyPI | `rttp` | **this package** — `pip install rttp` |
-| npm | **`@aicent/rttp`** | the unscoped `rttp` name on npm is held by an unrelated, unmaintained 2017 REST helper, and the `rttp` scope cannot be created at all — a personal account already holds that name — so the JavaScript side is published under this project's own organization. The package name itself is still just `rttp` |
+| PyPI | `rttp` | **this package** -- `pip install rttp` |
+| npm | **`@aicent/rttp`** | the unscoped `rttp` name on npm is held by an unrelated, unmaintained 2017 REST helper, and the `rttp` scope cannot be created at all -- a personal account already holds that name -- so the JavaScript side is published under this project's own organization. The package name itself is still just `rttp` |
 
 ---
 
 ## Specification status
 
-* **`rttp` URI scheme** — submitted to IANA under RFC 7595, ticket **#1459939**,
+* **`rttp` URI scheme** -- submitted to IANA under RFC 7595, ticket **#1459939**,
   Provisional (First Come, First Served), **under review**. It is **not yet
-  registered** — as of 2026-09-15 the IANA URI Schemes registry contains no
+  registered** -- as of 2026-09-15 the IANA URI Schemes registry contains no
   `rttp` entry. Please describe it that way.
-* **Frame layout** — RFC-002 §4.1, extended by `SPEC/RTTP-FRAME-EXT-v1.2.6.md`.
-* **Seal envelope** — `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md`, a **draft**: the format
+* **Frame layout** -- RFC-002 sec. 4.1, extended by `SPEC/RTTP-FRAME-EXT-v1.2.6.md`.
+* **Seal envelope** -- `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md`, a **draft**: the format
   is implemented and vector-tested, but it is not yet a numbered RFC-002 section.
-* **Managed profile** — implementation only; it predates the sovereign profile and
+* **Managed profile** -- implementation only; it predates the sovereign profile and
   has no standalone specification.
 
 Where this package and a specification disagree, **the specification wins and the