Source and collaboration
Artifacts serves canonical Git. Golf mediates credentialed reads and writes and stores repository identities, current grants, issues, PRs and receipts in D1. Public reads require an explicit public-repository policy.
GOLF Product / Architecture
One workflow. Two ways to run it.
Golf shares its interface and generated API across portable Forgejo and a native Cloudflare backend. Each deployment manages its own permissions and storage.
Developer preview · capability review October 14, 202601 / NATIVE CLOUDFLARE
A developer platform built from managed primitives.
The hosted control plane runs in Workers. Artifacts owns Git; D1 stores collaboration and policy; Durable Objects coordinate work.
Execution and evidence
Queues buffer work; Workflows retain progress; Containers run approved tests and agent proposals. Private R2 retains exact-source reports and preview bundles. Optional AI never decides merge authority.
Preview and delivery
The Preview Worker brokers protected static bundles. Workers for Platforms hosts the bounded managed-app profile with its own D1/R2, signing secret and outbound policy. Access and Golf both check admission.
Workers and authority
Shared UI, Connect APIs and current repository authorization in Workers and SQLite Durable Objects.
- Access identity requires an enrolled active Golf account.
- The four Durable Object classes have different coordination/execution roles.
- A passed test never supplies merge authority.
Artifacts and D1
Canonical Git and independent forks in Artifacts; collaboration, grants and receipts in D1.
- Explicit public publication permits bounded anonymous reads.
- Immutable object reads still require current permission.
- Portable Forgejo keeps separate backend ownership.
Execution and AI
Approved source moves through durable admission and bounded Containers execution. Optional Workers AI provides Clef advice and proposal inference.
- Clef is metadata-only advisory evidence.
- Proposals use their own Artifacts fork.
- The demo proposal profile changes only calc.py.
R2 and registry
Private reports, contexts and bundles live in R2. Managed registry holds approved execution and CI-published images.
- Source and image digests stay with the evidence.
- Provider tokens remain inside the trusted broker.
- Release/attachment hosted acceptance is separate.
Protected delivery
Preview Worker and Workers for Platforms serve the bounded protected output profiles.
- Access plus current Golf reader checks.
- Private per-preview D1/R2 and signing material.
- Outbound Worker enforces app egress policy.
Operations and communication
Email Service and signed webhooks keep people connected; optional analytics and maintenance expose system state.
- Provider email acceptance is not inbox delivery.
- Cron delivery is failing; DO alarms have completed maintenance.
- Bound analytics is not successful ingestion.
02 / PORTABLE
Run the core on infrastructure you own.
Cloudflare and AI are optional for the portable deployment.
Local and Docker
React and generated Connect clients talk to the Go service. Golf uses supported Forgejo APIs, its own PostgreSQL database and an encrypted keyring. Forgejo owns its own database and Git storage.
Kubernetes
Helm packages Golf, Forgejo and optional PostgreSQL. Operators supply an exact application image, existing Secrets, storage and ingress. Extra API replicas do not create extra canonical Git writers.
Optional workers
Enrolled Docker workers, private object storage and configured agents add bounded execution. The Helm core does not automatically install the Docker runner or agent services.
03 / THE AUTHORITY BOUNDARY
Golf checks repository permission after sign-in.
Access proves identity. Golf checks the current repository grant, exact source, policy and operation receipt.
Current authorization
An Access session or platform API token is not repository ownership. Current grants and sponsorship are rechecked at defined admission and execution boundaries.
Recorded outcomes
Golf records operation keys and reads provider state back when a response is uncertain. An unknown write cannot be silently reported as complete.
Release boundary
Same-repository ancestor merges have passed hosted testing. Full protected merge, arbitrary production promotion, migration/recovery and global scale remain separate acceptance work.
Make your first move.
Explore the hosted public repository, request enrollment for private workflows, or start your own portable installation.