Why AI Code Generators Produce Incoherent Codebases — and How a Model Registry Fixes It

The architecture behind Factory de Odoo: a 28-agent pipeline that guarantees cross-module coherence across a full ERP module suite Every time I tried using an AI code generator for Odoo ERP modules, I ran into the same wall. The individual files looked reasonable. Models were declared, views were structured, security rules were present. But as soon as I looked at the codebase as a whole, the cracks appeared: a Many2one field in Module 8 pointing at a model that Module 3 never actually declared. A security group defined twice in two different modules with slightly different XML IDs. Menu items from Module 6 and Module 11 both trying to parent themselves to a root menu that didn't exist yet. The generator hadn't failed. The output had. The root cause is architectural: most code generators — AI-assisted or not — have no persistent shared state across files. Each file is generated in isolation, with only whatever fits in the current context window as "memory" of what came before. On a smal