AEGIS evaluates engineering proposals through six gate checks over caller-supplied metrics and records each authenticated decision in a hash-chained audit trail. The hosted API and MCP endpoint are offline. The Python client, the local MCP server, and the offline attestation verifier are published on PyPI with their source.
Every proposal is evaluated against six gate checks over metrics the caller supplies. The result is a structured decision — PROCEED, PAUSE, HALT, or ESCALATE — with confidence scores, rationale, and next steps. Every authenticated evaluation is hash-chained; sandbox evaluations are not recorded.
Proposal → [Risk] [Profit] [Novelty] [Complexity] [Quality] [Utility] → Decision
↓
PROCEED / PAUSE / HALT / ESCALATE
+ confidence + rationale + next steps
+ hash-chained audit entryThe repository contains self-authored governance templates and runbooks. They are not certifications, and no third-party compliance audit or certification assessment has been conducted on AEGIS itself. See compliance maturity →