Policies
Route each request to a quality tier — Bell-test verified, vetted QRNG, or lowest latency.
How routing works
A policy names the guarantee you need, not a specific source. The egress maps the policy to a quality-tier pool, draws conditioned entropy from it through a per-request HMAC-DRBG, and records the policy plus the actual contributing sources in the receipt.
Policy reference
| Policy | Selection |
|---|---|
| quantum_verified | Bell-test / own QRNG only |
| highest_quality | best vetted QRNG mix |
| fastest_available | lowest latency |
| cost_optimized | cheapest acceptable |
| hybrid_mix | blend across tiers |
| failover | primary with fallback |
| local_only | hardware seed, no network |
| demo_mode | deterministic demo |
| qispace_native | route via QiSpace TQRND |
Fail-closed behavior
Choosing a policy
quantum_verified— key generation and any use where provenance matters most; served only from Bell-test / first-party QRNG sources.highest_quality— the default for cryptographic use; best vetted QRNG mix.fastest_available/cost_optimized— bulk or latency-sensitive workloads where tier provenance is secondary.local_only— air-gapped operation from local hardware seeds; no network sources.failover/hybrid_mix— availability-first blends across tiers.
demo_mode returns deterministic output and exists for integration testing only — never use it for keys.