Verification register Compute & Web Infra
Current reading
Readiness band and full integer triple
AI-assisted assembly · derived results
Readiness band
Watch
Primary summary from verified readiness
- Confidence
- 56% · fresh
- Computed at
- 2026-08-20T10:55:55.912838+00:00
- Claimed
- 70
- Reported
- 59
- Verified
- 49
- Gap
- +21
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed leads verified
Evidence strength Critical
Decision
What the current evidence supports
Human editorial judgment · 2026-08-20
Proceed with caution
- Why
- The zero-standing-access + typed-capability-binding architecture matches where agent authorization is heading and the stack is already Workers-native, so evaluation cost is low; but the upstream README's own early-access/"many rough edges" status, the COMING SOON self-host path, and Cloudflare's own admission that multiplayer access control is not solvable end to end today make it unsafe as a load-bearing dependency yet.
- Next
- Deploy a pinned cloudflare-os-starter release into an isolated Cloudflare account, wire exactly one read-only gatekeeper against a low-sensitivity internal system, and compare its typed-binding grant model against the existing MCP OAuth entitlement path before any production surface depends on it.
Constraints
Blockers
No named blocker is present in the current public projection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 7
- Tier 1
- 1
- Tier 2
- 1
- Tier 3
- 5
- Supports
- 2
- Contradicts
- 4
- Context
- 1
- Latest observed
- 2026-08-10
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Initial public reading
- 2026-08-10 Reading moved from watch to watch.