COSMO · public evidence bundle

EXECUTION-CASE-002-G

EXECUTED × 2 deliver + approve 2026-08-15 · Supra chain 8 · micro-live · double ceremony

Scope of this proof: the FULL ECONOMIC ARC of a marketplace job — mandated delivery AND mandated acceptance with escrow release. Two independent execution cases ran through the same engine and the same verification entry point on live on-chain job 10 (5 wCOSMO escrow): the solver agent (K1) committed a pre-mandated result hash on-chain (deliver_result_v2) under a provider mandate, and the buyer acceptance (approve_delivery_v2, atomic escrow payout) was ALSO executed under a signed one-shot mandate — held by an agent-controlled buyer wallet, not a human wallet extension. This closes the gap EXECUTION-CASE-002 deliberately left open: the approval leg is no longer a direct human action, it is its own mandated, policy-checked, offline-verifiable case.

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)

The job (shared anchors)

Ceremony 1 — mandated delivery (market.deliver_result.v1, case_msuc7iwa03bd86)

Ceremony 2 — mandated acceptance (market.approve_delivery.v1, case_msuc8s79e56cea)

The approve policy re-verified before release: job DELIVERED and not yet settled (G1), execution key == on-chain buyer (G2), on-chain result hash == mandated hash (G3), mandate window inside the review window (G4), escrow release within the cap (G5). Payment proof: buyer wallet −5 wCOSMO, solver +5 wCOSMO in the settle transaction.

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

Authority on record

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

Check integrity with: openssl dgst -sha3-256 <file> · full list also in index.txt

Per case, the evidence files (everything except receipt.json, MANIFEST.json, journal.jsonl) match the MANIFEST.json entries byte-for-byte; each MANIFEST is sealed into its 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 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 BOTH cases: ACCEPT, 10/10 criteria, exit code 0 — separate offline verifications of internal consistency, run with the public COSMO verifier at heros.cloud/verifier/.

Honest limits

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