Evidence
A claim is not a live state.
Vyren separates design claims, implementation evidence, deployment bindings and fresh production evidence. Evidence states are explicit so a completed design cannot be mistaken for a live system.
Implementation evidence
Reproducible build baseline
Build evidence does not imply production deployment, live addresses, participation, market formation or activation.
Evidence states
Required binding and freshness conditions are satisfied.
Refresh is due before the current window expires.
Freshness window has expired.
Integrity, runtime or binding conditions failed.
Required live evidence has not yet been established.
A prerequisite prevents the assertion from progressing.
Freshness
Current-state evidence expires according to its defined window and may move through DUE or STALE.
Replay
Decision-relevant evidence retains lineage so historical state transitions can be reconstructed.
Invalidation
Runtime mismatch, scope change or failed binding can invalidate evidence immediately, regardless of age.