Case examples
Illustrative case examples by lane.
Examples below describe how the program lanes can be applied in real partner, institutional, and platform workflows. They are illustrative scenarios, not endorsements or promises of buyer / regulator / insurer acceptance.
All case examples are illustrative. Real customer-named case studies will be published only with written permission.
By lane
AGENT-01 — agentic SaaS
An AI-agent SaaS records authority and action evidence per high-impact agent action so reviewers and counterparties can independently verify what the agent was authorized to do and what it actually did.
Illustrative scenario.
PAY-01 — high-value transfers
A payment platform records authorization, beneficiary, and reconciliation evidence around high-value transfers, packaging the evidence as a reviewer-friendly packet for internal and counterparty diligence.
Illustrative scenario.
ID-01 — privileged operator
A platform issues authority to a privileged operator and packages the authority record into an ID-01 packet so downstream reviewers can verify who held what authority and when.
Illustrative scenario.
HUMAN-01 — production change
A platform-operations team packages the human approval around a production change into a HUMAN-01 packet so an internal or external reviewer can verify approver, scope, and time.
Illustrative scenario.
VENDOR — vendor portfolio
A procurement team standardizes vendor evidence across a portfolio of recurring vendors using VENDOR packets so each vendor review delivers a consistent reviewer-friendly packet.
Illustrative scenario.
DORA/VENDOR — resilience scope
An operational-resilience team packages resilience and critical-vendor evidence into a DORA/VENDOR packet to support internal review and counterparty diligence (illustrative profile, not legal DORA certification).
Illustrative scenario.
Submit a case example
Partners that want to publish a named case example can email program@attestlayer.com. Cases are published only with written permission and reviewed for boundary language.
The AttestLayer trust model
AttestLayer’s trust model is intentionally narrow. It records what was submitted, what was accepted into scope, what was issued, and how the issued kit can be checked.
The model uses
- SHA-256 artifact hashing
- manifest-based evidence inventory
- canonical receipt hashing
- Ed25519 receipt signatures
- JWKS public-key discovery
- offline verification
- fail-closed verification behavior
What it proves
- files match the manifest
- manifest matches the receipt
- receipt key ID matches a public key
- receipt signature verifies
- the kit has not been modified since issuance
What it does not prove
- company compliance status
- company security status
- controls are operating effectively
- a buyer, auditor, insurer, bank, regulator, or PSP has accepted the packet
- the evidence content is legally sufficient
Integrity and issuance evidence only. Not audit, certification, or compliance guarantee.