Skip to main content
Jira progress: loading…

META

Metadata Enrichment Engines

1. Overview

Metadata Enrichment Engines (META) are micro-engines within the ZAYAZ Computation Hub responsible for attaching semantic, taxonomic, and governance metadata to data signals.

META engines do not compute or transform numeric values. They enrich signals with meaning, context, and classification required for compliance, explainability, and downstream reasoning.

META is an engine type within the MICE taxonomy.

2. Design Principles

  1. Non-Mutating Values
    META engines never alter quantitative values.

  2. Semantic First
    All enrichment is driven by explicit taxonomies, ontologies, or mappings.

  3. Composable Metadata
    Metadata can be layered incrementally without invalidating prior enrichments.

3. Scope of Responsibility

3.1. What META Engines Do

  • Attach taxonomy tags (ESRS, EU Taxonomy, GRI, etc.)
  • Assign materiality or relevance indicators
  • Flag regulatory or jurisdictional constraints
  • Annotate signals with risk, scope, or category metadata

4. What META Engines Do Not Do

  • ❌ Compute values (CALC)
  • ❌ Validate correctness (VALI)
  • ❌ Transform formats or units (TRFM)
  • ❌ Aggregate results (AGGR)
  • ❌ Enforce policy decisions (TRPG / ZADIF)

5. Inputs

  • Validated signals or outputs
  • Taxonomy and ontology references
  • Contextual parameters (jurisdiction, framework, scope)

6. Outputs

  • Original signal payload
  • Attached metadata annotations
  • Enrichment provenance references

META outputs are commonly consumed by:

  • RMAP
  • Reporting & disclosure engines
  • ZARA explainability layers

7. Canonical Identification

  • Engine Type: META
  • USO Code: META
  • Category: Micro Engine (MICE)

Status: Stable
Owner: Computation Hub / MICE



GitHub RepoRequest for Change (RFC)