HALMAI's runtime enforcement guarantees are machine-verified continuously. Technical disclosure of kernel invariants and real-time integrity status.
Fetching integrity status...
Six core rules that are machine-verified every 5 minutes. Violation triggers incident creation and optional lockdown.
No side effect without ALLOW decision. Every execution must have a corresponding ALLOW decision.
No execution without valid executionToken. Every execution must have proper authorization chain.
Every execution must reference valid decisionHash. The hash chain must be intact.
Hash chain must be continuous. No gaps or breaks in the audit trail.
Lockdown state overrides all ALLOW. No executions during lockdown.
Tenant isolation enforced on every request. No cross-tenant data access.
Every agent action passes through authorize() before execution. Pure function evaluation against versioned policy rules. No side effects during evaluation.
Approved actions execute through execute(). Exactly-once guarantees via idempotency keys. All effects logged to hash-chained ledger.
Every proposal, decision, and execution linked by SHA-256 hash. Any tampering breaks the chain and triggers integrity alerts.
Any historical decision can be replayed against versioned policy snapshots. Results: PASS (consistent), FAIL (drift detected), UNKNOWN (missing version).
• 3 critical anomaly events within 5 minutes
• Hash chain integrity failure (if strict mode enabled)
• Kernel invariant violation (if strict mode enabled)
• Budget breach at critical level
• Manual admin trigger
When lockdown is active, all execution requests are rejected. Manual unlock with logged reason is required to resume operations.
Anyone can verify HALMAI's enforcement status via the public integrity endpoint:
curl https://halmai.ai/api/public/integrityReturns: enforcementActive, invariantsPassing, hashChainValid, lockdownActive, lastIntegrityCheck
Contact our team for technical deep-dives or underwriter walkthroughs.