Proof Run Request

Request one proof run

Name one code patch, security finding, AI-agent action, access decision, or operational handoff you want packaged. No files, logs, screenshots, exports, credentials, private keys, MFA codes, or customer evidence are needed for the first fit check.

What happens next

01We check whether the technical action is bounded enough for one proof pack.
02We confirm the system boundary, action path, likely evidence sources, and obvious gaps.
03We reply with fit, scope, fee, and next action before any source materials are accepted.

First message only

Do not submit secrets, credentials, private keys, MFA codes, source exports, full logs, screenshots, customer records, or unrelated production data. Name evidence types only; source materials are handled after scope is agreed.

Commercial scope

Fee, timing, and evidence handling are confirmed by email after the first fit check.

No proof run starts from this form.

No customer evidence is accepted until scope is agreed.

Typical bundle

✓ACTION_BOUNDARY.json
✓AUTHORITY_MAP.json
✓EVIDENCE_MANIFEST.json
✓RECEIPT.json
✓VERIFY_RESULT.json

Inspect sample package

Boundary kept clear

Not a production deployment claim.

Not a legal compliance claim.

Not a complete AI governance program.

Need help? Support./Disclosure: Security.

What the proof pack contains

Boundary map

What action is in scope, who approved it, who acted, and where authority stops.

Action path

The one workflow, tool path, or touched system under review.

Evidence manifest

Available artifact classes, source references, hashes where available, and known gaps.

Receipt artifact and verifier path

Package artifacts that name approval, action, evidence references, limits, and challenge path when the scope supports them.