CRITICALTB · registered work
CRITICALTB: deterministic containment of AI agents
Deterministic containment at t = 0: no command runs without a verdict, and nothing destructive or boundary-crossing runs without a person’s signature (Ed25519).
CRITICALTB · containment at t = 0
The decision comes before the effect.
An after-the-fact control lets the effect happen and then reports it. Here the command does not reach the system until it has a verdict, and the default branch is not “let it through and log it”: it is “I cannot verify it, so I do not approve it”.
Choose an action to see the verdict.
An illustration of the work’s published rules. It is not the product or its real output.
What it does not do on your machine
In a containment product, this list is worth more than the other one.
- Does not registerservices, scheduled tasks or drivers
- Does not alterthe PATH, the system registry or the execution policy
- Does not writeoutside the profile of the user who installs it
- Scansthe disk read-only
- Re-measuresthe fingerprints of what is installed against its manifest on start-up
The PC edition ships its runtime for Windows. On Linux and macOS it works if the runtime is present: declared, not promised.
Evidence
Registration and published fingerprints.
CRITICALTBSHIELD v0.2 · work registered on 28/09/20262609287131254
SHA-256 · CRITICALTB-SHIELD v0.2 · consolidated work
86c9bea318fe8c138dd86659fc2747e9591d10e762f0d98ef9506e3b38396b45SHA-256 · CRITICALTB · PC Edition v0.3 · package
fc5a0c3e2fc1f97643952d658b050dd3818d5c7d09fd689d918a125000b8aae5