finance.credit.ifrs9_ecl.v1
Verification Objective
Verify that the Forge runtime can execute the canonical IFRS 9 Expected Credit Loss Primitive Profile using the production execution pipeline.
After completing this example you should be able to:
- execute the profile successfully
- inspect the execution result
- verify generated artifacts
- validate deterministic replay
- understand the execution contract
This document is intended as an executable verification example rather than a conceptual overview.
Primitive Profile
| Property | Value |
|---|---|
| Primitive | mc@1 |
| Profile | finance.credit.ifrs9_ecl.v1 |
| Output Value | expected_credit_loss |
| Runtime | Compute |
| Replay | Supported |
| Artifacts | Supported |
| Deterministic | Supported |
| Validator | validateFinanceCreditIFRS9ECLArgs |
Capability
This Primitive Profile estimates Expected Credit Loss (ECL) for a portfolio of credit exposures using Monte Carlo simulation.
The implementation supports multiple exposure stages, macroeconomic adjustments and configurable simulation parameters while preserving deterministic replay semantics.
Canonical Execution Contract
Execution uses the canonical Forge execution protocol.
Primitive
mc
Version
1
Profile
finance.credit.ifrs9_ecl.v1The request is validated before execution begins.
Required Inputs
The canonical validator requires:
- iterations
- exposures
- exposures[].ead
- exposures[].pd
- exposures[].lgd
- exposures[].maturity_months
Requests missing any required field are rejected before execution. :contentReference[oaicite:1]
Optional Inputs
Examples include:
- horizon_months
- output_mode
- macro_scenario
- stage multipliers
- exposure identifiers
- discount_rate
- volatility parameters
These parameters extend the analytical model without changing the execution contract. :contentReference[oaicite:2]
Canonical Smoke
The Forge repository includes a maintained smoke test for this profile.
The smoke verifies:
- successful execution
- expected output value
- summary statistics
- histogram generation
- artifact generation
- deterministic seed handling
Smoke documentation:
→ /verification/smoke-suite
(Real request payload intentionally omitted here to avoid duplication. The maintained smoke suite is the canonical source.) :contentReference[oaicite:3]
Verification Expectations
A successful execution should demonstrate:
- request validation succeeds
- execution completes successfully
- output contains
expected_credit_loss - summary statistics are returned
- requested artifacts are produced
- replay metadata is available
Successful execution alone does not validate analytical correctness.
Replay should also be verified.
Negative Validation
The maintained smoke suite also contains validator failure scenarios.
One example intentionally submits an invalid probability (pd > 1).
Expected result:
ok: false
error:
invalid_argsThis verifies that malformed requests are rejected before entering the execution runtime. :contentReference[oaicite:4]
Runtime Evidence
Successful execution exposes runtime evidence including:
- execution identifier
- primitive profile
- runtime metadata
- execution summary
- artifact references
- replay metadata
The exact evidence surface depends on execution policy.
Replay
Replay should produce equivalent execution characteristics when executed using the same deterministic seed and canonical execution contract.
Replay verification is described in:
→ /verification/replay-determinism
Artifacts
Typical artifacts include:
- execution summary
- histogram
- sample preview
Additional artifacts may be available depending on execution policy. :contentReference[oaicite:5]
Applied Intelligence Modules
This Primitive Profile is reused across multiple Forge Intelligence Modules, including:
- Banking Intelligence
- Credit Intelligence
- Capital Intelligence
- Portfolio Intelligence
The execution contract remains identical regardless of consuming Intelligence Module.
Related Documentation
- /examples/mc/
- /verification/
- /verification/smoke-suite
- /verification/replay-determinism
- /verification/artifact-inspection
Verification Checklist
| Verification Surface | Status |
|---|---|
| Primitive resolved | ✓ |
| Contract validated | ✓ |
| Execution completed | ✓ |
| Runtime inspected | ✓ |
| Artifacts inspected | ✓ |
| Replay verified | ✓ |
| Negative validation tested | ✓ |
Final Principle
This document verifies an executable Primitive Profile rather than describing a theoretical capability.
The canonical implementation, validation rules, maintained smoke suite and replay workflow together provide independently verifiable evidence that the profile behaves as documented.
Continue in Forge Studio
This document describes the canonical execution contract for this capability.
The Forge documentation explains how this capability works.
Forge Studio allows you to inspect, execute, and verify the live implementation.
Capability Explorer
Browse the live capability catalog, supported execution surfaces, available Primitive Profiles, and execution metadata.
→ https://studio.forgepool.io/capability-explorer
Block Registry
Inspect the registered Primitive Profile, execution contract, block metadata, adapters, versions, and runtime characteristics.
→ https://studio.forgepool.io/studio/blocks-registry
Execute
Execute this capability using Forge Studio, the Execution API, or an MCP-compatible client.
Verify
Before interpreting the result, inspect:
- runtime evidence
- generated artifacts
- deterministic replay
- execution metadata
Trust should be established through independent verification rather than documentation alone.