Check the capsule

TELOS re-checking a TELOS-produced evidence capsule. Self-attestation, not independent validation.

The signed capsule and its preserved whitepapers document the July 2026 demonstration. They are historical artifacts.

What this demonstration proves, and what it does not

TELOS is checking its own capsule from its own benchmark re-check.

You can verify:

that the files presented here match the published SHA-256 commitments;
that the published predecessor links are internally consistent;
that covered receipt fields verify against the public key identified for this demonstration; and
that changing a covered field without a corresponding valid signature causes signed-receipt verification to fail.

You cannot verify from this page:

that the underlying benchmark runs happened as described, when claimed, or under the claimed configuration;
who controlled the signing key, unless you obtain its identity binding independently;
that the record includes every relevant event;
that the scores, decisions, or benchmark conclusions are correct; or
that these results generalize to another model, scorer, agent, domain, or deployment.

No independent third party has re-run and validated this capsule. This is a self-attestation demonstration, not independent validation, certification, or audit. It is not a customer deployment and does not indicate a partnership or endorsement by any person or organization referenced in the underlying materials.

Same changed receipt, two verification contracts.

The telos/0.1-unsigned verifier asks whether the receipt matches the hashes and predecessor links presented with it. After changed content is rehashed, the record can still return VERIFIED, because anyone can create a new internally consistent unsigned chain.

The signed-capsule verifier checks an additional condition: whether the covered receipt bytes carry a valid signature under the public key identified for this demonstration. The changed receipt does not. Its leaf signature and manifest commitments no longer match, so the verifier returns REFUSED.

A hash chain makes a change detectable only relative to a commitment the verifier already trusts. A signature binds covered bytes to a key. Neither one, by itself, proves that the underlying run happened, that the timestamp is trustworthy, that the record is complete, or that the scoring was valid.

The two paths, side by side

The same capsule is checked twice: once as published, and once with one covered field changed. Both run here in your browser. The verifier used below checks the manifest signature, the predecessor links, the entry hashes, and the per-receipt signatures over covered fields. The downloadable bundle additionally re-hashes every pinned artifact in the capsule.

Genuine capsule not yet run

The capsule exactly as published.

—

Changed receipt not yet run

One covered field in receipt 15 is altered before checking.

—

Run it yourself, offline

The bundle includes the capsule, this page, and a dependency-free Python verifier. All work offline.

Download the offline bundle (.tar.gz)

tar -xzf telos-demo-surface-bundle.tar.gz
cd telos-demo-surface-bundle
python3 verify.py            # expect valid=true, 30 receipts
python3 verify.py --tamper   # expect valid=false, entry_hash:15 and leaf_signature:15

Published documents this demonstration is bound to

SHA-256 of the published HTML at the time this page was built. Recompute them against the live pages yourself; if a document has since changed, the values below will not match, and that difference is the finding rather than a failure of this page.

Document	SHA-256 of published HTML	Bytes
Whitepaper	`d3ab2f76cca30647e3f15ed4016ef5bf7f19b358659bea912da4e6b922f52093`	51,986
Technical Method	`6a3f74893d6909718ae4919d0a800922f22942e8c2319f84917f32f57b1e4fc0`	79,576
Validation Report	`eb1aae6666565e886a3f5dfef43072b4c4ac038bf051d30484dc6968570784d7`	33,343
Record of Trust Protocol	`7597e1784d5340240b382d973b284dceff1fea864b0fc0631a9f0697c7be1f8f`	46,383
Regulatory Alignment Map	`0d55e4b5b5e0b44e70a6fcda1953cd6219cfdf0abf494d7a0941d1e1a35cbf27`	31,675

Withdrawn historical value

AgentDojo task correctness — ~~52.2%~~ ~~12 of 23~~ — WITHDRAWN.

This value appears here only as withdrawn historical provenance. The cited deposit does not support it. The supported statement from that deposit is 139 events, 54 matching classifications, 38.8 percent, with all 85 benign texts overflagged; it is TELOS self-scored classification evidence and is not evidence that execution was blocked.

Current disposition: COULD-NOT-RUN. Deposit DOI 10.5281/zenodo.21631031.

What the verifier on this page does and does not check

Checks: the manifest signature; each receipt's predecessor link and sequence; each receipt's entry hash; each receipt's signature over its covered fields; and the capsule head.
Does not check: whether the described runs occurred, when they occurred, who controlled the signing key, whether the record is complete, or whether any score or conclusion is correct.
REFUSED below is a result produced by an artifact verifier about bytes presented to it. It is not a statement that any action was blocked, stopped, prevented, or enforced against.