Skip to main content

MOD-EXP

Module Explorer

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/modules_registry.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)