How we label product readiness

A feature name alone says little about whether a team can depend on it. Code may exist before provider interoperability, hardware coverage, operational monitoring, or external review is complete. ZKAuth uses three readiness labels across the public changelog.

Available

Available means the supported path is implemented, documented, and intended for current use within its stated limits. It does not imply a certification, external audit, or capability that the documentation excludes.

Preview

Preview means the product surface and core path exist, but a production expectation is incomplete. OAuth and OIDC configuration, for example, remains preview-scoped while selected provider interoperability is still being expanded. Preview users should expect narrower support and possible interface changes.

Experimental

Experimental work is research evaluation, not a production recommendation. Proof V2 and Access Pass use this label because the development implementation and evidence exist while cryptographic review, production ceremony, artifact provenance, and release authority remain open gates.

Where the detail belongs

The changelog states what changed and its availability. The evidence record holds test results and verification scope. The limitations page and threat model explain what is not covered.

Keeping those jobs separate gives a reader a short release history without hiding the material needed for a security decision.