Semantic Consistency

Kind: quality-attribute

Layer: Contracts Core

Record: architecture:semantic-consistency

Severity: mandatory

Scope: domain, API, data

Canonical: Ontology

The degree to which one name carries one meaning across the code, the schemas and the documentation.

Listed in Architecture principles, after Normalization and before Ubiquitous Language.

Requires

• Ubiquitous Language
• Semantic Contracts

Reinforces

• Correctness
• Interoperability

Enables

• Disambiguation

Conflicts with

• Ambiguous Naming
• Inconsistent Error Model

In tension with

• Polysemy Across Contexts

Tensions

• Semantic Consistency / Polysemy Across Contexts

Violated by

• Ambiguous Naming

Refactored by

• Name the Concept
• Split Bounded Context
• Anti-Corruption Layer

Severity

• mandatory

Category

• Schema / Canonical Data / Semantics

Enforced by

• codemods/entrypoints/word.entrypoint.ts
• rules/eslint/strings-terminology.eslint.rule.ts
• rules/eslint/strings-vocabulary.eslint.rule.ts
• runtime/entrypoints/ontology.entrypoint.ts

Reinforced by

• Domain-Driven Design
• Knowledge Graphs

Required by

• Data Contract
• Canonical Model

Linked from

• Anti-patterns
• Domain Architecture
• Contracts / Interfaces / Compatibility
• Correctness / Determinism / Verification
• Model Architecture
• Schema / Canonical Data / Semantics
• Core Vocabulary
• Domain Architecture
• Schema / Canonical Data / Semantics
• Severity levels
• The resolutions