Architecture at a glance
The hexagon, the two placement paths, and why the stamp + SBOM is the product — a narrative overview of how knock is built.
Features at a glance
What knock does, organised by the product loop: place, stamp, inventory, sign, enforce, and reclaim — with links to the how-to and reference pages for each.
Transforms & signed attestations
The hardening primitives and the SLSA / in-toto signing model.
Package-level SBOM
The inventory knock attaches to every placed image (copy and rebuild) so a CVE becomes one query, and why presence precedes signing.
Deletion & retention
The two removal axes, and why knock marks (usage-gated) instead of hard-deleting.