finance.system.systemic_fragility_search.v1
Overview
Verify that the Forge runtime executes the canonical Systemic Fragility Search Primitive Profile using the production Search execution pipeline.
After completing this example you should be able to:
- execute the canonical profile
- inspect the execution result
- verify generated artifacts
- validate deterministic replay
- understand the execution contract
This document demonstrates executable capability verification rather than financial modelling theory.
Primitive Profile
| Property | Value |
|---|---|
| Primitive | search@1 |
| Profile | finance.system.systemic_fragility_search.v1 |
| Runtime | Compute |
| Replay | Supported |
| Artifacts | Supported |
| Deterministic | Supported |
| CPU | Supported |
| GPU | Not Required |
| Validator | validateFinanceCapitalFragilitySearchArgs |
Capability
finance.system.systemic_fragility_search.v1 searches a cross-domain financial scenario space to identify combinations of capital, liquidity, contagion, sovereign, insurance, governance and market stresses that produce the highest systemic fragility.
Unlike Monte Carlo profiles, which estimate outcome distributions, this Search profile explores bounded mutation spaces and ranks candidate scenarios according to a deterministic discovery objective.
The profile is designed to identify fragility boundaries rather than forecast future events.
Canonical Contract
Execution uses the canonical Forge Search execution contract.
Primitive
search
Version
1
Profile
finance.system.systemic_fragility_search.v1Requests are validated before execution begins.
Required Inputs
The canonical validator requires:
- iterations
- base_scenario
- mutation_rules
- ranking
- ranking.objective
- ranking.top_n
Requests missing any required field are rejected before entering the execution runtime.
Optional Inputs
The implementation supports numerous optional scenario dimensions, including:
- CET1 ratio
- capital buffer
- funding gap
- liquidity buffer
- deposit flight
- wholesale funding rollover
- sovereign spread stress
- contagion intensity
- graph failure probability
- critical node stress
- cascade depth
- collateral deterioration
- insurance capital stress
- reinsurance recovery gap
- climate transmission
- governance pressure
- evidence
- scaling configuration
Only documented profile fields should be supplied.
Unsupported fields should never be introduced by clients or AI agents.
Canonical Smoke
The maintained Forge smoke verifies:
- successful validation
- successful execution
- ranked candidate generation
- deterministic seed handling
- runtime metadata generation
- replay metadata generation
- artifact availability
The maintained Smoke Suite remains the canonical source for executable payloads.
This document intentionally avoids duplicating maintained requests.
Verification Expectations
A successful execution should demonstrate:
- canonical validation succeeds
- mutation rules are accepted
- ranking objective is accepted
- candidate discovery completes successfully
- ranked candidates are returned
- runtime evidence is produced
- replay metadata is available
- execution artifacts are generated when requested
Verification should include replay after the initial execution.
Runtime Evidence
Successful execution exposes runtime evidence including:
- execution identifier
- primitive profile
- execution metadata
- ranking objective
- candidate count
- ranked candidates
- score distribution
- mutation trace
- replay metadata
- artifact references
The exact evidence surface depends on execution policy.
Replay
Replay should preserve the documented deterministic behaviour when executed using the same canonical execution contract and deterministic seed.
Replay confirms the stability of the discovery process rather than infrastructure identity.
Replay verification is described in:
→ /verification/replay-determinism
Artifacts
Typical execution artifacts include:
- ranked candidate list
- execution summary
- mutation trace
- score distribution
- replay metadata
Additional artifacts may become available as the profile evolves.
Applied Intelligence Modules
This Primitive Profile is reused across multiple Forge Intelligence Modules, including:
- Systemic Risk Intelligence
- Capital Intelligence
- Banking Intelligence
- Treasury Intelligence
- Insurance Intelligence
- Reinsurance Intelligence
- Climate Intelligence
The computational contract remains identical regardless of the consuming Intelligence Module.
Related Documentation
- /examples/search/
- /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
finance.system.systemic_fragility_search.v1 verifies a versioned Search Primitive Profile rather than a financial hypothesis.
Its behaviour is independently verifiable through canonical validation, deterministic execution, runtime evidence, replay, and artifact inspection, allowing evaluators to reproduce the same discovery workflow without relying on implementation details.
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.