OpenChainGraph Suite · CONTRACT A3

Model Passport Lifecycle

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.
Reading mode (RUNBOOK): Run these steps in order. The validation-status step reads the tier from step one and the outcome-analysis result from step two to decide the model’s status, so registration and backtesting have to run first.

Model inventory registration > outcome-analysis backtest > validation status determination — a linear SR 26-2 model passport chain. No routing gate: validation_status branching lives inside the final node's own output, not chain-level routing.

OpenChainGraph · 3 Steps compliance control Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology: Model Inventory Entry → Model Outcome-Analysis → Model Validation Status
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Market Rationale
Buyer: Model Risk Management officer / bank MRM function under SR 26-2 (successor to SR 11-7)
Forcing function: SR 26-2 model inventory and periodic revalidation cadence; ongoing-monitoring backtest requirements; AI/MRM regulatory-flux positioning
Chain Stages · 3 Steps
1 ROOT node
Model Inventory Entry Builder art-450-model-inventory-entry
Model-inventory record with proportionality tier and completeness score. Passes to outcome-analysis backtest.
↓
2 D2 node
Model Outcome-Analysis Comparison art-451-model-outcome-analysis
Predicted-vs-actual outcome backtest with pass/fail status against the declared breach-rate tolerance. Passes to validation-status determination.
↓
3 TERMINAL · D3 node
Model Validation Status Assessor art-453-model-validation-status
Final SR 26-2 validation status, days-since-validation, and next-due-in-days. Final stage.
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: This model was validated last August. Is it still inside its validation window as of January 2027?
Run the AINumbers MCP tool `run_chain` with {"chain":"model-passport-lifecycle"} and read `art-453-model-validation-status.validation_status`.
Re-run with `inputs` for `art-453-model-validation-status`, reusing the values that result echoed, with `as_of_date` set to "2027-01-15". Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/model-passport-lifecycle.html