Visual thesis
Poster-like narrative in public, utility-first detail in ops.
This wave follows a simple split: Claw EA gets the polished story and explorer gets the dense operator truth. Same workflows, different jobs, no card soup.
Workflow 01
GitHub PR proof workflow
The change itself, the commit proof, and the verification step stay in one review surface instead of being split across screenshots and side channels.
Real artifact anchor: proofs/feat/clawsig/human-readable-proofs/commit.sig.json · DID did:key:z6MktzmKpfCNcKSUp7qzTrZK3c89QFvhgmK7V1GXxMH9m8XW · commit:9455e07d21d20472610f9a7620c1f2183f16c79b.
Proof primitive
ED25519
commit-bound and offline-verifiable
Artifact type
message_signature
checked into the repo beside the change
Failure mode
Fail closed
wrong SHA or malformed envelope breaks trust immediately
What the UI has to do
Agent commits code in a normal branch.
The commit SHA is signed into commit.sig.json.
The PR pipeline validates the signature before merge.
Workflow 02
Proof bundle review workflow
Reviewers need a compact, repo-contained evidence view they can regenerate in CI. This bundle-review lane now comes from a traced marketplace E2E artifact instead of a local /tmp-only run.
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.
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
What the UI has to do
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.
Workflow 03
Arena decision workflow
Once a marketplace workflow fans out into multiple contenders, the UI has to show who won, why they won, and whether autopilot thresholds were actually met.
Real artifact anchor: artifacts/arena/arena_bty_arena_001/summary.json + artifacts/ops/arena-productization/2026-02-20T02-18-40Z-agp-us-060-execution-submission-autopilot/summary.json.
Contenders compared
3
arena_bty_arena_001 compare set
Winner
contender_codex_pi
Winner contender_codex_pi passed all mandatory checks and achieved top weighted score (89.2750).
Autopilot proof
10 staging / 3 production
valid pending_review thresholds met in AGP-US-060 evidence
What the UI has to do
The arena compares contenders against one bounty decision surface.
Reason codes explain why the winner cleared policy and scoring gates.
Autopilot evidence proves live readiness instead of implying it.
Generated from source artifacts
Registry refreshed: 2026-03-22T17:10:26.886Z