Financial services

Control evidence and valuation provenance for regimes that ask "prove that was the number, then"

Controls and valuations are challenged after the fact

SOX-era control evidence and Basel-era model governance share one demand: when a valuation, a reconciliation, or a control execution is challenged, the institution must show the record as it existed at the time — which method computed the number, from which inputs, and that nothing was quietly restated since. The systems holding those answers are the systems under question, and multi-party transactions add a second demand: exact attribution, where a settlement clears against multiple expectations and every unit must be accounted for. FORAY carries both: each record's commitment is anchored to a public chain so later edits are detectable, and the wire's allocation law requires settlement attributions to sum exactly, as decimal values — binary-float tolerance is forbidden by rule, not by convention.

Trades, funding, origination, and computed judgments

An ISDA-style agreement or facility is an Arrangement. A valuation or accrued-interest computation is an Accrual with its method, inputs, and output declared. A payment expectation is an Anticipation; a settlement leg is an Action. The worked examples carry the sector's core patterns:

  • FX Spot: USD/JPY With Two Settlement Legs — a two-legged settlement where each leg carries its own currency at element scope, and the yen leg's zero-decimal allocation is exact by the decimal law, no special casing.
  • Overnight Repo: Opening and Closing Legs — collateralized funding whose closing settlement is exact to eleven significant digits: the wire's decimal profile carries it byte-deterministically, and the allocation sum must match it exactly.
  • Auto Loan: Origination Through First Payment — a full origination chain: the credit agreement, the computed schedule, the expected installment, and two settlement Actions referencing backward.
  • Combined Payment: One Action, Two Allocations — one wire clearing two expected payments with exact attribution.
  • Depreciation: Accrual-Only Adjusting Entry — the formula-block discipline every declared computation uses: computation method, a salted formula identifier, named inputs, numeric output. For a valuation model under governance review, the declared method is fixed at origination and provable unaltered years later.

What a holder keeps

The anchor is permanent; the holder's ability to use it is exactly as durable as their custody. For every anchored record the institution keeps the exact record bytes, the full anchoring response (salt and window material), the formula packages behind declared computations — losing a formula package orphans the formula identifier the way losing a body orphans an anchor — and the anchor reference. The Evidence Custody Model states the package, retention discipline, refresh cadence, and succession expectations; the custody sheet is the completeness instrument a second party can re-verify.

What verification looks like

Verification is holder-side and requires no access to DUNIN7. The proofs page shows the full procedure against live mainnet anchors — body, salt, recomputed commitment, on-chain match — and the Verifier Specification defines it for any independent implementation, with an offline conformance suite behind it. A validation PASS attests conformance to the ruled shape; the trust model is the precise statement of what every FORAY proof covers.