Schema Validation

Kind: mechanism

Layer: Contracts Core

Record: architecture:schema-validation

Severity: mandatory

Scope: data, API, message

Canonical: Ontology

A mechanism that parses incoming data against a schema at the boundary and rejects any payload that does not conform.

Listed in Architecture principles, after RAID Redundancy and before Type Safety.

Requires

• Schema Contract

Reinforces

• Correctness
• Data Contract

Enables

• Fail Fast
• Interoperability

Conflicts with

• Untyped Payloads

In tension with

• Flexible Input

Tensions

• Schema Validation / Flexible Input

Violated by

• Trusting External Input

Refactored by

• Introduce Boundary DTO

Severity

• mandatory

Category

• Schema / Canonical Data / Semantics

Enforced by

• runtime/entrypoints/grammar.entrypoint.ts

Refactors

• Schema Drift
• Implicit Contract
• Stringly Typed Programming
• Explicit Contracts
• Preconditions
• Centralized Configuration
• Self-Describing Architecture
• Self-Describing Structures
• Metadata-Driven Design
• Input Validation

Required by

• Declarative Configuration

Enabled by

• Canonical Schema

Linked from

• Definitions own what, code owns how
• Anti-patterns
• Contracts / Interfaces / Compatibility
• Control / Coordination / Centralization
• Correctness / Determinism / Verification
• Core Modular Design
• Error Handling / Resilience
• Metadata / Self-Description / Declarative Systems
• Schema / Canonical Data / Semantics
• Security / Privacy / Compliance / Governance
• Contracts / Interfaces / Compatibility
• Schema / Canonical Data / Semantics
• Security Privacy Compliance
• Severity levels
• The resolutions

in this codebase

• schemaFindings