Claim
What is the system asserting?
Aegis Trust Center
What is trusted, and why?
Aegis is designed around a simple rule: important claims should remain attached to the evidence and authority that make them credible.
Trust ledger
Five boundaries that matter at launch.
Each boundary answers a different question. None is allowed to silently stand in for another.
Scoped
Evidence
What source, signal, or observation supports it?
Authorization
What action was explicitly permitted?
Verification
What independent check ran after the change?
Decision
What is allowed, blocked, or still under review?
Local-first developer workflow
Supported deterministic analysis and security state can remain on the developer machine.
Provider use is explicit
When model-backed review is enabled, the configured provider route is part of the trust boundary.
Payment evidence is server-side
Browser checkout completion is not sufficient to unlock paid capabilities.
Missing proof remains missing
Unavailable checks and unresolved evidence are preserved instead of being relabeled as success.
Read deeper
Security claims need proof.
Inspect the security architecture, privacy boundaries, legal terms, or refund policy directly.