Did the clocks move forward?
Source, event, receive, and decision timestamps must parse, remain ordered, and stay inside explicit latency limits.
Deterministic market-data QA
Can this market event defend its own decision?
Paste a synthetic evidence envelope. The inspector reconstructs four clocks, follows every lineage hop, tests confidence and state, then explains each failure with the values that caused it.
Interactive inspector
Test the envelope, not the narrative
All checks run locally in JavaScript. Samples are fictional and intentionally safe to edit.
1
LOCALSynthetic envelope
Use synthetic data only. The validator never sends or stores the text.
Decision policy thresholds
2
Evidence verdict
Source → event—
Event → receive—
Receive → decision—
Confidence—
Run the inspector to map the four clocks.
- No checks have run yet.
Evidence model
Four questions before a price can become a decision
The format is intentionally compact. It is an audit exercise, not a universal schema.
Can every transformation be named?
Each hop needs a unique stage, an actor, a timestamp, and a SHA-256-shaped input reference. Hops cannot travel backward.
Was uncertainty preserved?
Confidence is a bounded number, not a slogan. The policy threshold is visible and can be changed before evaluation.
Does the claimed outcome match the evidence?
An envelope marked accepted cannot hide a broken clock, missing lineage, or policy failure. The state is checked last.
