LoomSeal woven LS mark

For producers

One format across products, one verifier for everyone.

loomseal.com · For producers

For producers

One format across products, one verifier for everyone.

The format does not care what the claims are about. Anything a machine records in order, and somebody later has to believe, fits the same envelope.

Audit and access logs Deployments and change control CI and CD runs Build provenance and SBOMs Incident timelines Backup and restore records Compliance evidence Agent and model run logs

SwitchTender emits audit bundles today. The rest are uses the format supports, not integrations that ship.

SwitchTender is the first shipping producer. The example bundle and the seal package are the reference implementations. The chain profiles in the spec were derived from software KordLoom already ships, so the format describes real constructions rather than hypothetical ones.

If you build software that should prove what it did, the Go SDK is the seal package: it computes chain links, strips exactly the members a signature covers, and signs bundles, so a producer's commitments can never drift from what the verifier recomputes. Emitting your first bundle is this whole program:

import "github.com/kordloom/loomseal/seal"

claim := map[string]any{
    "type": "acme.deploy/1", "at": "2026-09-20T12:00:00Z",
    "payload": map[string]any{"service": "api", "version": "1.4.2"},
}
link, _ := seal.LinkV1(nil, "in_yourinstall", 1, "", seal.ClaimContent(claim))
claim["chain"] = map[string]any{"seq": 1, "prev": "", "link": link}

doc := map[string]any{
    "loomseal": "0.1", "bundle_id": "lsb_first", "created_at": "2026-09-20T12:00:01Z",
    "producer": map[string]any{
        "product": "acme", "product_version": "1.0.0", "install_id": "in_yourinstall",
        "public_key": base64.StdEncoding.EncodeToString(pub), "key_id": seal.KeyID(pub),
    },
    "subject": map[string]any{"type": "run", "id": "deploy-1042"},
    "chain": map[string]any{
        "profile": "loomseal-chain-v1", "keyed": false,
        "params": map[string]any{"install_id": "in_yourinstall"},
        "head":   map[string]any{"seq": 1, "link": link},
    },
    "claims": []any{claim},
}
raw, _ := json.Marshal(doc)
signed, _ := seal.SignBundle(raw, priv)   // priv is your ed25519 key

That output already passes loomseal verify, and the fingerprint to pin is seal.KeyID of your public key, published at /.well-known/loomseal.json on a domain you control. Register your claim types through the registry so a verifier can say more than "unknown type". Other languages: the spec plus the conformance vectors are the contract, and the Python verifier was written from them alone, so a producer in any language can be checked against the same vectors. Wrappers are the community's to write; the reference stays small on purpose.

The envelope, chain profiles, and verification stay common, so one verifier checks every producer. The format is Apache-2.0, so adopting it needs no negotiation and no permission.

Why we use it ourselves

Building on do not take our word for it, then asking you to take our word for it, is not a position we can defend.

We use it on our own products for a reason that is a little uncomfortable. SwitchTender's promise is that it proves every change. Without a bundle that promise is a sentence on a website, and you would simply have to believe us that the audit trail behind it is honest. Building a company on do not take our word for it and then asking you to take our word for it is not a position we can defend. So SwitchTender emits them. switchtender audit bundle turns its audit chain into a signed bundle, and you can check the claim on the box without asking us anything.

An audit log is worth exactly as much as the recipient's trust in whoever is holding it. A bundle is worth the same to a stranger as it is to your oldest customer, because checking it never involves you at all.