Implementation: Mixed, per defense (see the table) · Exposure: INTERNAL. See status labels. Safety is a floor that holds even when a component misbehaves. This page lists the threats and which defense answers each.

Architecture contract

Assumptions: the host, the signing keys and the policy configuration are trusted. One executor is fenced by its environment only, which is a weaker guarantee than the gated ones. The kernel does not claim to stop a compromised host.

Current implementation

The rows marked on main are implemented and internal. They are not reachable through api.allternit.com and are not a certification. Recorded-only replay is on main (internal), but replay-based regression checks and the conformance suite that would test these defenses continuously are not.

Availability

Developer relevance

Assume any input can be hostile and any single defense can fail. Do not build a feature that relies on a model choosing to behave.