These are the checks that keep the public sandbox honest: a change really saves and reopens, a broken save is caught, approval reaches the public view, and the exported blueprint carries what you chose. The file behind this page is a real run, not a template.
A save that keeps the initial state is detected as different
The untouched save still reads “The wheel, in motion”, not the edited “Ring market”.
pass
A tampered save is rejected and reported as recovered
A save with no contributions and a save with version 2 were both refused; each recovered to the initial sandbox instead of half-applying.
pass
Approving a pending note makes it public
The pending note left the queue and appeared in the public list (2 public, 0 pending).
pass
Hiding an approved note removes it from the public view
note-1 is hidden from the public list and still present in the owner's list.
pass
Restoring an older version does not republish a hidden note
Version 1 restored the saved name while note-1 stayed hidden and note-2 stayed pending; appearance and moderation travel separately.
pass
A restored sandbox still exports a valid blueprint
Export after restore produced preset “composition” with 2 links.
pass
Cloudflare creation and operations
Can someone go from an idea to a working, owned application, supervise real changes, recover from problems and keep improving it? The CF-COMPOSE campaign defines six required end-to-end creator journeys and nine additional real-product profiles. These are evaluation definitions, not claims that Cloudflare or App Composer has passed the journeys.
Required journey status: 6 of 6 not run. Real-product profile status: 9 of 9 not run. The original local foundation's checks are not full-journey results.
CF-J01 · not-run
Create an app and reopen the result
A creator makes a useful app for a declared task, saves and reopens it, makes a second useful change and retains owned source plus the supported saved state with truthful receipts.
CF-J02 · not-run
Preview a change with bounded delegated access
A colleague or agent creates and uses a correctly isolated preview within its grant; unrelated resources stay protected and revocation is observable.
CF-J03 · not-run
Recover an interrupted stateful change
A stale observation or lost acknowledgement does not cause an unexpected overwrite or duplicate effect; recovery restores its declared scope while retaining current restrictions.
CF-J04 · not-run
Finish a budgeted media job and reuse its output
An approved original survives transfer interruption, runs on a compatible processor and exports with intact lineage, permitted visibility and truthful cost attribution.
CF-J05 · not-run
Prove the real game or listening experience
A meaningful game or listening interaction has version-linked visual/audio evidence and independently verified state, with capture limits disclosed.
CF-J06 · not-run
Continue the project as an independent owner
An independent owner deploys the permitted source, supported state and assets in their own authorised account, rebinds credentials, completes the original task and makes a second useful change without hidden dependence on the original owner.
Show nine additional real-project evaluations
CF-R01 · not-run
New creator to useful owned application
A person without existing Cloudflare/Wrangler knowledge creates a useful multi-resource app, reopens it, makes a second change and owns the result.
CF-R02 · not-run
Phone-only supervised agent change to verified live release
An authorised phone user supervises a real agent change, preview, review, guarded release and independent live verification while their laptop is unavailable.
CF-R03 · not-run
Parallel agent alternatives with Git/Artifacts portability
Two independent agents create competing improvements from an identical immutable base, review the actual alternatives, retain all candidates and export the selected result to normal Git/GitHub.
CF-R04 · not-run
Original song to finished editable music video
A rights-cleared original song becomes a complete coherent music video with revision-linked scene plan, approved takes, audio sync, real render, saved originals and usable export.
CF-R05 · not-run
Real game and music player experience on mobile
A real browser/player completes a meaningful first-five-minute game or start/navigate/seek audio task with actual canvas, sound and performance evidence tied to its source version.
CF-R06 · not-run
Two-tenant governed operations, costs and region
Two distinct creator/tenant identities can use permitted apps and scoped agent actions, while cross-tenant access, unauthorised spending and unsupported residency claims are blocked.
CF-R07 · not-run
App-wide incident investigation and independently verified recovery
An authorised operator diagnoses a controlled multi-resource regression, proposes proportionate repair and proves usable application recovery without losing protected state.
CF-R08 · not-run
App Composer recursively rebuilds and evolves itself
An independently owned App Composer installation can be constructed through Composer's documented method, reproduce supported modules and then use the new instance to create and evolve a real third app.
CF-R09 · not-run
Evidence-led portfolio telemetry and actionable Cloudflare feedback
An operator sees which exact versions are live and which tasks actually completed across multiple independent projects, then publishes one rights-approved source-linked benchmark and one reproducible upstream improvement request.
They cover the first-time creator, phone-only agent releases, parallel Artifacts/Git workspaces, an original music video, real gameplay and listening, multi-tenant IAM and costs, full-app recovery, independent Composer self-rebuild, and public-safe portfolio proof. Each profile has a positive control, designed failures, measurable outcomes and specified source evidence.
This command runs only the provider-free local foundation. Complete journey and profile runs require separately authorised browser/provider/human evidence and are not made green by a CLI exit. Read the full protocol and test scenarios · Evaluation owner #601.
What this run does not prove
One machine, one run. There is no repeat count or variance claim yet, and no promise about other machines.
This run is the sandbox checks only. The comparison track is separate: one frozen brief, three agent configurations and three trials each. The Studio job receipts are a third record: real media jobs, not agent builds. The matched media comparison is a fourth: one still, two saved Studio clips and one blind pair.
Live checks are HTTP-level: they confirm the page responds and contains the expected text. They do not sign in, deploy or moderate anything.
No paid provider was called. Nothing here spends money or proves a provider integration.
0 blocked checks stay counted as blocked rather than passing by default.
Release timing receipts
The guarded release writes a redacted release-timing/v1 receipt. Benchmarks Studio can validate and compare those receipts without executing them: one row per repository and release path, with the total, slowest stage, three-minute target, strict 300-second limit, status and measured coverage.
Receipts stay in each repository's ignored .release/timing/ directory, so this page does not publish them. The portable pack format, refusal rules and Composer/Studio fixtures are in the ingest README. That is the known gap: the comparison is a local report today, and this page links to it rather than pretending a private receipt is public evidence.
Run it yourself
From a checkout of this repository:
pnpm bench
The runner prints the same JSON. Add --write to replace the results file this page reads. It exits non-zero only when a check fails; blocked checks are reported and counted.