Trust / Security
Threat-aware by construction
Security in Omnacta OS is not a checklist added after the fact. Authority, effect boundaries, and attribution are structural to how a mission executes.
Two critical evidence-integrity findings from the latest internal audit are open and disclosed below; they are not resolved by this page's existence.
Threat-aware principles
Least authority by default
Nothing acts with ambient permission; every effect requires an explicit, scoped grant.
Attributable effects
Every effect is expected to trace back to the authority grant that permitted it.
Fail closed on uncertainty
When an effect's outcome cannot be verified, the mission blocks rather than assumes success.
No silent capability escalation
A worker cannot expand its own authority; escalation requires a new explicit grant.
Current open security gates
These are drawn directly from the latest internal audit verdict and are not narrowed here.
- The gateway-finish execution path is being remediated to reject arbitrary non-failure JSON before it can be treated as accepted proof.
- Process authorization is being bound more strongly to the exact executed argument vector and its child effects to close a scope-escape risk.
- Until a newer accepted audit supersedes these findings, no claim of end-to-end verified execution or complete process-effect authorization is made.
- A passing test count does not, by itself, supersede an open evidence-integrity finding.
Supply-chain and package identity
Mission Packs and dependencies are expected to carry verifiable identity and version pinning before they are trusted inputs to a mission. This is part of the target architecture; a public package registry and signing service are not available today.
Go deeper on evidence
The Evidence model page explains exactly what current verification does and does not prove.