Core Developer — Anti-Patterns

Documentation status: guide — see Maturity and evidence.

• Exposing a private implementation type because it is convenient for one binding.
• Adding backend-specific semantics to the conceptual model.
• Changing binary/public contracts without version negotiation.
• Treating benchmark success as correctness evidence.
• Adding a persistence optimization that changes conceptual identity or transaction meaning.
• Documenting an experimental kernel as universally available.
• Letting one adapter silently differ from local Runtime semantics.
• Depending on undocumented global state instead of explicit execution context.