COSMO · public evidence bundle

EXECUTION-CASE-002

EXECUTED case_mst8l7i8d4391a 2026-08-14 · Supra chain 8 · micro-live · mandated work delivery

Scope of this proof: one mandated WORK DELIVERY — the solver agent registered and irreversibly committed a pre-mandated result hash on-chain (compute_rfq::deliver_result_v2, job 9, 5 wCOSMO escrow) under delegated provider authority, a one-shot signed mandate, a hash-pinned policy and a human ARM ceremony. The case ends at on-chain DELIVERED — buyer approval is a separate human step, deliberately outside the case. Together with EXECUTION-CASE-001 this is the generalization proof: one verification entry point, shared integrity guarantees, two domain-specific execution profiles.

Public evidence bundle. Offline verification uses the public COSMO verifier at heros.cloud/verifier/ (one self-contained file, no npm, no network) — a separate offline verification of internal consistency, not an independent third-party attestation.

← The institutional layer (context page)

Anchors

Two receipt hashes, both correct: the receipt statement hash is calculated from the canonical JSON representation of the signed receipt (sorted keys, no whitespace — this is the value recorded in the journal’s case_closed entry). The published file hash is calculated from the exact downloadable file bytes, including its final newline.

Subsequently settled (outside the case, as designed)

After the case closed at DELIVERED, the buyer approved the delivery as a separate human step: approve_delivery_v2 ↗ settled job 9 atomically on-chain (escrow payout to the solver and deposit release in one transaction). The full economic arc — principal, worker, acceptance, payment — completed; the approval leg ran as a direct human action, not yet as its own mandated case.

Drill honesty — the failures are part of the record

A first attempt closed EXECUTION_FAILED (an SDK argument-order defect broke the send BEFORE any network contact; on-chain state and sequence untouched, the receipt says exactly that, the one-shot mandate was consumed). A second attempt closed EXPIRED (the ARM ceremony missed the 20-minute mandate window by one minute — the ceremony clock is real). This third case ran simulate-first and closed EXECUTED on the first submit attempt.

Authority on record

Files (byte-identical copies of the canonical case documents)

Check integrity with: openssl dgst -sha3-256 <file>

The 13 evidence files (everything except receipt.json, MANIFEST.json, journal.jsonl, deliverable.json and the indexes) match the 13 MANIFEST.json entries byte-for-byte; MANIFEST is sealed into the receipt as evidence_root. deliverable.json is the delivered artifact itself — its sha3 IS the mandated and on-chain result_hash.

What verification checks (K/S/T/P/M/V/J/E/D/O)

• K — attestor key pin: the signing key is pinned in the trust store.
• S — receipt signature: ed25519 over the canonical envelope + statement.
• T — time bounds: attestation time within sane limits.
• P — policy pin: the policy hash matches the pinned, active policy.
• M — mandate integrity: recomputed hash, signature, case and policy binding.
• V — evidence integrity: manifest vs. directory, exact set, per-file sha3.
• J — journal chain: every entry hash-chained, opened first, closed last.
• E — execution artifact: pure ed25519 deliver-order check (no SDK), sender/mandate/correlation binding.
• D — derivation equality: the receipt statement re-derives byte-identically from the evidence.
• O — outcome consistency: outcome matches the evidence the case actually produced.

Result for this case: ACCEPT, 10/10 criteria, exit code 0 — a separate offline verification of internal consistency, run with the public COSMO verifier at heros.cloud/verifier/.

Honest limits

Frozen 2026-08-14. Signed originals are never modified after publication. · All settled proofs · Institutional layer