MOD-EXP
Module Explorer
Documentation Coverage
Auto-generated from MDX frontmatter using id and omr_module_ids.
| Module | Docs | Explorer |
|---|---|---|
Computation Hub computation-hub | 222 | Open |
ZARA zara | 206 | Open |
Shared Intelligence Stack sis | 181 | Open |
Reports & Insights Hub reports-insights-hub | 79 | Open |
Input Hub input-hub | 50 | Open |
Risk Intelligence Framework rif | 41 | Open |
Verification & Assurance verification-assurance | 38 | Open |
acad acad | 26 | Open |
SEEL seel | 10 | Open |
NetZero netzero | 7 | Open |
| Directory | Total | Set | TBD | Missing | Coverage | Review | Distribution |
|---|---|---|---|---|---|---|---|
| computation-hub-calcs | 210 | 210 | 0 | 0 | 100% | Review gaps | |
| key-zayaz-features | 113 | 113 | 0 | 0 | 100% | Review gaps | |
| appendices | 73 | 73 | 0 | 0 | 100% | Review gaps | |
| templates | 67 | 67 | 0 | 0 | 100% | Review gaps | |
| academy | 26 | 26 | 0 | 0 | 100% | Review gaps | |
| system | 26 | 26 | 0 | 0 | 100% | Review gaps | |
| shared-intelligence | 23 | 23 | 0 | 0 | 100% | Review gaps | |
| input-hub-general | 18 | 18 | 0 | 0 | 100% | Review gaps | |
| reports-hub-dashboards | 17 | 17 | 0 | 0 | 100% | Review gaps | |
| system-info | 17 | 17 | 0 | 0 | 100% | Review gaps | |
| ai-intelligence-layer | 15 | 15 | 0 | 0 | 100% | Review gaps | |
| reports-hub-visualization | 15 | 15 | 0 | 0 | 100% | Review gaps |
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:
| Layer | What it includes |
|---|---|
| Domain scope | A clearly defined ESG capability (e.g. Risk, Reporting, Net Zero, Verification) |
| Engines (plural) | One or more engines (rule, AI, micro, validation, aggregation) |
| Signal bindings | SSSR mappings to signals, metrics, and frameworks |
| Governance logic | Trust thresholds, human-in-the-loop rules, audit requirements |
| Workflow contracts | How it interacts with ZADIF, verifiers, HubSpot, calendar, etc. |
| External face | APIs, 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 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
entrypointis set.
| ID | Code | Name | Type | Domain | Category | Lifecycle | Signals | Spec |
|---|---|---|---|---|---|---|---|---|
sem | SEM | Smart Extrapolation Module | module | computation-hub | extrapolation | draft · v0.1.0 | uso:DATA.EXTRAPOLATION, csi:CSI_DATA_EXTRAPOLATION | Open spec |