His goal wasn’t a flashy chatbot. It was infrastructure: a system that knows its sources, ranks them by legal quality, and won’t confuse commentary with binding law.
Summary
Oliver Belitz developed a "second brain" for the EU AI Act, a structured knowledge base costing approximately €60 and 2.5 million tokens, designed to provide reliable AI assistance in compliance-heavy domains. Unlike traditional RAG systems that retrieve isolated snippets, this infrastructure knows its sources, ranks them by legal quality, and identifies conflicts without fabricating certainty. Belitz's system, inspired by Andrej Karpathy and built with Claude Code and Obsidian, uses a maintained markdown corpus with explicit cross-links, avoiding vector databases. Key features include source hierarchy, collision logic, statutory grounding, anti-anchoring rules, and semantic drift control, ensuring the AI behaves like a disciplined research function. Oliver Schmidt-Prietz validated this approach, emphasizing that token burn is scaffolding, wikis require policing against drift, and separate "regulatory" and "general" vaults are crucial to prevent contamination.
Key takeaway
For CTOs or VPs of Engineering building AI systems in compliance-heavy or high-stakes domains, you should prioritize pre-compiled, governed knowledge infrastructure over ad-hoc retrieval. Your teams must budget for upfront token costs as scaffolding, implement rigorous maintenance to prevent semantic drift, and establish separate knowledge vaults for different levels of truth. This approach enhances factuality, auditability, and conflict handling, reducing reputational and compliance risks by providing transparent, authority-respecting AI outputs.
Key insights
Curated, structured knowledge bases with explicit governance outperform naive RAG for high-stakes AI applications.
Principles
- Uncertainty belongs in the answer.
- Structure knowledge by authority hierarchy.
- Audit knowledge graphs periodically for drift.
Method
Build a knowledge graph using a maintained markdown corpus with explicit cross-links, separating sources by legal quality, implementing collision logic, and requiring statutory grounding for answers.
In practice
- Separate regulatory from general knowledge vaults.
- Implement anti-anchoring rules for prior publications.
- Design periodic audits beyond basic lint checks.
Topics
- EU AI Act
- Knowledge Graph Architecture
- Legal AI Systems
- Source Hierarchy
- Semantic Drift Control
Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Engineer, AI Architect, Legal Professional
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Pascal’s Substack.