MAS Project MindForge — AI Risk Management: Operationalisation Handbook

MAS Project MindForge — AI Risk Management: Operationalisation Handbook — 50% of in-scope requirements covered.

7 requirements · 7 in scope (7 designed). The 50% is weighted over the in-scope base.

MAS Project MindForge: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. oversight-modes-machine-enforceable · designed

    Scope & AI oversight: the three human-oversight modes are machine-enforceable at the action boundary, not…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 36 governedui, 12 purpose permission

  2. action-authority-inventory · designed

    Scope & AI oversight: the AI inventory is extended to an AI action-authority inventory — what each AI is…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 12 purpose permission

  3. escalation-before-finality · designed

    AI risk management: out-of-mode and out-of-scope actions escalate (REQUIRE_APPROVAL) or are refused before…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 25 edge governance, 36 governedui

  4. third-party-vendor-authority-register · designed

    AI risk management: third-party / vendor AI risk is governed via an external authority register at the action…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 12 purpose permission

  5. deployment-controls-authority-gateway · designed

    AI lifecycle management: deployment controls are enforced at the Authority Gateway before a consequential…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 25 edge governance, 12 purpose permission

  6. monitoring-change-evidence-replay · designed

    AI lifecycle management: monitoring & change management produce replay-provable Evidence Packs, replayable by…

    Rule packs: kye:rule-pack:mas-mindforge · Constitution: 13 resilience loop, 30 audit worm retention

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: MAS Project MindForge is an industry-co-created supervisory initiative whose AI Risk Management: Operationalisation Handbook gives Singapore financial institutions practical guidance for operationalising AI risk management across four blocks — Scope & AI Oversight, AI Risk Management, AI Lifecycle Management, and Enablers (17 considerations in total). KYE Protocol™ operationalises the action-boundary subset of the Handbook at runtime: it governs whether a consequential financial AI action is authorised, within an oversight mode the FI has declared for that use, evidenced, contestable, and final at the moment it happens — and PROVES the basis, replayable by MAS or internal audit. KYE™ does NOT replace MindForge and does NOT govern the FI's governance operating model, model-development methodology, or the correctness of the AI's output (§0.25 integrate-not-compete; honest scope). · License: MAS Project MindForge — AI Risk Management: Operationalisation Handbook is published by the Monetary Authority of Singapore and industry participants. KYE™ registry cites the Handbook's oversight-mode and risk-management constructs for mapping purposes only.

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Scope & AI oversight2020050%
AI risk management2020050%
AI lifecycle management2020050%
Enablers1010050%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
mas-mindforge.oversight-modes-machine-enforceableScope & AI oversight: the three human-oversight modes are machine-enforceable at the action boundary, not policy-on-paperdesignedrule_packs: kye:rule-pack:mas-mindforge
dictionaries: internal
constitution_refs: constitution/36-GOVERNEDUI.md, constitution/12-PURPOSE-PERMISSION.md
mas-mindforge.action-authority-inventoryScope & AI oversight: the AI inventory is extended to an AI action-authority inventory — what each AI is AUTHORISED to do, not just what existsdesignedrule_packs: kye:rule-pack:mas-mindforge
dictionaries: internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
mas-mindforge.escalation-before-finalityAI risk management: out-of-mode and out-of-scope actions escalate (REQUIRE_APPROVAL) or are refused before finalitydesignedrule_packs: kye:rule-pack:mas-mindforge
constitution_refs: constitution/25-EDGE-GOVERNANCE.md, constitution/36-GOVERNEDUI.md
mas-mindforge.third-party-vendor-authority-registerAI risk management: third-party / vendor AI risk is governed via an external authority register at the action boundarydesignedrule_packs: kye:rule-pack:mas-mindforge
dictionaries: internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
mas-mindforge.deployment-controls-authority-gatewayAI lifecycle management: deployment controls are enforced at the Authority Gateway before a consequential action proceedsdesignedrule_packs: kye:rule-pack:mas-mindforge
constitution_refs: constitution/25-EDGE-GOVERNANCE.md, constitution/12-PURPOSE-PERMISSION.md
mas-mindforge.monitoring-change-evidence-replayAI lifecycle management: monitoring & change management produce replay-provable Evidence Packs, replayable by MAS or internal auditdesignedrule_packs: kye:rule-pack:mas-mindforge
dictionaries: internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/30-AUDIT-WORM-RETENTION.md
mas-mindforge.enablers-named-accountabilityEnablers: every consequential AI action maps to a named accountable officer under whose authority it proceedsdesignedrule_packs: kye:rule-pack:mas-mindforge
constitution_refs: constitution/36-GOVERNEDUI.md, constitution/21-DELEGATED-AUDITABILITY.md

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.