Financial Runtime Review Path

Evaluate automated financial actions before live fund movement

The financial runtime profile, internally called SMERC-F, is the financial-action profile for recoverability-aware runtime permissioning. It lets a reviewer test metadata-only actions such as refunds, payment retries, treasury rebalancing, stablecoin liquidity movement, tokenized collateral movement, wallet-policy changes, transaction-limit changes, reserve-status publication, and external financial-risk signal evidence.

Run public workflow Read financial runtime guide View finance sample View finance report View external signal report Copy GitHub workflow

Evaluation Flow

A safe first review for banks, fintechs, and financial platforms

The first financial runtime review should test one workflow family with synthetic or sanitized metadata. Existing financial controls remain authoritative.

Select Workflow

Choose one area: refunds, payment retries, treasury, stablecoin liquidity, collateral, wallet policy, limits, reporting, or evidence from existing financial-risk tools.

Open guide

Describe Metadata

Provide 5 to 25 action records with risk, reversibility, containment, rollback latency, evidence, anomaly pressure, and scope.

Open sample

Run Evaluation

Use the repository workflow from GitHub Actions with read-only repository permissions.

Run public workflow

Review Evidence

Compare financial runtime posture, execution route, controls, Ref-gate failures, ledger validity, autonomy-budget impact, and any external risk signals used as evidence.

Open report

What The Sample Shows

Financial runtime governance separates authorized activity from recoverable activity

The sample intentionally mixes actions that can proceed, actions that should be constrained, and actions that should be blocked because recovery is weak or hard evidence fails. The point is not to detect crime or certify compliance. The point is to test whether automated financial actions deserve different runtime postures before execution.

Actions evaluated8 finance-specific metadata-only actions across payment, treasury, stablecoin, collateral, custody, limits, and reporting workflows.

Posture mix1 ALLOW, 4 THROTTLE, and 3 DENY in the generated sample report.

Ref-gate results2 hard evidence failures where recoverability scoring cannot rescue the action.

Ledger evidence8 valid Decision Lifecycle Ledger records preserving request, evidence, evaluation, route, and outcome placeholders.

Highest exposure example Stablecoin bridge transfer during elevated redemption pressure: DENY, BLOCK route, high irreversible exposure, weak recovery capacity.

Useful constraint example Payment settlement retry: THROTTLE with constrained execution controls instead of simple allow-or-block treatment.

Pilot signal The sample report returns strong pilot fit because it contains proceed, constrain, block, and evidence-failure cases worth reviewer labeling.

External signal proof The adapter consumes AML/KYT-, wallet-screening-, Travel Rule-, fraud-, treasury-risk-, reserve-monitoring-, blockchain-analytics-, and smart-contract-risk-style outputs as evidence without replacing those systems.

What Financial Runtime Governance Is

A pre-execution recoverability checkpoint for automated financial-action metadata.
A way to compare current allow/deny treatment against recoverability-aware posture.
A way to use outputs from existing financial-risk and compliance-style tools as pre-execution evidence.
A replayable evidence package for reviewer discussion before shadow-mode pilot approval.
A narrow extension of the SMERC runtime permission model into financial workflows.

What Financial Runtime Governance Is Not

Not AML compliance, sanctions screening, fraud detection, custody, settlement, payment execution, or trading software.
Not legal advice, compliance certification, or production financial-control attestation.
Not a replacement for IAM, OPA, payment controls, fraud systems, human approvals, SIEM, GRC, or existing audit processes.
Not a live-funds pilot until a qualified customer defines controls, scope, and accountability.

Run The Finance Sample

The finance pack reuses the general customer-evaluation runner with a financial runtime sample file. The internal profile name is SMERC-F.

python -m reference_engine.customer_evaluation \
  examples/smerc_f_customer_eval_actions.json \
  --json-output reports/smerc_f_customer_evaluation/customer_evaluation_report.json \
  --markdown-output reports/smerc_f_customer_evaluation/Customer_Evaluation_Report.md \
  --pretty

When To Move To Pilot

Move forward only if a financial-services reviewer can provide 10 to 25 metadata-only actions from one workflow, label whether each posture is useful or too strict, and define success metrics for a shadow-mode review. Existing financial controls should remain the source of truth during the first pilot.

Open financial runtime guide Shadow-mode pilot path General evaluation path