@aicent/rttp 0.1.0

package/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.

package/README.md

@@ -0,0 +1,238 @@
+# @aicent/rttp
+
+**RTTP for JavaScript: `rttp://` intent addressing, `ROUTE_SHARD` derivation —
+and the published conformance vectors that prove an implementation is right.**
+
+[RFC-002 §10](https://rttp.com/RFC-002/) · v1.2.6 · zero dependencies · no build step
+
+---
+
+## Verify it in one command — no trust required
+
+```console
+$ npx @aicent/rttp
+[PASS] all 25 checks passed (node, independent implementation)
+```
+
+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, the vectors ship inside the package and replay
+locally — offline, no account, no network. `[PASS]` or it is not.
+
+The JavaScript and Python sides **share no code**. They are separate
+implementations of the same published vectors, and they agree byte for byte.
+
+---
+
+## Install
+
+```console
+npm install @aicent/rttp
+```
+
+Node 18+. No dependencies, no build step, no transitive tree to audit: the
+published `src/` is exactly what runs.
+
+---
+
+## Quickstart
+
+```js
+import { parse } from '@aicent/rttp';
+
+const r = parse('rttp://brain.epoekie.aicent/verify');
+
+r.authority       // 'brain.epoekie.aicent'
+r.intent          // 'brain'
+r.pillar          // 'epoekie'
+r.root            // 'aicent'
+r.action          // 'verify'
+r.canonical_uri   // 'rttp://brain.epoekie.aicent/verify'
+r.route_shard_hex // '459e543b73d86005b72ba77d5756e83c'  <- 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. A URI
+either yields a shard or throws — there is no fallback, and no `rttps`.
+
+---
+
+## The one rule that surprises people
+
+**Malformed input is rejected, not normalised.** `rttp://…/VESSEL` and
+`rttp://F3B2A1C4.…/vessel` both throw, because the canonical form is lowercase
+US-ASCII (RFC-002 §10.3) and a case variant is not a spelling difference — it is
+a *different string*. Admitting both would give one address two spellings, which
+is the ambiguity §10.3 exists to remove.
+
+Nothing here is ever accepted because a check could not be performed: this
+package fails closed everywhere.
+
+---
+
+## The address and the prefix are different things
+
+A user agent accepts `navigator.registerProtocolHandler()` only for schemes on its
+own safelisted set, or for a scheme beginning `web+`. So a **web page** must use
+the `web+rttp:` prefix to register a handler (RFC-002 §10.6) — but that prefix
+describes the **client**, never the target.
+
+```js
+parse('web+rttp://logic.zcmk.aicent/pulse').canonical_uri
+// 'rttp://logic.zcmk.aicent/pulse'   <- always the canonical form, either way
+
+parse('web+rttp://logic.zcmk.aicent/pulse').route_shard_hex
+=== parse('rttp://logic.zcmk.aicent/pulse').route_shard_hex
+// true - same authority, same path, same shard
+```
+
+The output `scheme` field tells you which form arrived; everything else is
+identical.
+
+---
+
+## API — main entry
+
+| Export | What it does |
+|:---|:---|
+| `parse(uri)` | Validate, canonicalise, derive. Throws `RttpUriError`. |
+| `parseAndDerive(uri)` | Identical to `parse`; the specification's own wording. |
+| `deriveRouteShard(authority)` | `Uint8Array(16)` = `SHA-256(ASCII(authority))[0:16]`. |
+| `deriveRouteShardHex(authority)` | The same, as 32 lowercase hex characters. |
+| `isValidAction(value)` | §10.2 `action` form test. The verb set is **open**. |
+| `RttpUriError` | The only error type thrown. |
+| `SCHEME`, `BROWSER_HANDLER_SCHEME`, `ROUTE_SHARD_BYTES`, `HASH_INTENT_LEN`, `ACTION_MAX_LEN`, `SPEC_RELEASE` | Constants. |
+
+### Returned fields
+
+Field names are `snake_case` **on purpose**: the published conformance vectors use
+those names, so this output and the Python package's output compare directly —
+field for field, byte for byte.
+
+| Field | Meaning |
+|:---|:---|
+| `scheme` | `rttp` or `web+rttp` — which form arrived |
+| `intent` | 8 lowercase hex digits (32-bit routing hash) or a readable organ token |
+| `intent_is_hash` / `intent_hash32` | Whether it is a hash-intent, and its value |
+| `pillar`, `root` | The other two authority labels |
+| `action` | Empty string when omitted (RFC-002 §10.4 default operation) |
+| `action_omitted` | The same fact as a boolean |
+| `authority` | `<intent>.<pillar>.<root>`, canonical |
+| `canonical_uri` | Always begins `rttp://` |
+| `route_shard` / `route_shard_hex` | The 16-byte routing hash, two ways |
+
+---
+
+## The conformance vectors — `@aicent/rttp/conformance`
+
+```js
+import { loadVectors, runConformance } from '@aicent/rttp/conformance';
+
+const { checked, failures, passed } = runConformance(loadVectors());
+```
+
+Or from the command line:
+
+```console
+npx @aicent/rttp                      # replay the shipped vectors
+npx @aicent/rttp --vectors ./new.json # replay a different vector set
+npx @aicent/rttp --json               # machine-readable output
+```
+
+In CI:
+
+```yaml
+- run: npx @aicent/rttp
+```
+
+| Export | What it does |
+|:---|:---|
+| `runConformance(vectors)` | Replay a vector set → `{ checked, failures, passed }` |
+| `loadVectors(path?)` | Parse a vector set; defaults to the shipped one |
+| `DEFAULT_VECTORS_PATH` | Absolute path of the shipped `vectors.json` |
+| `parseUri(uri)` | The independent RFC-002 §10.2 implementation → `{ authority, action, shardHex }` |
+| `buildFrame(fields)` | The independent 128-byte frame builder → `Buffer` |
+| `ACTION_MAX_LEN` | `16` — the ACTION field's capacity |
+
+`vectors.json` is plain JSON and ships inside the package, also reachable as the
+subpath export `@aicent/rttp/vectors.json`. Any language can read it; that is
+what it is for.
+
+### What the 25 checks are
+
+| Group | Count | What it proves |
+|:---|:---|---:|
+| `positive_uris` | 6 | Accept, canonicalise and derive — including a hash-intent, an omitted action, and the browser-handler prefix |
+| `negative_uris` | 15 | **Reject** — uppercase, userinfo, query, fragment, port, multi-segment path, wrong authority shape, trailing slash, foreign scheme, surrounding whitespace |
+| `frame_vectors` | 3 | URI → `ROUTE_SHARD` → the 128-byte `PulseHeader128`, bit for bit |
+| `compat_vector_spec_rev_0` | 1 | A frame written before the v1.2.6 extension block still verifies |
+
+Each vector is deterministic: fixed sequence numbers, fixed timestamp, fixed AID.
+Two implementations either agree byte for byte or they do not.
+
+### Why the checker lives in this package, and why that is still honest
+
+`src/conformance.mjs` is written from RFC-002 §10.2 alone and **must never import
+`src/rttp-uri.mjs`**. A conformance suite that reuses the code under test only
+proves the code equals itself. The two files share no code, so the rule is
+checkable by reading them.
+
+They ship together for the same reason the Python wheel ships its self-test: so
+that a stranger can verify an installed package **offline, with no repository
+checkout**. A verification step that requires cloning an unrelated repository is
+not a verification step.
+
+`buildFrame` **refuses** an action longer than the field can hold rather than
+truncating it: a silently shortened verb would be a routing decision made by the
+codec, and the codec does not get to make that decision. (§10.2 sets no length
+limit on `action` — a *parser* must accept a long one; a frame builder cannot.)
+
+The vectors are **generated, not written**. `generated_by` in the JSON names the
+generator, and the file says so itself: change the cases in the generator, not the
+JSON. Hand-editing a conformance vector is how a specification quietly starts
+agreeing with its own bugs.
+
+---
+
+## Scope — what this package is not
+
+| | |
+|:---|:---|
+| ✅ **Validation** | Real, and specified (RFC-002 §10.2 / §10.3). |
+| ✅ **Canonicalisation** | Real, and specified. |
+| ✅ **ROUTE_SHARD derivation** | Real, and specified. |
+| ✅ **Conformance vectors + independent replay** | Published and generated. |
+| ❌ **Framing, as a library API** | `buildFrame` is exported from `./conformance`, where it exists to replay frame vectors — it is not offered as a general codec. |
+| ❌ **Transport** | Not here. There is no `send()`. |
+| ❌ **Routing service** | Not here. The shard is computed locally; delivering a frame to that hash is an operator's job. |
+| ❌ **Sealing (§11)** | Separate artifacts. |
+| ❌ **Browsers** | Node only — it uses `node:crypto`. The derivation is trivial to reproduce elsewhere, and the vectors let you prove you did. |
+
+---
+
+## Naming
+
+| Ecosystem | Name | Status |
+|:---|:---|:---|
+| crates.io | `rttp` | held by this project |
+| PyPI | `rttp` | the Python reference implementation |
+| npm | **`@aicent/rttp`** | the bare `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. This package is therefore published under the organization this project controls; the package name itself is still just `rttp`. |
+
+---
+
+## Specification status
+
+* **`rttp` URI scheme** — submitted to IANA under RFC 7595, ticket **#1459939**,
+  Provisional, **under review**. It is **not yet registered** — as of 2026-09-17
+  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`.
+
+Where this package and the specification disagree, **the specification wins and
+this package is wrong.** Please report it.
+
+---
+
+## License
+
+Apache-2.0. See `LICENSE`.

package/bin/rttp.mjs

@@ -0,0 +1,85 @@
+#!/usr/bin/env node
+/**
+ * rttp - replay the RTTP conformance vectors.
+ *
+ *     npx @aicent/rttp
+ *     rttp --vectors ./newer-vectors.json
+ *     rttp --json
+ *
+ * Exit status is 0 only when every check passes: `[PASS]` or it is not.
+ */
+
+import { DEFAULT_VECTORS_PATH, loadVectors, runConformance } from '../src/conformance.mjs';
+
+const USAGE = `rttp - replay the RTTP conformance vectors
+
+Usage:
+  rttp [--vectors <file>] [--json] [--help]
+
+Options:
+  --vectors <file>  replay a different vector set (default: the one shipped
+                    with this package)
+  --json            emit machine-readable results
+  --help            show this message
+
+Exit status: 0 when every check passes, 1 otherwise.
+`;
+
+function parseArgs(argv) {
+  const opts = { vectors: DEFAULT_VECTORS_PATH, json: false, help: false };
+  for (let i = 0; i < argv.length; i += 1) {
+    const arg = argv[i];
+    if (arg === '--help' || arg === '-h') opts.help = true;
+    else if (arg === '--json') opts.json = true;
+    else if (arg === '--vectors') {
+      i += 1;
+      if (argv[i] === undefined) {
+        console.error('rttp: --vectors needs a file path');
+        process.exit(2);
+      }
+      opts.vectors = argv[i];
+    } else {
+      console.error(`rttp: unknown argument ${JSON.stringify(arg)}`);
+      console.error(USAGE);
+      process.exit(2);
+    }
+  }
+  return opts;
+}
+
+const opts = parseArgs(process.argv.slice(2));
+
+if (opts.help) {
+  process.stdout.write(USAGE);
+  process.exit(0);
+}
+
+let vectors;
+try {
+  vectors = loadVectors(opts.vectors);
+} catch (err) {
+  console.error(`rttp: cannot read vectors at ${opts.vectors}`);
+  console.error(`  ${err.message}`);
+  process.exit(2);
+}
+
+const { checked, failures, passed } = runConformance(vectors);
+
+if (opts.json) {
+  process.stdout.write(`${JSON.stringify({
+    passed,
+    checked,
+    failed: failures.length,
+    vectors: opts.vectors,
+    spec: vectors.spec,
+    applies_to: vectors.applies_to,
+    failures,
+  }, null, 2)}\n`);
+} else if (passed) {
+  console.log(`[PASS] all ${checked} checks passed (node, independent implementation)`);
+} else {
+  console.log(`[FAIL] ${failures.length} of ${checked} checks failed (node)`);
+  for (const item of failures) console.log('   -', item);
+}
+
+process.exit(passed ? 0 : 1);

package/package.json

@@ -0,0 +1,54 @@
+{
+  "name": "@aicent/rttp",
+  "version": "0.1.0",
+  "description": "RTTP for JavaScript: rttp:// intent validation, canonicalisation and ROUTE_SHARD derivation (RFC-002 §10), plus the published conformance vectors and an independent replay of them, including the 128-byte frame. Zero dependencies, no build step.",
+  "keywords": [
+    "rttp",
+    "uri",
+    "uri-scheme",
+    "intent-addressing",
+    "route-shard",
+    "frame",
+    "rfc-002",
+    "conformance",
+    "vectors",
+    "protocol"
+  ],
+  "license": "Apache-2.0",
+  "author": "RTTP Working Group",
+  "homepage": "https://rttp.com/",
+  "type": "module",
+  "main": "./src/rttp-uri.mjs",
+  "exports": {
+    ".": {
+      "types": "./src/rttp-uri.d.mts",
+      "default": "./src/rttp-uri.mjs"
+    },
+    "./conformance": {
+      "types": "./src/conformance.d.mts",
+      "default": "./src/conformance.mjs"
+    },
+    "./vectors.json": "./src/vectors.json"
+  },
+  "bin": {
+    "rttp": "bin/rttp.mjs",
+    "rttp-conformance": "bin/rttp.mjs"
+  },
+  "files": [
+    "src",
+    "bin",
+    "README.md",
+    "LICENSE"
+  ],
+  "sideEffects": false,
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "test": "node --test",
+    "prepublishOnly": "node --test"
+  }
+}

