Source
Repositories, history, issues, PRs and human review.
DEPLOYMENT / DOCKER
Editable architecture diagram · Open full size ↗
Docker: what runs, what persists.
The portable core uses Forgejo and PostgreSQL. Execution workers are allocated separately.
Editable architecture diagram · Open full size ↗DEPLOYMENT / KUBERNETES
Editable architecture diagram · Open full size ↗
Kubernetes: placement and ownership.
API replicas share one forge writer and retained storage. More replicas alone do not establish HA.
Editable architecture diagram · Open full size ↗DEPLOYMENT / CLOUDFLARE
Editable architecture diagram · Open full size ↗
Cloudflare: where each part lives.
Workers own the application, Artifacts owns Git, and D1 owns collaboration state.
Editable architecture diagram · Open full size ↗CLOUDFLARE / ARCHITECTURE IN CONTEXT
Conceptual illustration · exact services on adjacent slides · Open full size ↗
The storage roles have different jobs.
Artifacts keeps Git; D1 keeps domain state; private R2 keeps outputs; the managed registry keeps images.
Conceptual illustration · exact services on adjacent slides · Open full size ↗CLOUDFLARE / ARCHITECTURE IN CONTEXT
Conceptual illustration · exact services on adjacent slides · Open full size ↗
A durable path to executable evidence.
Authorized exact-source work passes from intake through orchestration and approved compute to private reports.
Conceptual illustration · exact services on adjacent slides · Open full size ↗CLOUDFLARE / ARCHITECTURE IN CONTEXT
Conceptual illustration · exact services on adjacent slides · Open full size ↗
Advice and proposals are separate paths.
Clef sees metadata. Executable proposals work on an independent fork and return tests and a patch for human review.
Conceptual illustration · exact services on adjacent slides · Open full size ↗CLOUDFLARE / ARCHITECTURE IN CONTEXT
Conceptual illustration · exact services on adjacent slides · Open full size ↗
A running preview has its own boundary.
Static bundles and Worker applications stay protected, isolated and subject to current reader/lease checks.
Conceptual illustration · exact services on adjacent slides · Open full size ↗CLOUDFLARE / SERVICE 01 OF 26
Workers
The product entrypoint
ROLE IN GOLF
Purpose in Golf
Serves the shared Golf UI, native APIs, Git brokerage and trusted service entrypoints at custom domains. UI files are embedded in the control Worker.
How the workflow uses it
A browser, Git client or Golf CLI reaches the control Worker. Generated Connect handlers and broker entrypoints enforce the same current Golf authority.
Current operating boundary
Full native forge parity, fleet scale and SaaS onboarding remain open.
- 01Browser or CLI
- 02Worker API
- 03Current Golf permissions
CLOUDFLARE / SERVICE 02 OF 26
Artifacts
Canonical source and proposal isolation
ROLE IN GOLF
Purpose in Golf
Stores canonical Git objects/refs and independent agent forks; supports clone/push, source/history/diffs and first-slice standard PR merge.
How the workflow uses it
A private Git push/clone goes through Golf admission and short-lived brokered provider access. An agent receives a separate fork; source/history/diffs stay bound to exact objects.
Current operating boundary
Merge requires same repository and base ancestor of head; no tree merge, squash, protected merge or native repository deletion.
- 01Authorized Git request
- 02Artifacts objects and refs
- 03Source and independent forks
CLOUDFLARE / SERVICE 03 OF 26
D1
Collaboration with current permission
ROLE IN GOLF
Purpose in Golf
Stores identities, grants, collaboration, operation journals, evidence intake, environments, email outbox and encrypted execution values; separate D1 databases back Worker previews.
How the workflow uses it
An issue, PR, review, environment policy or execution intent becomes a versioned domain record. Users/grants, outboxes and readback receipts remain Golf-owned SQL state.
Current operating boundary
Recovery, broader authorization matrices and complete repository parity remain open.
- 01Authorized mutation
- 02D1 collaboration records
- 03Scoped readback
CLOUDFLARE / SERVICE 04 OF 26
Durable Objects
Different objects, different responsibilities
ROLE IN GOLF
Purpose in Golf
SQLite workspace authority serializes writes/revocations, admits bounded concurrent reads and coordinates tasks; read shards scale immutable-source reads; alarms run maintenance when Cron stops arriving.
How the workflow uses it
Workspace coordinates authority/journals and maintenance. RepositoryReads serves bounded reads; PRTestTask and PRAgentTask own the approved test/proposal compute lifecycle.
Current operating boundary
Bounded single-installation qualification, not global scale or provider availability.
- 01Workspace request
- 02Object coordination
- 03Read or task result
CLOUDFLARE / SERVICE 05 OF 26
Containers
Run the approved profile
ROLE IN GOLF
Purpose in Golf
Runs exact-source approved CI and OpenCode proposals in DO-managed Linux containers with outbound interception and verified destruction.
How the workflow uses it
Capture exact source and execute one approved Actions workflow or Python module in the reviewed image. Keep terminal status, denied requests and private output; do not infer general workflow compatibility.
Current operating boundary
One approved Actions path or Python module; Internet denied; arbitrary upstream workflows and hostile-repo isolation not qualified.
- 01Approved source and image
- 02Isolated container
- 03Private output receipt
CLOUDFLARE / SERVICE 06 OF 26
Sandbox SDK files
Stage files inside Containers
ROLE IN GOLF
Purpose in Golf
Uses @cloudflare/sandbox Files and SandboxFileError to access container files alongside raw ctx.container execution.
How the workflow uses it
The harness uses Sandbox SDK helpers to stage and read files inside raw Containers.
Current operating boundary
Golf uses raw ctx.container execution. It does not instantiate getSandbox or a Sandbox class.
- 01Selected files
- 02Sandbox file helpers
- 03Container filesystem
CLOUDFLARE / SERVICE 07 OF 26
Managed image registry
Bind an image to the job
ROLE IN GOLF
Purpose in Golf
registry.cloudflare.com holds pinned runner images and digest-verified per-job OCI artifacts; trusted Worker brokers short-lived account registry credentials.
How the workflow uses it
The approved execution image is published to registry.cloudflare.com. Authorized CI publication and image inventory retain exact digests and repository/job receipts; provider authority stays inside the broker.
Current operating boundary
Golf brokers provider authority and preserves repository/job approval. Broader image scanning, trust and retention policy remain separate acceptance.
- 01Approved image build
- 02Brokered publication
- 03Digest-bound receipt
CLOUDFLARE / SERVICE 08 OF 26
R2
Private objects with source identity
ROLE IN GOLF
Purpose in Golf
Private immutable reports, context/results, read indexes, static previews, screenshots, per-preview app files, release assets and discussion attachments.
How the workflow uses it
Reports, context, patches and preview bundles are retrieved only with current reader authority. Bounded release assets and discussion uploads retain original receipts and verified download digests.
Current operating boundary
Release and attachment slice locally verified; release max 25 assets x 256 KiB, discussion max 100 files x 256 KiB; no attachment replacement/deletion.
- 01Checked private output
- 02R2 storage
- 03Reader-authorized delivery
CLOUDFLARE / SERVICE 09 OF 26
Queues
Make admission durable
ROLE IN GOLF
Purpose in Golf
Buffers evidence IDs into Workflows with durable D1 outbox, bounded retries and reauthorization.
How the workflow uses it
The evidence queue buffers source-bound work before the Workflow consumer starts it. Stable identity and bounded handling preserve the original request across delivery retries.
Current operating boundary
Email/webhook transport currently uses D1 outboxes and maintenance, not Queues.
- 01Admitted job intent
- 02Queue and durable outbox
- 03Workflow consumer
CLOUDFLARE / SERVICE 10 OF 26
Queues dead-letter queue
Retain exhausted evidence delivery
ROLE IN GOLF
Purpose in Golf
Optional separate queue retains failed evidence deliveries and exposes failure retention.
How the workflow uses it
An optional separate queue/consumer records delivery that exceeded its normal attempts. Redrive is an operator decision with fresh authority checks; it cannot fabricate passing evidence.
Current operating boundary
Provisioning implemented on Alchemy; real dead-lettered delivery not exercised on retained installation.
- 01Exhausted attempts
- 02Dead-letter queue
- 03Operator inspection or redrive
CLOUDFLARE / SERVICE 11 OF 26
Workflows
Keep stages and outcomes together
ROLE IN GOLF
Purpose in Golf
Coordinates authorization, exact-source tests, agent proposals, report publication, previews and cleanup through durable steps.
How the workflow uses it
Durable stages reserve authority, start approved compute, retain reports and manage bounded delivery. A provider timeout remains an observed failure/uncertainty, never an assumed success.
Current operating boundary
Bounded concurrency/retention/steps; Workflows coordinate effects but do not grant authority or approve merges.
- 01Admitted job
- 02Durable execution stages
- 03Retained terminal outcome
CLOUDFLARE / SERVICE 12 OF 26
Workers for Platforms
An app preview with its own resources
ROLE IN GOLF
Purpose in Golf
Dispatches isolated PR Worker applications behind the preview gateway, with separate private D1/R2, child hostnames and an outbound-denial Worker.
How the workflow uses it
Dispatch an approved prebundled Worker module with per-preview D1, R2 and signing material. A dedicated Outbound Worker enforces the configured application egress policy.
Current operating boundary
Only approved prebundled module/schema; arbitrary builds/bindings, app cookies/WebSockets, production promotion and multi-tenant scale remain open.
- 01Approved Worker bundle
- 02Dispatch namespace
- 03Isolated preview resources
CLOUDFLARE / SERVICE 13 OF 26
Access / Zero Trust
Identity plus a Golf grant
ROLE IN GOLF
Purpose in Golf
OTP login and approved-email policies gate control/preview domains; service tokens protect machine access; Golf rechecks D1 repository grants and short-lived single-use preview grants.
How the workflow uses it
Separate human OTP and machine Service Auth policies protect the control/preview entrypoints. Golf maps verified identity to an already enrolled active account, then checks repository permission.
Current operating boundary
Access admission does not itself grant repository permission; native account lifecycle and broader identity onboarding remain open.
- 01OTP or service authentication
- 02Cloudflare Access
- 03Current Golf repository grant
CLOUDFLARE / SERVICE 14 OF 26
DNS, custom domains and TLS
Protect the actual hostnames
ROLE IN GOLF
Purpose in Golf
Provides branded control/preview URLs and per-application child hostnames; Email onboarding provisions DKIM/SPF/return-path DNS.
How the workflow uses it
Own-zone control and preview domains receive TLS and approved routing. Email sender onboarding adds DNS records. Alternate endpoints must not bypass the Access and Golf reader boundaries.
Current operating boundary
Selected approved zone/hostnames only; customer vanity-domain lifecycle is separate planned Cloudflare for SaaS work.
- 01Owned hostname
- 02DNS, routes and TLS
- 03Control, preview or email entry
CLOUDFLARE / SERVICE 15 OF 26
Secrets Store
Trusted authority, scoped value release
ROLE IN GOLF
Purpose in Golf
Keeps management/registry/analytics credentials, app signing key, webhook encryption key and execution-value AES-GCM key in trusted bindings.
How the workflow uses it
Separate secrets hold provisioner/registry/analytics authority, signing and encryption keys. Repository values are ciphertext in D1 and reach only an exact-approved native PR workflow.
Current operating boundary
Secret rotation procedure and approved external-egress broker remain open; job log masking only detects exact secret text.
- 01Encrypted configuration
- 02Trusted Worker and key
- 03Approved provider operation
CLOUDFLARE / SERVICE 16 OF 26
Workers AI
Two inference jobs
ROLE IN GOLF
Purpose in Golf
Runs optional metadata review advice on @cf/cloudflare/clef and coding proposals on @cf/zai-org/glm-5.3-flash through trusted brokers.
How the workflow uses it
Clef supplies metadata-only advisory PR evidence. GLM 5.3 Flash powers the maintained proposal harness on an independent fork; approved tests and human review remain separate from inference.
Current operating boundary
Advice is metadata-only; proposals change one approved file and are tested in an independent Artifacts fork; per-use-case model selection remains planned.
- 01Approved context
- 02Workers AI inference
- 03Advice or independent proposal
CLOUDFLARE / SERVICE 17 OF 26
AI Gateway
A policy on inference
ROLE IN GOLF
Purpose in Golf
Private authenticated inference gateway disables prompt/response logs and cache, caps 60 requests/minute and configures 500 cents/day.
How the workflow uses it
Route authenticated Workers AI calls through a private gateway, with prompt/response logging and cache disabled. The retained configuration sets 60 requests/minute and a $5/day limit.
Current operating boundary
Rate/spend-limit enforcement not exercised; admin gateway usage UI remains planned; AI remains opt-in.
- 01Authenticated AI request
- 02Gateway policy and tracing
- 03Workers AI model
CLOUDFLARE / SERVICE 18 OF 26
Browser Run
Optional static preview snapshots
ROLE IN GOLF
Purpose in Golf
Optional one-dispatch static-preview PNG capture retained privately with digest checks and current-reader authorization.
How the workflow uses it
An explicitly authorized snapshot can capture script-free static HTML with external requests denied. A historical hosted proof produced a real PNG; retained captures were not completed at this review.
Current operating boundary
Enabled in the reviewed engineering deployment, with no completed retained captures at this review. Historical hosted proof covers script-free static HTML only; full interactive QA remains open.
- 01Approved script-free HTML
- 02Browser Run capture
- 03Private R2 screenshot
CLOUDFLARE / SERVICE 19 OF 26
Analytics Engine
Optional evidence metrics
ROLE IN GOLF
Purpose in Golf
Optional sampled evidence-completion counts, report bytes, duration and observed tokens with hashed workspace index and no source/prompts.
How the workflow uses it
The deployed dataset binding accepts the implemented source path for bounded evidence metrics. Hosted ingestion/SQL readback still needs acceptance; metrics are not quota or billing authority.
Current operating boundary
Source, build and binding checks passed. Hosted ingestion and SQL readback are unverified. Metrics do not govern billing or quotas.
- 01Execution completion
- 02Metrics sample
- 03Analytics Engine dataset
CLOUDFLARE / SERVICE 20 OF 26
Workers Analytics API
A separate operational read path
ROLE IN GOLF
Purpose in Golf
Operations collector reads requests/errors/subrequests from GraphQL with a separate Account Analytics Read credential.
How the workflow uses it
Operations requests installed-Worker traffic through a dedicated account Analytics Read token in Secrets Store. The retained feed has failed collection; configured is distinct from collected.
Current operating boundary
Collection currently fails inside the Worker. The equivalent token/query succeeds externally.
- 01Operator observation
- 02GraphQL analytics query
- 03Provider response or failure
CLOUDFLARE / SERVICE 21 OF 26
Workers Logs / managed observability
Provider observations with explicit policy
ROLE IN GOLF
Purpose in Golf
Optional sampled logs help diagnose the native deployment alongside local D1 journals.
How the workflow uses it
The retained Worker reports observability enabled and logpush disabled. Invocation/log/query-string/privacy and retention settings remain separately scoped; no complete trace/export consumer is claimed.
Current operating boundary
Provider observability is enabled on the reviewed engineering deployment; logpush is disabled. Wider tracing/export and retention remain separate acceptance.
- 01Worker invocation
- 02Managed provider logs
- 03Operator inspection
CLOUDFLARE / SERVICE 22 OF 26
Cron Triggers
Maintenance with a fallback
ROLE IN GOLF
Purpose in Golf
Configured five-minute maintenance for CI intake retry, preview purge, evidence/index reconciliation, webhook/email retries and probes.
How the workflow uses it
The declared schedule has delivered no events on the retained account. Workspace keeps a five-minute alarm and runs maintenance after ten minutes without a scheduled report; it stands down when cron resumes.
Current operating boundary
Retained account receives no scheduled events; workspace DO alarm supplies maintenance fallback and cause is unresolved.
- 01Cron tick or object alarm
- 02Maintenance coordinator
- 03Cleanup and retry
CLOUDFLARE / SERVICE 23 OF 26
Workers rate limiting
Bound anonymous reads approximately
ROLE IN GOLF
Purpose in Golf
Optional per-network/location approximate throttling protects credential-less public source and clone reads.
How the workflow uses it
Credential-less public source/clone requests use per-network/location rate counts. Signed-in, credentialed and runner calls are excluded. A limiter error allows the request; this is not a global execution quota.
Current operating boundary
Signed-in, credentialed and runner requests are excluded. Limiter errors allow the request. This is not a security quota.
- 01Anonymous read request
- 02Rate-limit binding
- 03Read or fail-open policy
CLOUDFLARE / SERVICE 24 OF 26
Email Service sending
Notify the enrolled address
ROLE IN GOLF
Purpose in Golf
Consent-based own-Access-address repository subscriptions receive category-and-link notifications from D1 outbox with rechecks, bounded retries and daily attempt budget.
How the workflow uses it
Consent and repository subscriptions fill a D1 outbox. Send from the onboarded subdomain after current account/address/grant checks; record provider acceptance and bounded retry observations.
Current operating boundary
Retained installation provider acceptance verified; inbox receipt unobserved; bounces/complaints/replies/unsubscribe links remain open.
- 01Consent and current grant
- 02D1 notification outbox
- 03Email provider acceptance
CLOUDFLARE / SERVICE 25 OF 26
Signed webhooks
Deliver a committed event observation
ROLE IN GOLF
Purpose in Golf
Encrypted repository subscriptions and stable signed deliveries to approved HTTPS receivers; retained Slack test accepted.
How the workflow uses it
Encrypted subscriptions choose approved HTTPS origins. Sign a stable event document and retain receipt/attempt status. Native Slack delivery uses the accepted text shape; receivers should deduplicate.
Current operating boundary
D1 outbox/maintenance provides bounded retries, not queue-based email/webhook transport. Receiver/event/retry matrix remains bounded.
- 01Repository event
- 02Signed D1 outbox
- 03Authorized HTTPS receiver
CLOUDFLARE / SERVICE 26 OF 26
Cloudflare CLI
Provision and verify owned resources
ROLE IN GOLF
Purpose in Golf
cf supplies scoped provider discovery, setup/deploy and readback qualification; Alchemy optionally provisions equivalent reviewed native resources.
How the workflow uses it
Alchemy defines the stack; native cf supplies supported operations and deployment. Additive migration, token renewal, binding/domain readback and ownership-aware teardown keep the installation concrete.
Current operating boundary
Alchemy beta and cf beta are deployment dependencies only; private state/journals require careful ownership and teardown inspection.
- 01Declared deployment recipe
- 02Scoped Cloudflare CLI
- 03Resource creation and readback
NATIVE ARCHITECTURE
Editable architecture diagram · Open full size ↗
A platform built from managed primitives.
Each service has a specific role. Golf retains current authorization.
Editable architecture diagram · Open full size ↗