System status
What Kyvrane is running on.
Provider modes are reported exactly as they are. Fallback data is labelled demo and never presented as live.
LAST UPDATED 2026-09-09 13:57:37 UTC01 / SERVICE
Running on fallback data.
At least one provider is not configured with live credentials, so its adapter is serving local input. Verdicts below are still deterministic and receipts are still hash-sealed. What changes is the freshness and origin of the inputs, not the integrity of the decision.
02 / PROVIDERS
Provider modes
03 / WHAT DEMO MODE DOES NOT CHANGE
Demo data still produces a real verdict.
The policy engine is pure. It performs no network calls and consults no model. Given the same assessment input it returns the same APPROVE, REVIEW, or BLOCK with the same reason codes, whether that input arrived from a live provider or from local fallback. A receipt issued in demo mode is a real receipt of a real decision over the data it was given. It is not evidence about the live market.
The distinction Kyvrane refuses to blur: demo data can be stale or synthetic, and the interface says so on every receipt via its provenance badges. Nothing here upgrades fallback input into a live market claim.
04 / ACTIVE POLICY
Thresholds in force
Active policy version. Deterministic TypeScript, no AI in the authorization path.
Net executable edge below this is blocked.
Estimated slippage above this is blocked.
The full pipeline and every reason code are documented in the verdict reference.
05 / VERIFY IT
Run an assessment against current conditions.
The workspace evaluates a proposal against the modes shown above and returns a hash-sealed receipt. Every receipt carries the provenance of the data it used.