AEGIS
Govern and secure autonomous engineering. AEGIS sits between autonomous AI coding agents and development environments, enforcing machine-verifiable policy for scope, security, risk, multi-agent consensus, and cryptographic audit.
Kernel-Adapter Architecture
AEGIS decouples the governance engine from specific agent frameworks. OpenCode is the primary adapter, with Claude Code and Codex supported via standardized interfaces.
Governance & Security Capabilities
Built on a deterministic fail-closed model where unverified mutating actions and unknown identities are denied by default.
Agent Governance & Identity
Authenticates agent sessions, binds tool invocations to cryptographically attested identities, and enforces scope boundaries to prevent lateral capability escalation.
Execution Control & Gating
Intercepts file system modifications, command executions, and network egress. Mutating actions require explicit policy validation against defined project boundaries.
Policy Enforcement (aegis.yaml)
Machine-verifiable rules requiring approved Architectural Decision Records (ADRs) for structural changes, cited research for external integrations, and risk classification.
Immutable Hash-Chained Audit
All runtime events, prompts, tool outputs, and decisions are written to an append-only JSONL log chained with SHA-256 cryptographic hashes for tamper evidence.
Multi-Agent Consensus
High-risk code changes require independent peer review and consensus verification from distinct subagents or designated human supervisors before merge.
Machine Evidence Verification
Autonomous task completion requires verified machine evidence: zero compiler errors, passing test suites, linting validation, clean container builds, and verified commit signatures.
AEGIS Verification CLI Specification
Runtime verification primitives
AEGIS is currently in private developer preview under active enterprise development by Granwel. It is undergoing dogfood validation on Granwel corporate software and selective enterprise partner codebases.