package/src/conformance.d.mts

@@ -0,0 +1,108 @@
+/**
+ * Type declarations for @aicent/rttp/conformance.
+ */
+
+/** One URI that a conforming implementation must accept. */
+export interface PositiveUriVector {
+  uri: string;
+  canonical_uri: string;
+  authority: string;
+  intent: string;
+  intent_is_hash: boolean;
+  pillar: string;
+  root: string;
+  action: string;
+  action_omitted: boolean;
+  route_shard_hex: string;
+}
+
+/** One URI that a conforming implementation must reject. */
+export interface NegativeUriVector {
+  uri: string;
+  reason: string;
+}
+
+/** One URI -> 128-byte frame vector. */
+export interface FrameVector {
+  uri: string;
+  sequence_id: number;
+  ttl: number;
+  priority: number;
+  timestamp_ns: number;
+  aid_origin_hex: string;
+  action: string;
+  uri_anchored: boolean;
+  spec_rev: number;
+  route_shard_hex: string;
+  header_hex: string;
+}
+
+/** A frame written with the pre-extension layout (`SPEC_REV = 0`), which readers must still accept. */
+export interface CompatVector {
+  uri: string;
+  spec_rev: number;
+  action: string;
+  action_omitted: boolean;
+  uri_anchored: boolean;
+  expected: string;
+  header_hex: string;
+}
+
+/** The published vector set. Generated - never hand-edited. */
+export interface VectorSet {
+  spec: string;
+  applies_to: string[];
+  generated_by: string;
+  note: string;
+  route_shard_rule: string;
+  frame_size: number;
+  action_max_len: number;
+  positive_uris: PositiveUriVector[];
+  negative_uris: NegativeUriVector[];
+  frame_vectors: FrameVector[];
+  compat_vector_spec_rev_0: CompatVector;
+}
+
+/** Result of one `parseUri` call. */
+export interface ParsedUri {
+  authority: string;
+  action: string;
+  shardHex: string;
+}
+
+/** Input to `buildFrame`. */
+export interface FrameFields {
+  sequenceId: number | string | bigint;
+  ttl: number;
+  priority: number;
+  shardHex: string;
+  aidHex: string;
+  timestampNs: number | string | bigint;
+  action: string;
+  uriAnchored: boolean;
+}
+
+/** Outcome of replaying a vector set. */
+export interface ConformanceResult {
+  checked: number;
+  failures: string[];
+  passed: boolean;
+}
+
+/** Absolute path of the vector set shipped inside this package. */
+export declare const DEFAULT_VECTORS_PATH: string;
+
+/** The ACTION field is 16 bytes. */
+export declare const ACTION_MAX_LEN: 16;
+
+/** Independent implementation of RFC-002 §10.2. Throws `Error`. */
+export declare function parseUri(uri: string): ParsedUri;
+
+/** Independent implementation of the 128-byte frame. Throws `Error`. */
+export declare function buildFrame(fields: FrameFields): Buffer;
+
+/** Load a vector set. Defaults to the one shipped with this package. */
+export declare function loadVectors(path?: string): VectorSet;
+
+/** Replay a vector set against the independent implementations. */
+export declare function runConformance(vectors: VectorSet): ConformanceResult;