Skip to main content
Jira progress: loading…

VALI

Validator Engines

1. Overview

Validation Engines (VALI) are micro-engines responsible for verifying the correctness, completeness, and admissibility of data within the ZAYAZ Computation Hub.

VALI engines enforce structural and domain constraints without altering data values.

VALI is an engine type; individual validators are implemented as MEID-registered micro engines.

2. Design Principles

  1. Non-Mutating
    VALI engines never modify data — they only accept, reject, or flag it.

  2. Rule-Driven
    All validations are driven by explicit schemas and constraint definitions.

  3. Fail-Fast Semantics
    Invalid data is detected as early as possible in the execution chain.

3. Scope of Responsibility

3.1. What VALI Engines Do

  • Schema validation
  • Type and range checks
  • Mandatory field enforcement
  • Cross-field consistency checks
  • Declared constraint enforcement

4. What VALI Engines Do Not Do

  • ❌ Compute values (CALC)
  • ❌ Transform units or formats (TRFM)
  • ❌ Estimate missing values (SEM)
  • ❌ Aggregate results (AGGR)

5. Inputs

  • Raw input payloads
  • Computed or transformed outputs
  • Validation profiles and schemas

6. Outputs

  • Validation result (pass / fail / warnings)
  • Validation metadata and error codes
  • Provenance references

VALI results are consumed by:

  • CALC (pre-compute validation)
  • TRFM / AGGR (post-compute validation)
  • Policy gates and audit systems

7. Canonical Identification

  • Engine Type: VALI
  • USO Code: VALI
  • Category: Micro Engine (MICE)
  • CALC — Calculation Engines
  • TRFM — Transformation Engines
  • SEM — Stochastic Extrapolation Module

Status: Stable
Owner: Computation Hub / MICE



GitHub RepoRequest for Change (RFC)