lambda · partner evaluation
agλ
lambda
verify-first public semantics · partner depth

Check attestations.
Without seeing inside.

Lambda binds structured content to tamper-evident attestations that independent parties can check. You can learn what valid and invalid mean on the pavilion; the machinery that mints attestations is partner-only.

verify-first public partner production eval pass/fail only
public surface vs sealed core

Public material covers format semantics and verification behaviour — whether an attestation checks out, not how it was produced. Exposing signing paths would invite cloning, probing, and oracle-style attacks.

1
Learn the boundary
Pavilion: attestation format · verifier rules · evidence summaries.
Semantics only — no signing recipe
2
Fit your use case
Chain-of-custody · supply-chain integrity · regulated attestations.
Production evaluation is partner-gated
3
Request partner access
Submit via /access/ with team context and deployment intent.
Bilateral NDA · manual review · no public binary
partner access

Lambda has no public download. Partner teams receive a scoped evaluation path after review.

request evaluation →

Third parties can confirm whether an attestation checks out. How attestations are produced — composition, policy, signing — stays sealed.

Privacy: partner evaluation runs on local fixtures only.

public surface
format semanticspavilion docs
verifier behaviourpass/fail only
evidence summariesscoped results
sealed · never exposed
signing machinerypartner only
pipeline compositiontrade secret
production keysnever public
key fields
valid invalid chain_ok format
evidence ledger

Pinned gate run · scope-labelled numbers only.

headlinethroughput bench
scope64-byte proof claim · pipeline stages
gateproduction_gate PASS
tests125 tests summed
reproducereval-kit bench JSON