Start with the situation
Each example names one bounded problem a buyer might have, not a product feature list.
Published sample — not live customer evidence
These pages are labelled samples and illustrations for orientation only. They are not live customer artifacts, production verification results, or certifications.
Examples
Example reviews you can inspect
See how WitnessOps packages a bounded review: the situation, what was checked, which evidence is referenced, and what remains unproven. Use these before you request work for your own environment.
Operator scripts and checks run inside a scoped package when useful. They are methods — not a product card for every capability.
How to use these pages
Inspect what was checked
Look for who authorized the work, what evidence is referenced, and how results are handed over.
Read the limits
Samples are labelled. They are not live customer evidence, production verification, or certification.
Sample cases
Local server security review
Full sample packageSynthetic hostSituation
A read-only local server security review was packaged for inspection.
What you can inspect
How posture and findings sit next to a receipt and hash manifest, and what /verify does and does not confirm for this sample.
Open example →
Launch readiness review
Full sample packageOFFSEC-LAUNCH-READYSituation
One launch host needs a before-and-after readiness picture against an approved baseline.
What you can inspect
Baseline/candidate relationship, drift notes, findings, proofpack ZIP, and named limits — not launch approval.
Open example →
Customer Security Review Sprint
Synthetic demoCSRSituation
A security questionnaire is holding up a deal.
What you can inspect
Synthetic answer matrix shape, evidence references, open items, and ownership of final submission.
Open example →
AI agent change package
Full package on GitHubReceipt + verifier pathSituation
An AI agent proposed and applied one bounded code or configuration change.
What you can inspect
Who authorized it, what was allowed, what evidence was captured, and how a third party can re-check the package.
Open example →
Custody / wallet-ops review
Full sample packageOFFSEC-CUSTODY-OPSSituation
A proof-backed review of custody or wallet-operations controls without keys or fund movement.
What you can inspect
Sanitised posture, findings, proofpack, and hard boundaries — no solvency or custody-of-funds claim.
Open example →
Incident readiness review
Full sample packageOFFSEC-INCIDENT-READYSituation
A bounded readiness record for one named incident scenario and environment.
What you can inspect
Sanitised readiness observations, open decisions, and proofpack limits — not live IR command.
Open example →
Access removed proof (method sample)
Method sampleNot a product cardSituation
One named access-removal event with sanitised before/after observations.
What you can inspect
Package shape and limits. Not a public product card and not universal access-elimination.
Open example →
SBOM field checklist (method sample)
Method sampleNot a product cardSituation
A labelled synthetic package shows how a field checklist can sit inside a delivery — not a public product card.
What you can inspect
Generation context, present/partial gaps, and limits. Not compliance certification and not a catalogue SKU promotion.
Open example →
Privileged access grant
Access pathExplanatory example onlySituation
Someone requested time-bounded administrative access for one task.
What you can inspect
How approval, provisioning, and entitlement evidence should connect — and where replay often stays weak.
Open example →
Approval-gated containment
Control pathExplanatory example onlySituation
A containment action must not run until approval is recorded.
What you can inspect
Gate enforcement, target-state evidence, and what a portable inspection path should include after the event.
Open example →
Limits that always apply
- Not live customer evidence or a claim of completed verification for your environment.
- Not a legal compliance claim, certification, or audit opinion.
- Not a production deployment claim or complete AI governance program.
- A valid public receipt result confirms the checks named in that receipt — not that every underlying action was correct.
Next steps
Verify a receipt
Upload or paste receipt JSON and read a clear, receipt-scoped result.
Open verifier →
Illustrative sample report
A generic report shape for orientation — not a live customer report.
Open sample report →
Start a review
Describe one situation without secrets. We confirm fit, scope, price and evidence handling before work starts.
Start a review →
Start a review
Primary route: /review/request
Fallback contact: engage@mail.witnessops.com
Do not send passwords, private keys, API keys, recovery codes, session tokens or other secrets.