What was sealed is what you still have
Signed, Sealed, Delivered - I'm Yours.
Integrity tooling for agent instruction files and source trees.
When something drifts, verify names every non-OK path with status and digests — never a silent fail.
Verified by HashSeal
Two Paths
Sealed, Verifiable, Agent Instruction Files
Seal AGENTS.md, skills, and other AI instruction files with a
BLAKE3 digest
with optional GPG via git’s signing credentials. The idea is simple; Check instruction file integrity before sending them to models or agents to run. Sign your instructions so that your users can verify and trust that they are exactly what you intended to deliver.
Secure your CI and Build Chains
Tree ledgers, release bundles (hashseal-bundle/), and thin plugins
so CI and multi-agent builds cannot silently rewrite what you ship. Stop multi-agent workflows from accidentally altering build chains mid-stream. Ship builds with artifacts that can be verified by anyone.
How it works
-
Seal
Canonicalize content, write hashseal: "blake3:…" (instruct) or a tree ledger (build).
-
Ship or hand off
Commit, release, or pass instructions to an agent host — the seal travels with the files.
-
Check
Recompute digests. Failures list every path that drifted, with expected vs actual digests.
Quickstart
cargo build -p hashseal --release
cargo run -p hashseal -- seal --instruct --root fixtures/mvp-demo
cargo run -p hashseal -- check --root fixtures/mvp-demo
Same core powers the tiny hashseal-check binary, WASM, browser extension, and zero-dep verify SDKs.
Install details → · CLI reference →
Docs
Format, signing, verify SDKs, IDE and browser surfaces.
Tree seal, release bundles, plugins, packaging.