Understand the terms. Inspect the tradeoffs.

38 terms

Canonical repositoryGit

The repository where authoritative writes belong. Portable Golf uses Forgejo; native Cloudflare Golf uses Artifacts. Connected projects retain their original forge until an explicit cutover.

ForgeGit

The collaboration system around Git: repositories, issues, reviews, permissions and releases. Git object storage alone is not a complete forge.

RefGit

A named pointer to a Git object, such as a branch or tag. Conditional ref changes help prevent an old operation from overwriting a newer state.

Object IDGit

The identifier for a Git object. Golf’s plan records the object format alongside opaque IDs instead of assuming every future format has the same length.

LFSGit

Git Large File Storage keeps large file contents separately from ordinary Git history. A verified import or backup must preserve the reachable large objects too.

WorktreeGit

Another checkout associated with a repository. Worktrees share repository state, so separate directories alone are not a security boundary between hostile jobs.

QuarantineGit

A receive-time boundary for new Git objects before a push is accepted. Validation and protected-ref checks must happen before unauthorized data becomes accepted state.

Merge candidateGit

The exact proposed integration of a change with its current base. Testing only the source branch does not prove the eventual merged result passes.

Stale baseGit

A branch base that has moved since a proposal or candidate was prepared. The relevant combined candidate must be reconstructed and tested again.

Merge queueGit

A controlled order for integrating approved changes. Golf initially plans one active candidate per protected branch before considering speculative parallel trains.

CODEOWNERSGit

Repository rules for required ownership review. GitHub and GitLab formats and semantics differ; importing the text alone does not prove equivalent enforcement.

Connected originGit

A mode where GitHub or GitLab remains canonical and Golf performs qualified adjacent work through scoped APIs and events.

Execution attemptExecution

One concrete try at a job or task. A retry creates a separate attempt so logs, credentials, side effects and completion evidence are not mixed.

Runner poolExecution

A group of eligible execution capacity with declared resources, network placement and trust capabilities. A job must match those requirements before admission.

LeaseExecution

A bounded claim that an execution attempt is assigned to a runner. Expiry and fencing prevent an old runner from reporting authoritative completion after reassignment.

FencingExecution

A mechanism that excludes stale or competing writers. A queue lock inside Golf is insufficient if an unfenced external path can still mutate the same canonical state.

IdempotencyExecution

A contract that repeated requests with the same identity do not accidentally create repeated effects. It needs a defined scope and lifetime.

ReconciliationExecution

Reading observed state and comparing it with intended state after interruption, drift or uncertain responses. It avoids treating a timeout as proof of failure or success.

Transactional outboxExecution

Events recorded with the related database state and delivered afterward. Consumers still need deduplication because delivery can occur more than once.

Capability catalogExecution

The versioned list of operations and semantics a particular engine, provider or installation actually supports, including explicit blockers.

HarnessAgents

The tool that drives an agent’s execution loop and tools. Claude Code, Codex, OpenCode, Grok Build and Pi are target harness integrations in Golf.

Model providerAgents

The inference service or local model endpoint. A harness and a provider can be combined only when their actual protocols and behavior are supported.

MCPAgents

Model Context Protocol: a way for compatible clients to access tools and resources. Its authentication and permissions do not replace Golf’s authority checks.

ACPAgents

Agent Client Protocol: a session interface used by supported agents/clients. Permission requests, cancellation and resume still need explicit policy handling.

Human handoffAgents

A controlled transition in which a person inspects or takes over work while preserving changes, evidence, access boundaries and unresolved effects.

Protected previewDelivery

A temporary deployment with access control and exact output identity. The application remains untrusted code even when its URL requires login.

PromotionDelivery

Authorizing an already identified candidate or build output for a higher-trust environment. A new build or changed configuration may require new evidence and approval.

BindingDelivery

A declared connection between an application and a resource such as R2, D1 or a queue. Preview bindings should not silently provide production write access.

Resource ownershipDelivery

The explicit record of which system may change or delete a cloud resource. Golf and external IaC must not be uncoordinated competing writers.

DriftDelivery

A difference between the desired configuration and observed resources. Golf’s design reports or pauses conflicts before applying changes under a clear ownership policy.

RollbackDelivery

Restoring an earlier application version or deployment state. It does not inherently reverse database writes or recover deleted application data.

TTLDelivery

Time to live: an expiry policy for temporary links, credentials or resources. Cleanup failures still need tracking after the intended expiration time.

Opaque sessionIdentity

A random session identifier that does not expose the upstream credential to the browser. The current Golf slice hashes its stored identifier and encrypts the upstream token.

OAuth / OIDCIdentity

Related authorization and identity protocols. A repository connection, Golf sign-in and a model-provider login are separate grants even when a provider uses OAuth for more than one.

ScopeIdentity

A bounded set of allowed operations attached to a credential. Repository read access does not automatically grant creation, infrastructure administration or deployment.

SBOMOperations

A software bill of materials listing components in a deliverable. The release plan uses it alongside version pinning, signatures and provenance.

ProvenanceOperations

Evidence linking an output to its inputs and build process. It is distinct from the Git author field, a code review and a cryptographic commit signature.

RPO / RTOOperations

Recovery point and recovery time objectives: acceptable data loss and restoration time. They need measured restore drills in the actual supported deployment profile.

No matching term. Try a broader word or another topic.