pragma.vision Your technology observatory

Verification register Compute & Web Infra

Readiness verdict

Vercel eve

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
60

Public ambition and stated capability

Reported
54

Observed practitioner reporting

Verified
46

Independently supported evidence

Gap
+14

Claimed minus verified

Evidence strength Critical

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Wait for stronger evidence

Why
Strong vendor proof points (29% of Vercel deploys agent-triggered, 100+ internal agents, 92% support-ticket resolution) and Apache-2.0 open source, but it is explicitly beta with API churn and deep Vercel lock-in; our stack runs on Cloudflare Workers, so adoption would fight Rule #9 free-tier and existing infra.
Next
Spin up a throwaway eve agent for one internal non-critical workflow to evaluate durable-session ergonomics, but do NOT put it on the Contract Spine or any checkout/protocol path until GA

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
7
Tier 1
0
Tier 2
2
Tier 3
5
Supports
4
Contradicts
3
Context
0
Latest observed
2026-06-23

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.