{"repo":"war851/AI-Governance-Architecture","free":true,"listed":false,"github":"https://github.com/war851/AI-Governance-Architecture","clone":"git clone https://github.com/war851/AI-Governance-Architecture.git","description":"Claude Code best practices applied to application design. Interactive HLD/LLD visualizations, a DB-governed implementation example, and the same primitives as a runnable agent: the Governed Agent. LLM-agnostic, DB-governed, GDPR-ready.","language":null,"stars":52,"topics":["ai-architecture","ai-governance","claude-code","eu-ai-act","gdpr","governed-ai","llm","prompt-engineering","tdd","ai-safety"],"license":null,"category":"ai-agents","readme_excerpt":"Governed AI Architecture: Structure Beats Intelligence A reusable pattern where a single database owns the process (steps, functions, skills, messages, and data evolution), and the LLM is a stateless semantic engine. Don't train your AI. Certify it. Open Interactive Architecture Diagram · view source The same primitives as a runnable agent: Governed Agent · Article: EU AI Product Architecture --- The Bridge: Claude Code → DB-Governed Applications This architecture is a direct transformation of Claude Code's configuration model into a database-governed application pattern. The same separation of concerns that makes Claude Code effective - structure over intelligence, config over code, governance over vibes - applied to full applications. Claude Code DB Governed App Same Principle --- --- --- CLAUDE.md cascade - 5-level config hierarchy Config tables - steps, messages, skills Behaviour lives in config, not in code or weights Skills files - methodology loaded at runtime Skills table - methodology loaded at runtime Don't train - certify. Swap a skill, change the lens Slash commands - executable units by name Edge functions - executable units by step Defined input → defined logic → defined output Rules - path-scoped, loaded when relevant Step scope - prerequisites + visibility Right context at the right moment PLAN.md - explicit sequence of work Steps table - explicit ordered sequence Process is defined, not improvised by the LLM TODO.md - tracks what feeds what Data evolution - o","default_branch":null,"files":null,"tree":[],"storefront":"/r/war851","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/war851/AI-Governance-Architecture/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}