Provenance

Provenance operations in @runstamp/sdk create immutable, tenant-bound lineage records. Each record binds exact input and output hashes to the operation, actor or model, policies, sanitized parameters, deterministic time, parent lineage, warnings, losses, and release-validator evidence. @runstamp/provenance is the internal binding name, not a separate install.

Install

npm install @runstamp/sdk

The SDK needs Node.js >=18.14.1. @runstamp/provenance is a private binding and is not published on npm.

Workspace implementation APIs

These helpers belong to the private engine package. The SDK does not export them directly.

• createProvenanceRecord and append helpers — create canonical hash-bound lineage.
• Detached Ed25519 signing and offline verification helpers — sign without coupling the package to key management.
• renderLineageReport — produce a human-readable report.
• Provenance schemas and the EX01 extension definition — validate and compose the same model in other runtimes.

Stable operations

The four catalog operations cover record rendering, report rendering, append, and verification.

common.validate.provenance accepts lineage envelopes and checks canonical record hashes and parent bindings. Its public input does not accept artifact bytes, an artifact resolver, or a signature key resolver. A PASS can report verifiedArtifacts: 0 and verifiedSignatures: 0; it does not prove that a file's content matches the recorded hash or authenticate a signature.

Callers must hash the artifact bytes themselves and compare their length and digest with the record. That is an application check. The private verifyLineage helper's byte and key resolvers are outside the public SDK operation contract. Lineage does not establish that an assertion is true, grant approval, or manage identity or keys.