Published sample, not live customer evidence
Launch readiness review
Synthetic public sample from the OffSec suite. Deterministic fixture evidence only. Not a live customer launch review, not production verification, and not launch approval.
Sample case
Launch readiness review
Situation: one launch host needs a before-and-after readiness picture against an approved baseline: drift, findings, and open decisions on the package, never automatic launch approval.
How to use this sample
1. Read the owner signal
Open review-summary.json for the decision-facing summary of this synthetic run.
2. Inspect drift
Read drift.json for admitted changes between baseline and candidate snapshots.
3. Read findings and report
Use findings.json and report.md for posture notes and named limits.
4. Stay inside the boundary
Historical verification output is a reference, not a current verification result or launch approval.
What you can inspect
- baseline and candidate snapshot relationship
- drift notes for admitted v1 changes
- findings and readiness report
- receipt, evidence manifest, and hash sidecars
- buyer walkthrough and historical reference output
Package files
- BUYER_WALKTHROUGH.md
- review-summary.json
- drift.json
- findings.json
- report.md
- receipt.json
- evidence_manifest.json
- verification_result.json
Proofpack bytes are published as a .proofpack file (ZIP-compatible contents). Prefer the listed package files for browser inspection.
Legacy proofpack format
This sample uses an earlier proofpack format. It is not compatible with the current Bundle V1 verifier. A pinned historical verifier is not presently available. Downloads are preserved for historical inspection, not as a current verification result.
Boundaries
- No launch approval, security guarantee, remediation, or arbitrary cloud review.
- No compliance certification or continuous monitoring.
- Synthetic trust keys only, not production signing custody.
- Not live customer evidence, production verification for your environment, or compliance certification.