pragma.vision Your technology observatory

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-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
45

Public ambition and stated capability

Reported
39

Observed practitioner reporting

Verified
32

Independently supported evidence

Gap
+13

Claimed minus verified

Evidence strength Growing

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

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
6
Tier 1
0
Tier 2
1
Tier 3
5
Supports
3
Contradicts
3
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

This is the initial public reading. No earlier readiness change is recorded.

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.