Architecture & Methodology📋

Software Engineering Practices📋

• "anything-as-code" — infrastructure, configuration, requirements, quality gates
• "you better make it a module" — modular design with clear boundaries, 62+ projects in Diem CMF
• "don't put the burden on developers" — structural solutions over discipline-based ones

Domain-Driven Design Philosophy📋

• Attributes over base classes — developer declares intent, generator handles implementation
• 5 DSLs built on M3: DDD, Content, Admin, Pages, Workflow
• Migration field guide: from Big Ball of Mud to bounded contexts

Requirements Engineering📋

• Requirements as code — abstract classes with acceptance criteria as abstract methods
• 4-layer traceability: Requirement → Specification → Implementation → Test
• Compile-time enforcement: the build fails if any AC is unlinked
• typeof() and nameof() references (never strings)

Law as Code — Métacratie📋

• Compilateur croisé Law × Commons × Citizen — Roslyn cross-compiler generating specific legal frameworks indexed by META(Ex × Ty)
• Hexagonal pattern for bridges: pure Core domain ← Roslyn ports ← SourceGenerator / Analyzer / Cli adapters
• Three analyzer families: structural per-frame (generated), cross-frame coherence (bridges), root symbolic
• Pluralité native des cadres: multiple ${Author} coexist for same (Space, Time) — ConsensusScorer exhibits divergences
• Filiation: Chomsky generative grammars, Whitehead process philosophy, Roussel/OuLiPo specific frameworks, Sowa conceptual graphs, Meyer DBC, Catala

AI-Assisted Development📋

• Claude Code (CLI) — daily driver for architecture design, code generation, testing, documentation
• Claude Code Skills — custom skill definitions for consistent code generation across the ecosystem
• Multi-LLM integration in DockAi: Claude, OpenAI, Ollama