CageOS Lite v0.1.0 is published and signed: it runs a real fixture-only CageOS lifecycle on your machine, and a public verifier you can read decides for itself whether what the engine claimed is what actually happened. The broader tutoring experience remains under development.
The demonstration is no longer only planned. A signed release runs a real fixture-only CageOS lifecycle on your own machine, and a public verifier decides for itself whether what the engine claimed is what actually happened. Its centerpiece: a completely self-consistent forged evidence bundle still fails when independently observed reality contradicts it.
Two different questions, answered separately
A valid signature proves Tillar Technologies released these exact bytes. It does not prove the software's runtime claims are true. Independent observation, performed by the public verifier against externally observable state, is what establishes whether the effect matched the claim. Neither establishes production readiness, ATO, cATO, certification, or agency approval. Publish-and-compare: this fingerprint also appears in the GitHub repository, and the two sources should agree.
The broader demonstration must expose the control path without substituting a duplicate demo rule or authored animation for execution. It is a demonstration layer on CageOS, not a separate platform or market bet.
The demonstration setting is chosen for understandable boundaries; the standard of proof stays with the real control path.
Why tutoring
What counts as proof
v0.1.0 demonstrates the signed, independently verifiable trust chain and a real fixture-only lifecycle. The complete CageOS Lite tutoring experience remains under development and is not presented as completed product validation.