Verification, not permission
OIVN returns verified, not verified, unknown or error for credentials, relationships and evidence — with a machine-readable reason. Whether an action is allowed is OVAK's decision.
OIVN
OWOS Federation
Shared verification infrastructure
Is this credential or evidence authentic and current?
OIVN verifies whether credentials, relationships and evidence are authentic, current and sufficient for a defined requirement. OVIN answers who the subject is. OVAK decides whether an action is allowed. Verified is never the same as permitted.
Credentials & evidence
Credential definitions, instances and lifecycle, backed by evidence references rather than copies of anyone else's private data.
Federated by OVIN
OVIN establishes who the human is. OIVN never mints identity and never treats app linkage as authorization.
Auditable history
Every persisted evaluation keeps its policy, reason, missing requirements and evidence references for review.
Admission ready
A clean capability for future Scan / QR / NFC flows to call — OIVN evaluates, the target service still performs the action.
Fail closed
No requirement set, no passport, or an unavailable dependency never resolves to verified.
The boundary
OIVN verifies
Whether credentials, relationships and evidence are authentic, current and sufficient, under a named requirement set, at a point in time.
OVIN identifies
Who or what the subject is, and its canonical relationships.
OVAK authorizes
Whether an action may happen, using verified facts plus policy. An OIVN result is never a permission.