← Back to Architecture
Architecture
Verification Flow
End-to-end accessible verification sequence.
Latest version
AGVS Draft v0.1This section is part of the current public OSCF documentation draft.
Step 1
A user attempts to access a protected action or resource.
Step 2
The system calculates an initial risk score.
Step 3
The server creates the challenge metadata.
Step 4
The client presents the challenge accessibly.
Step 5
The user performs the gesture or fallback action.
Step 6
The server validates freshness, nonce, session binding, score, retries, and replay status.
Step 7
The system decides whether to verify, retry, escalate, or block.
Step 8
Evidence is recorded and the challenge is invalidated.