Vectors

Vectors are the shared test cases that fix the rules byte for byte across languages. The package ships them in vectors/, one JSON file per entry point or pairing. Any implementation of the Legal Context Protocol, in any language, that passes them assembles the same bytes, computes the same hashes, and places and reads H in the same fields as this package.

Every expected value in a vector file comes from outside this package: a specification's published example, a standard's test value such as SHA-256 of "abc" from FIPS 180-2, a transaction read from a live network, or an independent tool (Python's json and hashlib, sha256sum, openssl, viem, eth-account, a rail's own SDK). Each file's about names its sources.

What they fixCopy Anchor Link

The vector files reference lists every file with its about.

Running themCopy Anchor Link

The files ship inside the package, beside dist/. This example runs the core rows of core-vectors.json through assemble and checks each expected hash:

import { readFile } from "node:fs/promises";
import { assemble, type Json } from "@integraledger/lcp";

const url = new URL("../vectors/core-vectors.json", import.meta.resolve("@integraledger/lcp"));
const core = JSON.parse(await readFile(url, "utf8")) as {
  vectors: { name: string; id?: string; binding?: [string, Json]; content?: [string, string][]; expectHash: string }[];
};

for (const v of core.vectors) {
  if (v.id === undefined || v.binding === undefined || v.content === undefined) continue;
  const content = v.content.map(([slot, hex]) => [slot, Uint8Array.from(Buffer.from(hex, "hex"))] as const);
  const atr = await assemble(v.id, v.binding, content);
  console.log(v.name, !("refused" in atr) && atr.atrHash === v.expectHash);
}

V1 true
V2 true
V3 true

The package's own test suite runs every file this way, in full. The buyer packages in integra-agentic-terms run the same files from TypeScript and from Python, so the rules hold in both languages.

PlantsCopy Anchor Link

A row marked plant is a deliberate wrong input with a known outcome: bytes one changed byte away from the ATR, a receipt with the hash in the wrong topic, an agreement resource advertising another ATR's hash. A check that accepts a plant is broken, whatever else it passes.