Aegis

What is Aegis?

Aegis is a deterministic context compiler for AI coding agents (e.g., Cursor, Claude Code, Codex). It replaces probabilistic search with a Directed Acyclic Graph (DAG) backed by SQLite to map file paths and layers directly to Markdown documentation, ensuring agents receive exact architectural context for each editing task.

How to use Aegis?

After installing and configuring the server, agents invoke Aegis before editing a file; it deterministically traverses the dependency graph and compiles the required context. The exact setup and invocation commands are not detailed beyond the paradigm described.

Key features of Aegis

• Deterministic Context Routing (same input, same context, reproducible).
• Transitive Dependency Resolution (automatically fetches dependent guidelines).
• Dual Surface Architecture (Agent read-only context vs. Admin human review).
• Human-in-the-Loop Knowledge Evolution (proposes DAG updates, approved by humans).
• Massive Token Efficiency (12x reduction in token consumption, 3.5x faster responses in benchmarks).
• Optional Local SLM Expansion (node-llama-cpp engine for semantic intent extraction).

Use cases of Aegis

• AI coding agents needing architectural guidelines for a specific file or layer.
• Preventing AI hallucinated architectures by feeding deterministic context.
• Reducing token waste from agents endlessly grepping repositories.
• Maintaining codebase integrity with a “Tech Lead” that forces rules before edits.
• Enabling agent self-review and human-approved knowledge base updates.

FAQ from Aegis

How does Aegis differ from traditional RAG?

Traditional RAG suffers from a “semantic gap”—searching by feature keywords fails to retrieve abstract architectural rules. Aegis uses deterministic compilation via a DAG, not probabilistic vector embeddings.

What are the runtime dependencies?

Aegis uses a SQLite-backed DAG. It optionally supports node-llama-cpp (Qwen) for local SLM expansion, but this is opt-in.

Where does the context data live?

All rules and dependency mappings are stored in a SQLite database that backs the DAG.

Can agents update the knowledge base?

Agents can trigger aegis_observe to report missing rules, but canonical knowledge updates require human approval on the admin surface.

What transports/auth are supported?

—