Security
Zero Trust Intelligence (ZTI) sells verification, so this page holds itself to the same bar: what the gate enforces, how it fails, and where the honest limits are. No "uncrackable" claims. They would be false.
Enforcement model
A receipt binds to git write-tree: the content address of exactly what would be
committed. The same hash is checked at pre-commit and in CI, so nothing can drift between
what was verified and what ships. The gate is agent-neutral: it governs any committer,
human or agent, by git content alone.
Tier 1: runtime hook
Blocks out-of-contract writes and irreversible commands live during an agent session. Bash is screened for irreversible patterns and forbidden-path tokens.
Tier 2: pre-commit gate
Blocks the commit unless a passing receipt covers the staged tree. A receipt is minted only by re-running the contract's required checks; the agent's claim is never the input.
Tier 3: CI required check
Catches --no-verify at the merge, on the PR head SHA. This tier exists because the local bypass exists.
Failure behavior
No receipt, a failed receipt, an unreachable plane, and a license-locked plane all block. A plane outage never becomes an open gate. The plane is never in the evaluation path: the gate keeps enforcing on its cached contract, so a dead plane stops merges, not enforcement.
Receipts are hash-sealed per the open ZTIP protocol (RFC 8785 canonical JSON, SHA-256). The plane re-verifies the seal on ingest and rejects tampered receipts.
Honest limits
git commit --no-verify bypasses the local hook by design; that is git.
The CI required check is what catches it at the merge. The public
blocked PR shows exactly that play, caught.
The 30-day trial is enforced offline. Wiping plane state or rolling the clock back resets it. That tradeoff was accepted on purpose: there is no phone-home, and your plane never talks to us.
A determined reverser can patch a local binary. The license check raises a real bar against casual bypass and is a legal instrument for honest organizations. We do not claim more than that.
Deployment posture
ZTI Core is a single-tenant, self-hosted container. Your receipts, contracts, and audit trail stay on your infrastructure. License tokens are verified offline (Ed25519); nothing phones home. The public plane at demo.zerotrustintelligence.io is the operator's own console for a live instance, not a shared service.
Found a vulnerability?
Write to licensing@zerotrustintelligence.io with "Security" in the subject. You will get a direct answer from the author, not a queue.