Correctness and resources
- Official verifier acceptance
- Reference proof equality
- Fixed-host resource matrix
- Crash, corruption, truncation, signal, and ENOSPC recovery
No production Guard artifact or purchase link is published until every technical, customer, merchant, legal, and retirement gate is backed by reviewed evidence.
A qualified release binds the Guard version, exact engine source SHA, OCI digest, artifact hashes, schema versions, compatibility profile, release date, SBOM, provenance, signatures, benchmark evidence, and review evidence in one signed channel manifest.
| Artifact | Current public availability |
|---|---|
| MIT Community source and doctor | Available in the public repository |
| Qualified Community engine binary and OCI image | Awaiting engine release gates |
| Guard v1 binary and OCI image | Awaiting all launch gates |
| Guard channel manifest | Published with the first qualified release |
| Guard checkout | Not yet for sale |
Qualified releases are planned quarterly. Old immutable releases are retained because checkpoints are exact-release-bound. A compatibility profile expands only after its complete correctness, resource, recovery, review, and external-use gate is repeated.
The website cannot enable checkout by changing a button or adding a URL. The published commerce configuration must indicate a passed canonical launch gate and contain a separately reviewed hosted-checkout variant before page code makes a purchase control clickable.