Sample proof run
AI Agent Action Proof Run
This sample shows how another party checks a proof bundle after an AI agent acts. Inspect the action boundary, evidence manifest, receipt, verifier result, challenge path, and digest manifest before packaging a security workflow for your own case.
Sample lineage
99741c8d50cd3adbfdc28bc317ac563a1e8dd1ef
All GitHub artifact links on this page use the sample commit, not the mutable main branch.
ed4614932f1b96fa9cc082fb481239ac8655bd49596d846db4da5bf5eb6dca14 RECEIPT.json
The commit pin and manifest line support replayable sample inspection only; they are not production custody proof.
Manifest provenance
witnessops/witnessops-sample-cases
sample-cases/ai-agent-action-proof-run/MANIFEST.sha256
efa7181d7575e95cb63673442cfe48671a3bb8a8
6c43e87534a4e445321c46d9765efa885d3df5aa8eb8110a214653b0f46d7447
Manifest coverage
MANIFEST.sha256 is displayed as the digest-list artifact, but it is not self-listed inside MANIFEST.sha256. README.md is hashed in the pinned manifest, but it is not shown as a page inspection artifact.
ACTION_BOUNDARY.json, AUTHORITY_MAP.json, EVIDENCE_MANIFEST.json, RECEIPT.json, VERIFY_RESULT.json, CHALLENGE_PATH.md, MANIFEST.sha256
ACTION_BOUNDARY.json, AUTHORITY_MAP.json, CHALLENGE_PATH.md, EVIDENCE_MANIFEST.json, README.md, RECEIPT.json, VERIFY_RESULT.json
MANIFEST.sha256
README.md
Three-minute buyer walkthrough
Can another party inspect who approved the action, what ran, what evidence survived, and what the verifier checked?
A CISO, AI platform owner, GRC lead, or auditor needs to read the bundle without guessing what each file means.
The sample demonstrates receipt shape and verifier path. It is not a production deployment, legal compliance claim, or whole-program assurance claim.
Sample outcome
What this sample shows before you open the artifacts
A sample AI agent performed one bounded code or configuration workflow after human approval.
VERIFY_RESULT.json reports pass_with_sample_limitations for the sample receipt shape, manifest checks, and declared evidence boundaries.
This sample does not prove production deployment, legal compliance, source-system truth, production signing-key custody, or complete AI governance.
You can inspect how authority, action scope, evidence, receipt, verifier result, challenge path, and manifest fit together before packaging your own security workflow.
Read the buyer walkthrough first if you want the plain-English path. Open the artifacts when you want to inspect the bundle directly.
How to inspect this sample
Confirm the sample is scoped to one workflow, one agent/tool path, and one touched system.
ACTION_BOUNDARY.json
SHA-256: ede15bd741240b1dbbfa654cfefb458664af4082ce4cedc79caa3f98d2550a07
Inspect who may approve, run, review, and challenge the action.
AUTHORITY_MAP.json
SHA-256: ae8e868544dbd4aee86a9480c4651c477b754a433d8f7bef924401bc749ddb62
Review captured artifacts, hashes, sources, and declared evidence gaps.
EVIDENCE_MANIFEST.json
SHA-256: 5bd0eae8e0ded738cd841fea082c1515a56a023dfa90c5d49dc3454e7897e99a
See how approval, action, evidence, result, and limits are bound into one record.
RECEIPT.json
SHA-256: ed4614932f1b96fa9cc082fb481239ac8655bd49596d846db4da5bf5eb6dca14
See what passed, what failed, and what remained outside the verifier boundary.
VERIFY_RESULT.json
SHA-256: d719577e1cf3ebd083df7a9017eeacb6ef260662513726e4da01cf83c25e4c4d
Understand how another party can inspect, dispute, or ask for stronger evidence.
CHALLENGE_PATH.md
SHA-256: 5dde8aeb13a51302ccb6880c2444f242b7a9c44c55fd81e1fd7dffcdb9ce7b3d
Check the published file digests so artifact drift is visible.
MANIFEST.sha256
SHA-256: 6c43e87534a4e445321c46d9765efa885d3df5aa8eb8110a214653b0f46d7447
The manifest is the sample drift check, not a production custody claim.
AI agent proposes and performs a bounded code or configuration change after human approval.
Can another party inspect who approved the action, what ran, what system it touched, what evidence survived, and what could not be verified?
Use the sample to inspect the proof shape, then submit one bounded agent-assisted workflow for your own package.
Artifact set
The one workflow, one action path, and one system boundary under review.
SHA-256: ede15bd741240b1dbbfa654cfefb458664af4082ce4cedc79caa3f98d2550a07
Open artifact
Who can approve, run, review, and challenge the agent-assisted action.
SHA-256: ae8e868544dbd4aee86a9480c4651c477b754a433d8f7bef924401bc749ddb62
Open artifact
The captured artifacts, hashes, sources, and known evidence gaps.
SHA-256: 5bd0eae8e0ded738cd841fea082c1515a56a023dfa90c5d49dc3454e7897e99a
Open artifact
The signed or simulated receipt binding approval, action, evidence, result, and limits.
SHA-256: ed4614932f1b96fa9cc082fb481239ac8655bd49596d846db4da5bf5eb6dca14
Open artifact
The verifier result showing pass, fail, or limits for the sample bundle.
SHA-256: d719577e1cf3ebd083df7a9017eeacb6ef260662513726e4da01cf83c25e4c4d
Open artifact
How a third party can inspect, dispute, or request stronger evidence.
SHA-256: 5dde8aeb13a51302ccb6880c2444f242b7a9c44c55fd81e1fd7dffcdb9ce7b3d
Open artifact
Digest list for checking that the sample artifacts did not silently drift.
SHA-256: 6c43e87534a4e445321c46d9765efa885d3df5aa8eb8110a214653b0f46d7447
Open artifact
Proof-run shape
- one workflow
- one action path
- one receipt
- one verifier result
- one challenge path
Boundary
This sample demonstrates the receipt shape and verifier path only. It does not claim production deployment, legal compliance, or complete AI governance coverage.
Ready to test your own workflow?
Use the sample to inspect the proof shape before submitting your own workflow. The request page asks for your name, work email, optional company or team, security workflow, workflow/tool path and touched system, scope and approval boundary, and evidence available.