Skip to main content

MOD-EXP

Module Explorer

Module coverage dashboard

Documentation Coverage

Auto-generated from MDX frontmatter using id and omr_module_ids.

Total docs
941
Set
930
TBD
0
Missing
11
Multi-module docs
103
Coverage %
98.8%
Modules represented
16/11
Module heatmap
Top-covered modules
ModuleDocsExplorer
Computation Hub
computation-hub
244Open
Shared Intelligence Stack
sis
231Open
ZARA
zara
211Open
Verification & Assurance
verification-assurance
103Open
Reports & Insights Hub
reports-insights-hub
79Open
constitutional-governance
constitutional-governance
78Open
Input Hub
input-hub
50Open
Risk Intelligence Framework
rif
41Open
pergamum-pulse
pergamum-pulse
22Open
EcoWorld Academy
ecoworld-academy
13Open
Module universe
Expected modules in taxonomy: 11
All expected modules are represented.
Generated at: 9/1/2026, 6:07:37 PM

A ZAYAZ Module is a bounded capability domain that orchestrates multiple engines, data models, rules, and workflows around a coherent ESG purpose.

A module typically contains:

LayerWhat it includes
Domain scopeA clearly defined ESG capability (e.g. Risk, Reporting, Net Zero, Verification)
Engines (plural)One or more engines (rule, AI, micro, validation, aggregation)
Signal bindingsSSSR mappings to signals, metrics, and frameworks
Governance logicTrust thresholds, human-in-the-loop rules, audit requirements
Workflow contractsHow it interacts with ZADIF, verifiers, HubSpot, calendar, etc.
External faceAPIs, reports, exports, or ZARA/ZAAM entry points

Modules sit one level above engines.

Engines vs Micro-Engines vs Modules

A. Micro Engines (MICE)

  • Atomic, single-purpose
  • Stateless or narrowly stateful
  • Examples:
  • Flight emissions calculator
  • Risk tagger
  • Monte Carlo simulator
  • Root-cause analyzer
  • Identified via MEID
  • Replaceable, versioned, testable

B. Engines (mid-level)

  • Still computational, but broader
  • Often aggregate multiple micro-engines
  • Examples:
  • DICE
  • DaVE
  • SEM
  • AISIM
  • NETZERO compute core
  • Can be reused across modules

C. Modules (top-level capability domains)

  • Orchestrate engines + rules + workflows
  • Have governance meaning
  • Are licensable / white-label units
  • Show up in architecture diagrams and contracts

Engines compute. Modules decide when, why, under what trust conditions, and with what consequences.


The Module information below is auto-generated from /workspaces/zayaz-docs/docusaurus/src/generated/modules.generated.ts

To see individual modules:<ModuleExplorer id="input-hub" defaultOpenId="input-hub" />

To filter by tag: <ModuleExplorer tag="csrd" />

Modules

Modules Registry Table

This page is auto-generated from `config/system/omr.modules.json.

  • Each row is a module (for example SEM, ZHIF).
  • The spec column links to the MDX spec for that module, if entrypoint is set.
IDCodeNameTypeDomainCategoryLifecycleSignalsSpec
semSEMSmart Extrapolation Modulemodulecomputation-hubextrapolationdraft · v0.1.0uso:DATA.EXTRAPOLATION, csi:CSI_DATA_EXTRAPOLATIONOpen spec



GitHub RepoRequest for Change (RFC)