Compatibility: Pactmark 0.1.x. Status: experimental. The staging result described here is anonymous, ephemeral, memory-backed and explicitly non-production.

​
What @pactmark/cloudflare is

A Web-standard HTTP subset. It exists to prove that the kernel is genuinely portable — that core, runtime, policy, evidence and agent avoid Node built-ins, environment reads and provider SDKs — rather than to be a recommended production target.
src/index.ts

​
What the staging check actually established

Health returned 200

The Worker started and served the health endpoint.

One deterministic SSE fixture completed

Streaming works through the Web-standard handler.

Error routing behaved

Problem Details responses with stable KAF_* codes.

Readiness honestly returned 503

Because the memory-backed runtime is neither durable nor production-isolated. This is the most important result on the page.
It also passed type generation and a Wrangler dry run.
Do not send secrets or customer data to any anonymous, ephemeral fixture. The public staging URL and exact deployment evidence live in the mutable v0.1 readiness record in the repository.

​
What you cannot do inside a Worker

Unsupported capability metadata fails closed rather than degrading. Specifically, do not select: You must provide platform-supported persistence and egress adapters explicitly. There is no default that quietly does the wrong thing.

​
Declaring what your agent needs

If the runtime cannot supply a required capability, KAF_RUNTIME_CAPABILITY_MISSING is raised before the run starts. An agent that needs backgroundWakeup or durableStorage will refuse to run on a Worker configured without them — which is the correct outcome.

​
When this target makes sense

1

Portability testing

Proving your agent code has not accidentally acquired a Node dependency.
2

Read-only, short, self-contained runs

Where the whole run genuinely finishes inside one request and causes no external effect.
3

An edge-facing façade

In front of a durable Pactmark deployment that lives elsewhere. The Worker terminates TLS and forwards; it does not own the run.

​
When it does not

Any run that waits for a human, causes an external effect, needs reconciliation, or must survive a process restart. Those need the durable profile — see Node and OCI container.

Portable agent example

One unchanged implementation behind Node, Vercel and Cloudflare entrypoints.

What Pactmark does not prove

Where this experimental status sits among the other boundaries.