Purpose
This localized note explains the scope and checks associated with **HexaOS Security**.
Checks
•Always verify the version, artifact, environment, expected result and return code.
•Repeat after a restart when persistence or runtime state is part of the scenario.
Boundary
A packaged component is not READY; documented runtime proof is required for the exact artifact.
Current status
HexaOS is in engineering and validation. No ISO is declared ready without reproducible tests.