LoomSeal

Proof, not promises.

One file. Verified by anyone. The KordLoom proof format: signed, chained, anchored bundles that verify offline, free, with no account and no trust in the sender.

Why it exists

When everything can be fabricated, the only evidence worth sending is evidence a stranger can check.

Anyone can generate a convincing screenshot now. A log can be edited, a dashboard can lie, and a compliance PDF can be written five minutes before the meeting. The old ways of showing your work stopped being evidence the day generating them became free.

LoomSeal is the KordLoom answer: when a KordLoom product says proved, this is the receipt. One JSON bundle carries the claims, the digests of the evidence behind them, their position in an append-only hash chain, the external anchors that fix that chain in time, and the producer's signature. A small open verifier checks all of it in seconds, offline. Send the file to an auditor, a security reviewer, a customer, a regulator, or another machine. None of them has to believe a word you say. That is the point.

Verify one right now

Sixty seconds from clone to verdict.

go install github.com/kordloom/loomseal@latest
git clone https://github.com/kordloom/loomseal
cd loomseal
loomseal verify examples/audit.loomseal.json --evidence examples/evidence

bundle     lsb_example_0001 from loomseal-demo 0.1.0
subject    fleet demo-yard
signature  ok, key sha256:f8840a25992b58b823321187e1c44d36ee1a748023034a46d26ea93419edaf07
chain      loomseal-chain-v1, full, 2 claims, head matched true
anchors    1 matched by coordinates, 0 proofs carried, not validated in this version
evidence   1 verified, 0 missing, 0 referenced only
VERIFIED   signed, chained (full), anchored by reference

Real output, reproducible from the public repository. The verifier is built on the Go standard library alone, so every line that touches a verdict is readable in an afternoon.

What a verified bundle means

Signed

The producer holding the signing key assembled these exact claims. Flip one byte anywhere and the signature fails, loudly, with the break named.

Chained

The claims sit in an append-only chain that has not been reordered, rewritten, or trimmed. Anchored history cannot be manufactured after the fact. Whoever has been recording, wins.

Anchored

Chain heads are fixed in time outside the producer's reach, and every artifact you were handed matches its recorded digest: the page as it stood, the run as it happened.

And the boundary, stated plainly, because proof that overclaims is just marketing: a chain fixes the record, not the character of the recorder. What verification cannot prove is spelled out in the spec right next to what it can.

Signed. Chained. Anchored.

For producers

One format across products, one verifier for everyone.

Dormouse and SwitchTender speak LoomSeal, and their exporters ship with their next releases; until then the example bundle and the seal package are the reference producers. If you build software that should prove what it did, import github.com/kordloom/loomseal/seal to sign bundles and compute chain links, follow the bundle shape in the spec, and register your claim types through the registry. The envelope, chain profiles, and verification stay common, so one verifier checks everyone, and the format is Apache-2.0, so adopting it requires no negotiation and no permission.