A checked change moves through evidence and human review to a protected preview.
A checked change moves through evidence and human review to a protected preview. Mermaid source ↗
01 / PREVIEWS

Static and Worker previews.

Previews are separate from production and retain their source and lifetime.

Static bundles

Passing approved tests can publish a bounded Artifacts directory to private R2. A dedicated Preview Worker brokers content after Access and current Golf reader checks.

Managed Worker apps

Workers for Platforms dispatches a bounded, approved module profile. Each preview can have its own D1, R2 and Secrets Store signing material; the Outbound Worker denies unapproved Internet egress.

Browser and policy

Optional Browser Run captures script-free static HTML. The preview environment policy can restrict branch, lifetime and count. These are not arbitrary interactive app testing or universal environment support.

02 / WHAT COMES NEXT

Promotion needs its own evidence.

A preview link does not prove production readiness.

Current merge slice

Hosted native merging supports same-repository merge commits when base is already an ancestor of head. Squash, diverged branches, forks, drafts and locked targets are refused.

Protected merge

Complete trusted checks, review eligibility, protected publication and broad merge semantics remain qualification work.

Production CD

Arbitrary bindings, general application builds, production promotion, rollback and domain adoption require their own implementation and acceptance. They are not promised by the preview profile.

Make your first move.

Explore the hosted public repository, request enrollment for private workflows, or start your own portable installation.

Find your next step

31 pages and guides

Tab through results · Enter to open · Escape to close