What AEGIS does

AEGIS builds an evidence pack from a DITA source and proves that each requirement is covered, current and approved, or names it as a gap.

Regulators, downstream providers and compliance leads read model documentation as evidence. They need each statement with its version, its source and the person who approved it. A DITA source in Git already holds all three. AEGIS reads the Gemma evidence set in dita-corpus: requirement topics, the relationship table that links each requirement to its evidence, each topic's prolog dates and keys, and the pull request that approved each file.

Four checks decide whether a pack can be released. They are plain code and give the same answer every time. One tool calls a model: when a requirement has no evidence, Gemini 3.8 Flash proposes a link, and a person approves or rejects it. The model never approves a link, releases a pack or edits a topic.

The quickest way to see it work is the AEGIS generate page. Pick a system and it builds the authority pack for the AI Office and a downstream pack for providers who build on the model, then measures both against the design's metrics. See Generate the authority and downstream packs.

On the AEGIS sandbox you act in a private sandbox. Your links, decisions and planted leaks are stored for 7 days and never change the source.