Skip to content

Model risk register & inventory
ID MOD-173
System SD06
Repo bank-risk-platform
Build status Not started
Deployed No

Central Snowflake-native model register covering every model-bearing module on the platform. Serves as the authoritative inventory for the platform's own model-risk governance, and pre-populates the register fields that APS 113 and the RBNZ internal models compendium require — so customers can pull a ready-made register entry rather than constructing one from scratch.

Purpose

Every institution that deploys a platform model needs a model register entry for that model. APS 113 mandates specific fields (type, scope, IRB asset class, materiality/exposure, model owner, implementation date, validation rating, last/next validation dates). The RBNZ requires an agreed internal models compendium for IRB-accredited deposit takers. Building a register entry from scratch requires understanding the platform model in detail — the platform can supply that understanding directly.

MOD-173 maintains one canonical register entry per model-bearing module, kept current as the model evolves, and exposes it via a read-only API so each customer's own model inventory system can pull the record directly.

What it stores

For each model-bearing module (MOD-028, 030, 031, 033, 034, 035, 017, 023, 039, 055, 041):

  • Model identity: module ID, title, version, effective date, SHA of the deployed model artefact
  • Classification: model type, scope, applicable portfolio / IRB asset class, risk tier (1 / 2 / 3 per DT-013)
  • Materiality: total exposure and percentage of portfolio (customer-parameterised at deploy time)
  • Ownership: model owner, validation function, independent reviewer
  • Validation status: current validation rating, date of last validation, date of next scheduled validation
  • Evidence pack reference: S3 path to the current evidence pack artefacts
  • Pre-validation report: reference to the latest third-party pre-validation report
  • Regulatory approval status: APRA approval date (where applicable); RBNZ approval status and compendium reference (where applicable)
  • Change history: link to MOD-175 change-control records for this model

Deployment gate integration

The deployment pipeline gate for any model-bearing module checks that a register entry exists and is current before allowing promotion to production. A model module without a register entry will not deploy. This enforces the DT-013 definition-of-done at the infrastructure level.

Compliance visibility integration

If MOD-056 (compliance visibility engine) is deployed, it can read the register to surface approaching validation deadlines as obligation events — routing to the customer's compliance calendar automatically.

Module dependencies

Depends on

Module Title Required? Contract Reason
MOD-102 Snowflake account configuration & governance Required — Snowflake account provisioned by MOD-102 is the storage and query layer for model register tables and the read-only API.
MOD-104 AWS shared infrastructure bootstrap Required — EventBridge bus and SSM parameter store used for register-update events and deployment-gate configuration.
MOD-056 Compliance visibility engine Optional — Compliance visibility engine can surface model validation obligations as compliance evidence rows; integration is additive and not required for the register to function.

Required by

Module Title As Contract
MOD-174 Model performance monitoring & drift detection Hard dependency —
MOD-175 Model change control & re-approval workflow Hard dependency —
MOD-177 SD06 risk dashboard renderer Optional enhancement —

Policies satisfied

Policy Title Mode How
DT-013 Model Validation & Audit Policy GATE A model-bearing module cannot be marked Deployed without a corresponding register entry; the deployment pipeline gate enforces this check before promotion to production.
DT-005 Model Risk Management Policy LOG Central model inventory maintains the register required by the Model Risk Management Policy, covering all platform model-bearing modules with APS 113 and RBNZ compendium fields.

Capabilities satisfied

(No capabilities mapped)

Part of SD06 — Snowflake Analytics & Risk Platform Compiled 2026-05-22 from source/entities/modules/MOD-173.yaml