pragma.vision Technology observatory & strategic foresight

Verification register Security & Identity

Readiness verdict

OpenID4VC High Assurance Interoperability Profile (HAIP) 1.0

A dated reading of what is claimed, reported, and independently verified in the current evidence.

As of
2026-08-20
Revision
1
Method
v1.3.0

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Ready

Primary summary from verified readiness

Confidence
72% · stale
Computed at
2026-08-20T10:52:21.474465+00:00
Claimed
80

Public ambition and stated capability

Reported
73

Observed practitioner reporting

Verified
63

Independently supported evidence

Gap
+17

Claimed leads verified

Evidence strength Strong

Decision

What the current evidence supports

Human editorial judgment · 2026-08-20

Adopt with guardrails

Why
It is a finalized, IP-protected standards-body spec, validated through 2025 interop testing and EC-assessed with no identified gaps — the lowest-risk DID/VC interop bet available — provided we explicitly cover its acknowledged out-of-scope areas and the format-optionality seam.
Next
Adopt HAIP 1.0 as the target profile for any verifiable-credential issuance/presentation (UCP Credential Provider): pin OpenID4VCI 1.0 + OpenID4VP 1.0, ES256/P-256, SHA-256, and standardize on SD-JWT VC; layer our own trust-list and holder-auth to cover the out-of-scope gaps.

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
11
Tier 1
0
Tier 2
4
Tier 3
7
Supports
6
Contradicts
3
Context
2
Latest observed
2026-02-25

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revisions

Initial public reading

  1. 2026-07-19 Reading moved from ready to ready.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.