Algoblocker enterprise
Layer 3 of Algoblocker’s 3+2+1 stack is a NumericalOS
profile the operator builds locally. This site does not host ISOs for it.
Boot remains unverified until numericalos-verify-boot observes
a specific artifact.
No join. No telemetry. No default coordinator.
Receipts use the same
C hash as numos.state.
The Algoblocker control plane never stores a receipt by default.
Export the profile
py -3 -m numos.export_state --profile privacy-workstation --seed-only --out dist py -3 -m numos.distro --profile privacy-workstation list py -3 -m numos.receipt --example py -3 -m numos.receipt --write receipt.txt --workstation
Units: warp, resolver,
receipt-export (numctl receipt-export),
extension-policy, plus the self-init floor
(mounts, identity, hold). All four privacy units are
required_units of the privacy phase
(on_failure: degrade), so a missing warp-cli
degrades that phase instead of being skipped.
What this is not
- Not a metal-verified boot
- Not Cloudflare Access and not HMAC device-lock
- Not anonymity (WARP is a Cloudflare herd)
- Origin JA3 stays the browser unless Gateway TLS inspection is on
Algoblocker surfaces: control plane · WARP / Cloudflare One onboard · receipt schema.