Program · Sample Kit
Sample standardized verification kit
Inspect the output format before partner qualification: manifest, receipt, binder, issuer key, verifier files, and browser/offline verification path.
The sample kit is a compact public example of the AttestLayer verification output. It is not a guarantee that every optional production artifact is enabled on every plan, ruleset, or adapter profile.
This matches the current public sample-kit boundary, which says live PASS delivery may include additional artifacts depending on plan, ruleset, adapter profile, and enabled features.
AttestLayer is not an audit opinion, compliance certification, insurer, bank regulator, payment processor, law firm, or procurement approver. Record-only evidence issuance for review workflows.
What the Sample Kit proves
The Sample Kit does not prove that a customer is compliant, secure, approved, insured, or accepted. It proves the output format: manifest, receipt, binder, issuer key, verification instructions, and offline verification path.
For business reviewers
Inspect the binder and understand what a forwarded packet looks like.
For technical reviewers
Inspect manifest, receipt, JWKS, hashes, and verifier files.
For partners
Confirm whether the output can be repeated across many clients without custom explanation every time.
Artifact list
The existing Sample Kit already lists the ZIP SHA-256, manifest root hash, schema, receipt key ID, manifest, receipt, JWKS, mapping, verifier files, and offline verification steps. The public sample kit currently describes this as a compact flat ZIP with 11 files, including manifest, receipt, sample binder, JWKS, mapping, and verifier files.
- START-HERE.pdf
- manifest.json
- receipt.json
- artifacts/sample-binder.pdf
- jwks.json
- mapping.json
- verifier/index.html
- verifier/app.js
- verifier/README.md
- README-FIRST.md
What partners should inspect
Reviewer readability
Can a non-technical reviewer understand the binder?
Technical inspection
Can a technical reviewer inspect the manifest and receipt?
Boundary language
Can the partner explain the PASS/FAIL boundary without overclaiming?
Forwardability
Can the packet be forwarded without requiring an account?
Verification path
Can the verification path work in browser or offline where enabled?
Repeatability
Can the output format be repeated across many clients?
Sample kit is not production scope
The sample kit is a public demonstration artifact. Production kits may differ by plan, ruleset, adapter profile, validation version, enabled features, and partner agreement. Do not promise a specific optional artifact unless it is included in the active agreement.
Ready to standardize the packet layer?
Use the public sample to inspect a compact verifier bundle, then request partner qualification to confirm which artifacts apply to your use case.