Correctness

Kind: quality-attribute

Layer: Computation Core

Record: architecture:correctness

Severity: mandatory

Scope: function, module, system

Canonical: Ontology

The degree to which the behavior of code matches its specification.

Listed in Architecture principles, after Repeatability and before Formal Verification.

Requires

• Specification
• Validation
• Tests

Reinforces

• Design by Contract

Enables

• Safe Operation

Conflicts with

• Undefined Behavior

In tension with

• Delivery Speed

Tensions

• Correctness / Delivery Speed

Violated by

• Undefined Behavior

Refactored by

• Unit Tests
• Define Contract

Severity

• mandatory

Category

• Correctness / Determinism / Verification

Enforced by

• codemods/entrypoints/code-point.entrypoint.ts

Reinforced by

• Domain Model
• Happens-Before Relationship
• Semantic Contracts
• Postconditions
• Invariant
• Formal Verification
• Specification-Based Testing
• Property-Based Testing
• Verification
• Fail Fast
• Error Handling
• Design Review
• First-Principles Design
• Model Evaluation
• Finite State Machine
• Schema Validation
• Type Safety
• Semantic Consistency
• Input Validation
• Atomicity
• ACID
• Consistency
• Isolation
• Concurrency Control

Enabled by

• Preconditions
• Single Source of Truth

Linked from

• Who does what
• Unknown is not pass
• Counting copies
• Coverage is derived
• Separate, trade, or mitigate
• What can drift, seen through how it drifts
• Domain Architecture
• Causality / Ordering / Distributed Time
• Contracts / Interfaces / Compatibility
• Correctness / Determinism / Verification
• Error Handling / Resilience
• Architecture Review / Evolution / Governance Artifacts
• Model Architecture
• Behavioral Patterns
• Schema / Canonical Data / Semantics
• Security / Privacy / Compliance / Governance
• Transactions / State / Concurrency
• Contracts / Interfaces / Compatibility
• Core Vocabulary
• Correctness / Determinism / Verification
• Severity levels
• The resolutions