Jira progress: loading…
RMAP
Risk Mapping Engines
1. Overview
Risk Mapping Engines (RMAP) map validated and enriched signals to predefined risk taxonomies or frameworks.
RMAP engines translate data into risk-relevant representations without modifying the underlying values.
2. Design Principles
-
Framework-Driven
Risk mappings are always tied to an explicit framework. -
Deterministic Classification
Given the same inputs and rules, mapping outcomes are reproducible. -
Explainable Mapping
Each mapping result is traceable to its rule set.
3. Scope of Responsibility
3.1. What RMAP Engines Do
- Map signals to risk categories
- Assign risk levels or bands
- Align signals with external risk frameworks
4. What RMAP Engines Do Not Do
- ❌ Compute or aggregate values
- ❌ Enrich taxonomies (META)
- ❌ Enforce policy actions
- ❌ Perform estimations
5. Inputs
- Validated and enriched signals
- Risk framework definitions
- Mapping rules and thresholds
6. Outputs
- Risk-mapped classifications
- Risk metadata and severity indicators
- Mapping provenance references
7. Canonical Identification
- Engine Type:
RMAP - USO Code:
RMAP - Category: Micro Engine (MICE)
Status: Stable
Owner: Computation Hub / MICE