Daily eiq2 sovereign data market intelligence

Executive summary

What changed

• The UK now reports 46 providers and 64 certified digital-verification services across distinct identity, attribute, holder, orchestration, and component roles; a machine-readable register is planned for Winter 2026.
• Arizona’s Indigenous Data Sovereignty Policy operationalizes collective authority through purpose-bound agreements, explicit permission, provenance, delegated access, dynamic consent, and return or reconnection obligations.
• The AMA’s planned SNOMED CT-to-CPT mapping initiative exposes a key health-data bottleneck: valid APIs and consent do not resolve incompatible clinical, administrative, and policy meanings.
• Veea’s “sovereign data fabric” launch shows category compression: local inference and jurisdictional control matter, but locality is not the same as rights-aware movement.

Strategic read

Why it matters for eiq2

• The object model needs a broader principal. A participant-only wallet story fails institutional, delegated, community, and collective-governance cases.
• External authority has to stay visible. Each transaction should identify the trusted source, trust registry, semantic authority, delegated scope, and status or expiry check.
• Identity is an input, not the whole control layer. Knowing who may act does not establish data truth, permission, acceptable purpose, or downstream-use conditions.
• Differentiation must be operational. eiq2’s claim is how minimum verified data or governed proofs move with permission, provenance, conditions, and a record of use—not merely where data lives.

Operator priorities

Actions for Dave / Melanie

1. Revise the atomic transaction schema before its next investor or product-diligence use. Add principal/rights-holder type, external trust registry, semantic authority, delegated scope, and return/reconnection obligation.
2. Test the revision against one prior-authorization transaction: source clinical fact → terminology mapping → payer policy decision → permission → minimum verified object → exception/retention handling → usage record.
3. Define a registry-adapter pattern for identity, organizational authority, credential status, and service certification instead of rebuilding those functions.

Risks and monitored signals

Watch items

• Category compression: “sovereign data” increasingly means edge locality, jurisdiction, identity, or wallets. The deck needs to show the distinct governed-movement controls.
• Semantic failure: a technically valid FHIR payload may still be unusable when clinical, administrative, and policy meanings diverge.
• Status and inclusion: the OfDIA machine-readable register and AMA mappings remain planned; assisted and exception paths also matter because fewer than half of surveyed UK providers reported non-digital support routes.