LiveWhich signals does policy evaluate?
Policy signals
Thresholds, evidence quality, and the distinction between measured and unavailable.
Example tenant thresholds
policy.json
{ "liveness": { "pass": 0.86, "gray_zone": 0.72 }, "audio_visual_offset_ms": { "maximum": 50 }, "virtual_camera": { "verified_agent_required": true }, "on_insufficient_evidence": "ESCALATE"}A gray-zone result
evaluation.json
{ "verdict": "ESCALATE", "failed_rules": ["liveness.pass_floor"], "step_up": "OUT_OF_BAND_CONFIRMATION"}Policy inputs
- 01
Liveness and audio-visual sync use explicit pass, gray-zone, and block thresholds. Insufficient evidence reports as unavailable; it never silently passes.
- 02
Capture provenance becomes authoritative only when a trusted local agent signs it. Browser-only provenance remains a hint.
Verify the implementation
How presence signals are produced.
/how-it-works/presence-proof →Failure and fallback behavior.
/how-it-works/failure-behaviour →
Current limits
- Synthetic-voice policy is reserved in the contract but currently has no producer; its value is not presented as a measurement.
One next step
Continue with the executable path.