rttp 0.1.0__tar.gz

rttp-0.1.0/CHANGELOG.md

@@ -0,0 +1,122 @@
+# Changelog — `rttp` (Python)
+
+All notable changes to the `rttp` package. Format follows
+[Keep a Changelog](https://keepachangelog.com/); versioning is
+[Semantic Versioning](https://semver.org/).
+
+---
+
+## [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
+  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
+    that only understand the original layout remain conformant
+  * `build()` · `build_for_uri()` · `parse()` · `verify()` · `to_hex()` /
+    `from_hex()`
+  * 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)
+  * 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
+    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
+  `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
+    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()`
+  * 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
+  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
+  * 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
+  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`,
+  `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`.
+
+### 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.
+* 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.
+
+### Known gaps
+
+Tracked in `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md` §8 and §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
+  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
+  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
+  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
+  classifies every forward case explicitly:
+  * `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
+    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.
+  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-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "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.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "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 2013-2019 Nikolay Kim and Andrew Svetlov
+
+   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.

rttp-0.1.0/MANIFEST.in

@@ -0,0 +1,20 @@
+# The source distribution is the artifact that matches this project's claim:
+# a protocol reference an air-gapped reviewer can read end to end. So it carries
+# the documents, not just the code.
+include README.md
+include CHANGELOG.md
+include LICENSE
+include pyproject.toml
+
+# The published conformance vectors are package data (see pyproject.toml), so the
+# self-test works offline from an installed distribution.
+include src/rttp/vectors/*.json
+
+# Build and cache noise.
+global-exclude *.py[cod]
+global-exclude __pycache__/*
+prune src/rttp.egg-info
+prune .venv
+prune .venv-clean
+prune dist
+prune build

rttp-0.1.0/PKG-INFO

@@ -0,0 +1,234 @@
+Metadata-Version: 2.4
+Name: rttp
+Version: 0.1.0
+Summary: RTTP reference implementation: PulseHeader128 framing, rttp:// addressing, and self-certifying Ed25519 seals (RFC-002 §4.1 / §10 / §11).
+Author: RTTP Working Group
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://rttp.com/
+Project-URL: Specification, https://rttp.com/RFC-002/
+Keywords: rttp,protocol,ai-agents,intent-addressing,uri-scheme,ed25519,conformance
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Internet
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: ed25519
+Requires-Dist: cryptography>=41; extra == "ed25519"
+Provides-Extra: dev
+Requires-Dist: build>=1.0; extra == "dev"
+Requires-Dist: twine>=4.0; extra == "dev"
+Dynamic: license-file
+
+# rttp
+
+**Reference implementation of RTTP (Resonant Time Transfer Protocol): the
+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
+
+---
+
+## Verify it in one command — no trust required
+
+```console
+$ pip install rttp
+$ python -m rttp.selftest
+rttp 0.1.0 self-test
+python 3.14.2 on win32
+...
+[PASS] all 53 checks passed
+```
+
+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,
+  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
+  outside the standard library.
+
+Offline. No account. No network. `[PASS]` or it is not.
+
+---
+
+## Install
+
+```console
+pip install rttp              # core: zero dependencies, standard library only
+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
+air-gapped reviewer should be able to check the frames.
+
+---
+
+## What is in the box
+
+| 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.aid` | Autonomous Identity derivation | RFC-001 |
+
+Plus `rttp.vectors` — the published conformance vectors, shipped inside the wheel
+so the self-test works from an installed package with no repository checkout.
+
+---
+
+## Quickstart
+
+### Address an intent
+
+```python
+from rttp import rttp_uri
+
+parsed = rttp_uri.parse("rttp://brain.epoekie.aicent/verify")
+parsed["authority"]          # 'brain.epoekie.aicent'
+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
+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
+difference, it is a different string.
+
+### Build a frame from a URI
+
+```python
+from rttp import pulse_header, rttp_uri
+
+parsed = rttp_uri.parse("rttp://brain.epoekie.aicent/verify")
+raw = pulse_header.build_for_uri(
+    sequence_id=1, ttl=255, priority=1,
+    uri=parsed["canonical_uri"],
+    aid_origin=bytes.fromhex("..."),   # originator AID, 32 bytes
+)
+len(raw)                          # 128
+pulse_header.verify(raw)["action"]  # 'verify'
+```
+
+`build_for_uri` performs the mapping RFC-002 §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
+zero, and `VERSION_ID` stays 130.
+
+### Seal with your own identity
+
+```python
+from rttp import seal_asym
+
+keypair = seal_asym.generate_keypair()      # nothing is issued to you
+print(keypair["aid_hex"])                   # = SHA-256(public key): your identity
+
+envelope = seal_asym.seal({"intent": "verify", "task_id": "t-1"}, keypair)
+
+ok, reason, aid = seal_asym.verify_envelope(envelope)
+# ok=True, signer identity recovered from the packet itself
+```
+
+The verifier needs **only the envelope**. There is no key directory, no
+credentials to obtain, and no operator who could refuse to issue them.
+
+---
+
+## Two profiles, and when each applies
+
+| | **Managed** — `seal` | **Sovereign** — `seal_asym` |
+|:---|:---|:---|
+| Primitive | HMAC-SHA256 | Ed25519 |
+| Key material | pre-shared table | self-generated |
+| Identity | a role name | `AID = SHA-256(public key)` |
+| Verifier needs | the same key table | only the envelope |
+| 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
+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.
+
+A protocol that invites third parties needs the sovereign profile. That is not a
+preference; it is the difference between a private system and a public one.
+
+---
+
+## 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. |
+
+**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
+concerns are specified separately.
+
+Unknown revisions, algorithms and malformed input **fail closed** everywhere.
+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
+two implementations either agree byte for byte or they do not.
+
+The vector set is the intended deliverable for third-party certification: pass it
+and you interoperate; fail it and you know exactly which byte is wrong, without
+needing to trust the authors.
+
+---
+
+## Naming
+
+| Ecosystem | Name | Status |
+|:---|:---|:---|
+| crates.io | `rttp` | held by this project |
+| PyPI | `rttp` | this package |
+| npm | `@aicent/*` | the unscoped `rttp` name on npm is held by an unrelated, unmaintained 2017 REST helper, and the `rttp` scope cannot be claimed at all — a personal account already holds that name — so the JavaScript side is published under the organization this project controls |
+
+---
+
+## Specification status
+
+* **`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
+  `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
+  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
+  has no standalone specification.
+
+Where this package and a specification disagree, **the specification wins and the
+package is wrong.** Please report it.
+
+---
+
+## License
+
+Apache-2.0. See `LICENSE`.