Flow-Center Operating Overrides

Verify a record

Each override in the backtest was sealed as a Retrospective Evaluation Record — a retrospective determination, not an authorization. Pick one, or paste a proof id, and the platform’s own verifier will recompute it: the hash chain up to that position, the Ed25519 signature, and the payload rehashed against the input hash bound into the signed core.

Backtest · no integration, no write access to any systemRun c16e6e2d-47e4-49cc-8746-9eeacaa77874150 sealed records

Select a sealed record

…or paste a proof id

What the verifier checks

Hash chain — every record from the start of the run up to this one is recomputed from its own contents and re-linked.
Signature — the record hash is checked against the Ed25519 server signature and the signing key fingerprint.
Payload binding — the stored payload is rehashed and compared to the input hash sealed into the signed core, so an edited verdict or an edited constraint trace fails verification.

The verifier is the platform’s, not this screen’s. It is scoped to the flow-center chain: a proof id from another chain returns “record not found”.