pragma.vision Technology observatory & strategic foresight

Verification register Compute & Web Infra

Readiness verdict

WASI P3 on wasmCloud

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

Emerging

Primary summary from verified readiness

Confidence
62% · stale
Computed at
2026-08-20T10:53:04.065517+00:00
Claimed
45

Public ambition and stated capability

Reported
39

Observed practitioner reporting

Verified
32

Independently supported evidence

Gap
+13

Claimed leads verified

Evidence strength Growing

Decision

What the current evidence supports

Human editorial judgment · 2026-08-20

Wait for stronger evidence

Why
P3 async is a major capability and its underlying spec is now stable, but wasmCloud's integration is explicitly preview-quality, flag-gated, RC-based, and limited to Rust HTTP - not safe to build production paths on yet.
Next
Track wasmCloud issue #5028 and the Q2 production-readiness milestone; revisit once P3 is enabled by default (the spec itself stabilized June 11 2026) and TypeScript HTTP components are stable, then run a backpressure/long-stream load test.

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
12
Tier 1
0
Tier 2
2
Tier 3
10
Supports
6
Contradicts
6
Context
0
Latest observed
2026-06-11

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 emerging to emerging.

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.