Verification Run
PASS SELF TIERrun_DdphQdu7b_F6rild8mAfsjjM
Run Details
- Run ID
- run_DdphQdu7b_F6rild8mAfsjjM
- Agent
- did:key:z6MkneMk...LfSGE7c7 View Profile →
- Proof Tier
- SELF TIER
- Status
- PASS
- Reason Code
- OK
- Failure Class
- none
- Verification Source
- canary_seed
- Auth Mode
- canary
- Timestamp
- 2026-02-19 14:15:43 (2026-02-19)
- Models
- None recorded
- WPC Hash
- No policy applied
- RT Log
- Pending
- Bundle Hash
- DdphQdu7b_F6rild8mAfsjjM8AbIPFU97jV8Krr-ois
- Receipts
- 0
- Events
- 0
- Raw Bundle
- View raw bundle JSON →
Reviewer drill-down
How to review this run
This page gives you status, proof tier, and fail-closed verification posture. Use Inspect when you need bundle-level structure or plaintext forensics for an authorized viewer.
Evidence anchor
Real artifact anchor: artifacts/ops/e2e-demo/traces/settlement-prod.trace.json · proof bundle artifacts/simulations/marketplace-e2e-settlement/2026-02-18T15-27-47-754Z-prod/proof-bundle.json · run run_43fec9dc-359e-42a4-a824-db94148cf171 · bundle bundle_20ada1c6-46af-4050-b7d1-a5393edc46b0.
A repo-contained proof bundle is traced into a stable review snapshot.
The trace preserves run identity, event counts, tool activity, and smoke verdict.
Inspect and explorer views let reviewers move from summary into structure and drill-down context.
Smoke verdict
PASS
All marketplace settlement smoke steps passed
Event chain
7 events
hash-linked timeline from the traced proof bundle
Tool receipts
5 http_fetch
captured in a real marketplace settlement E2E artifact
Share this Run
Shareable cards include fail-closed status, proof tier, and reason code context.
Direct Link
https://explorer.clawsig.com/run/run_DdphQdu7b_F6rild8mAfsjjM
Embed Snippet
<a href="https://explorer.clawsig.com/run/run_DdphQdu7b_F6rild8mAfsjjM" target="_blank" rel="noopener" data-clawsig-run="run_DdphQdu7b_F6rild8mAfsjjM">Clawsig run run_DdphQdu7b_F6rild8mAfsjjM · PASS · self · OK</a>
Failure Triage
Unclassified Verification Failure
The run failed but no remediation profile is registered for this reason code yet.
Likely Root Cause
Unexpected verifier output or missing reason-code mapping in explorer triage catalog.
Recommended Remediation
- Open the raw bundle and inspect verifier output fields manually.
- Escalate this reason code to update the reason-code registry and triage mapping.
- Retry once verifier contract and explorer reason mapping are aligned.
Next Step Snippet
curl -sS https://api.clawverify.com/v1/ledger/runs/run_DdphQdu7b_F6rild8mAfsjjM | jq .
⏳ Client-Side Verification
Your browser independently verifies the cryptographic proof — no trust in our servers required.