Verification
Two projects check the protocols and guarantees behind Lakestream: model-checked protocol specifications and a black-box harness for running systems.
Two separate projects sit alongside the Lakestream specs: protocol specifications, specified and model-checked in a separate repository, and streaming-proof, a black-box harness that checks a running deployment. Neither is a certification or a conformance suite.
Two kinds of checking
The protocol specifications are model-checked: a bounded exhaustive search over the state space of an abstract protocol, which can show that no reachable state violates a stated property. It says nothing about whether a given codebase implements that protocol.
streaming-proof is empirical: it exercises a real deployment through its ordinary client protocol and reports the violations it observes. It can find implementation and integration defects that a protocol model cannot express, and it can miss anything a given run did not happen to trigger.
Together they cover different failure surfaces. A protocol can be sound while its implementation is not; an implementation can pass a run while retaining a latent protocol-level flaw the workload never reached.
No certification
There is no certification program for Lakestream, and running either of these does not produce one. This documentation defines no cross-implementation certification suite and reports no passing conformance result.
Where conformance is stated
Conformance to the Lakestream specs is stated per role, in the specs themselves: see Conformance in the Storage Spec and the Materialization Spec. What each implementation actually supports is listed on Implementation status.