CIO — Anti-Patterns

Documentation status: guide — see Maturity and evidence.

Avoid governance choices that erase the separation between domain meaning and implementation.

• Treating every source-level feature as a supported product commitment.
• Publishing internal implementation names as external API contracts.
• Letting each project duplicate the same domain vocabulary independently.
• Coupling business models to one UI toolkit, database or accelerator backend.
• Choosing distributed execution by default instead of from latency, resilience or sovereignty requirements.
• Allowing undocumented public endpoints or generated SDK drift.
• Treating a successful demo as evidence of operability without monitoring, backup, recovery and upgrade procedures.