Evidence Report

Scope: public demo · Tenant log: evd://tenant/t_demo · Period: 2026-07-18T01:08:23Z → 2026-07-18T01:08:23Z · Generated: 2026-09-02T13:49:49Z

VERDICT: VERIFIED

Independently confirmed public commitment (E2): every subject receipt summarized here is covered by a checkpoint whose anchor was re-read from the public chain during this report run and whose RFC 3161 token terminates at a TSA root supplied by the relying party. The earliest covering commitment was at 2026-07-18T01:08:26Z. This establishes public commitment no later than that block time; it does not prove the action's self-reported event time or export completeness. This HTML records the result of that run; it is not a signed live-query transcript. Re-run the live command below against a trusted RPC of your choice to reproduce the public-chain determination. Credential-bearing RPC URLs are not embedded; only exact allowlisted public endpoints may be shown.

Relying-party TSA root fingerprint(s), SHA-256 over DER: 2aca8fea5d3ce48b01cc77076293c280e6c23ffe44034757ee7833ca9f45d633. These identify the external trust input used by this level; the report does not make that trust decision for its reader.

Full bundle digest (SHA-256/JCS): bcd2193d4891fe184e91402a07d54c790c7db1118a6330470b5cea4e33bfcbf9 — cite this evidence bundle by that digest.

This report was generated from the verified evidence bundle plus the live chain checks listed below; the generator used no other data source.

Evidence levels, briefly

Each evidence level adds a requirement; this is not a score. This report's displayed subject rows: E2.

E0 · Signed receipt
The receipt's DSSE signature verifies. That authenticates the signed bytes, not the underlying action.

E1 · Presented history
E0 plus Merkle inclusion, key-log replay and signed-checkpoint consistency for the history presented—not latest history, capture/export completeness or independent time.

E2 · Public commitment
E1 plus one exact covering Base/Base Sepolia checkpoint confirmed live, with an RFC 3161 token for that same checkpoint digest ending at a TSA root supplied by the relying party.

E3 · Dual attestation
E2 plus an issuer signature and a co-signature from an active non-issuer registered recorder on the same receipt, verified under a recorder key supplied by the relying party.

What happened

time (UTC)	agent	action	context	level
session no session
2026-07-18T01:08:23Z	_system	Signing key created `evd.key.created`	key 6sihoKmS2ClmVd-s	E2 ✓
session s_a70a88a9d68f5d7e inferred
no mandate recorded
2026-07-18T01:08:23Z	refund_agent	AI model call `llm.chat`	gpt-x, status 200	E2 ✓
2026-07-18T01:08:23Z	refund_agent	AI model call `llm.chat`	gpt-x, status 200	E2 ✓
session no session
2026-07-18T01:08:23Z	_system	Signing key rotated `evd.key.rotated`	key z8BJ5P1udWHH4DnA	E2 ✓
session s_a70a88a9d68f5d7e inferred
2026-07-18T01:08:23Z	refund_agent	AI model call `llm.chat`	gpt-x, status 200	E2 ✓

What this level means: Every E2 ✓ line has the E1 receipt and presented-history checks plus live checkpoint coverage and a timestamp rooted outside the bundle.

Verification appendix

key log: 2 key(s) witnessed by the log itself; trust root 70d425bc4c581bfb8391da0e20b9ff317c5111d4fd1605508f0b3297a790fcdd (pin this out-of-band)
checkpoint chain: target size 5, root 988b24d590bd64ba…, append-only consistency verified across the chain
log origin UNATTESTED — no trust anchor was supplied for this origin, so who owns this log is unknown (not a failure, not a pass)
anchor LIVE-CONFIRMED on Base Sepolia: tx 0x8036062f311a1cb76936f1fb8751d04b9ff43a714c0c2768116ea9792753ee89, block 44284309, 2026-07-18T01:08:26Z — digest + emitter + block time confirmed on chain 84532, block 44284309; contract 0xF2B38e2376869FB2c268A175E612117E65f6B984; checkpoint digest 1bea54aa22cf39b0d9af2a37058e07c08411f559bcbe8143f60cddcd471bdf1b
live RPC used: https://base-sepolia.drpc.org · endpoint-string SHA-256 efcae95d312e6b934a3c12c67149c1ac24d7aa19d02aed9b479bdc19f24c387f (shown because this exact endpoint is on the narrow public allowlist)
RFC 3161 timestamp (qualified status NOT independently verified): 2026-08-09T21:15:45Z — https://timestamp.sigstore.dev/api/v1/timestamp (token chain terminates at a TSA root supplied out of band by the relying party); certificate revocation status (CRL/OCSP) was not checked
agent lineage: refund_agent: lineage not established

How to verify this yourself

pip install swarrm==1.2.0        # or: use verify/ from the repo
swarrm verify bundle.json           # → VERIFIED
swarrm verify bundle.json --trust sample_sigstore_tsa_trust.json --live --rpc https://base-sepolia.drpc.org   # external-level check

The bundled sample_sigstore_tsa_trust.json makes this run reproducible, but it is not independent merely because it is a separate file. Before relying on it, retrieve /api/v1/timestamp/certchain from Sigstore yourself and confirm the root's SHA-256/DER fingerprint is 2aca8fea5d3ce48b01cc77076293c280e6c23ffe44034757ee7833ca9f45d633.

No install? Drop the bundle into swarrm.ai/verify — it verifies in your browser, no account, nothing uploaded.

Annex

Download the embedded evidence bundle — the exact bytes this report verified, embedded in this file so report and proof travel together (P2: nothing else must accompany this document). Its SHA-256 is the digest cited above; any verifier run on the download must reproduce this report's verdict.

When Swarrm's hosted export flow creates a report, it appends the report's SHA-256 afterward as an evd.report.created receipt. That later receipt is not inside the input bundle and must be supplied and verified separately; standalone report generation does not create it.