HOW IT WORKS
From routing change to reviewable evidence.
Nelvoss turns schema-defined routing records into reconstructable decision context, deterministic replay results and exportable evidence—outside the transaction path.
Four-stage workflow
Illustrative decision flow
Observe
Schema-defined historical, synthetic or approved pilot records enter the assurance layer outside the transaction path.
Reconstruct
The recorded candidate set, policy context and decision inputs are assembled into a complete decision view.
Verify
Supported decisions are replayed deterministically and compared with the original selection.
Export
Evidence Bundles and integrity-linked artifacts are prepared for independent review outside the live routing system.
Example record
- Decision
decision-example-001- Policy
policy-v3- Selection
provider-beta- Replay
- match
- Evidence
- valid
Recorded context model
Illustrative decision flow
- Decision identifier
decision-example-001- Recorded timestamp
2026-07-31T14:22:08Z- Candidate providers
provider-alpha · provider-beta · provider-gamma- Policy version
policy-v3- Decision inputs
eligibility, latency band, recorded cost components- Original selection
provider-beta- Replay result
MATCH- Evidence status
valid
Current policy versus proposed policy
Current policy selection
provider-beta
Proposed policy selection
provider-gamma CHANGED
Illustrative values only
Selection replay shows how routing logic changes. It does not establish the unobserved outcome another provider would have produced.
Evidence outputs
- Evidence Bundle samples with verification status
- Integrity-linked Assurance Chain artifacts
- Verified Decision Coverage for the supplied population
Source-data limitation
Nelvoss verifies the integrity and reproducibility of the recorded context it receives. It does not independently prove that every upstream source record is true.
Operating boundary
- No orders
- No wallet access
- No signing
- No payouts
- No transaction broadcasts