One bounded technical action. One scoped proof pack.
Use WitnessOps when a code patch, security finding, AI-agent action, access decision, or operational handoff needs to be explained to another reviewer.
This is not certification, production validation, or a whole-system audit. It is one bounded package with stated evidence, limits, and a challenge path.
What the package does
We name the boundary, inspect available evidence, package the result, preserve the receipt path, and show what another reviewer can inspect.
No dashboard subscription. No vague audit promise. One scoped package for one bounded technical action.
Scope
One technical action.
One system boundary.
One evidence package.
One receipt path.
One challenge path.
Send the non-secret fit check first.
Inspect the receipt shape and verifier path first.
Code patches, security findings, AI-agent actions, access changes, or operational handoffs that need reviewable evidence.
A bounded proof pack naming scope, evidence, receipt, verifier path, limits, and the next gate.
Secrets, credentials, private keys, customer records, MFA codes, or unrelated production data.
Use this when one action needs more than chat, screenshots, or a loose report.
- Code patches or pull requests
- Security findings or remediation work
- AI-agent actions touching code, access, or data
- Access, identity, exception, or approval decisions
- Operational handoffs that need evidence
What the proof pack contains
Scope map
The action, system, owner, and boundary under review.
Evidence package
Available artifacts, receipts, hashes, screenshots, reports, and known gaps.
Decision record
What changed, what was decided, and what remains outside scope.
Receipt artifact
A generated package artifact that binds scope, action, evidence references, result, and limits when produced.
Verifier path
Package artifacts and instructions another party can inspect offline, check, or mark out of scope.
Challenge path
How a third party can inspect, dispute, or request stronger evidence.
What the workflow package answers
- What technical action is in scope?
- What workflow, repo, access path, finding, or handoff is being reviewed?
- What evidence supports the package?
- What changed or was decided?
- What can another party inspect offline?
- What remains outside scope or challengeable?
Inspect the public proof-package shape
The public sample shows how another party checks the action boundary, evidence manifest, receipt, verifier result, challenge path, and digest manifest after a governed action.
Boundary
The public sample demonstrates package shape and verifier path only. It does not claim production deployment, legal compliance, whole-system security, or independent approval. WitnessOps names what is evidenced, what is declared, and what remains challengeable.