Glossary
Definitions of terms used throughout Forginate's product and documentation, alphabetized.
Approval — An explicit human sign-off gate. Documents, integration merges, and deployment plans all require approval before the platform acts on them.
Audit log — Append-only record of security- and billing-relevant actions (token creation, member changes, plan changes, approvals). Viewable by org admins at /api/orgs/:orgSlug/audit.
Auto-upgrade — Per-deployment flag: when CI is provisioned on the project repo, every push to the default branch builds a new container image and rolls the deployment automatically (status upgrading).
Build task — One unit of build work generated from the build plan; each task is executed by an AI build agent in its own factory run.
BYO provider — A "bring your own" LLM provider configuration (e.g. your own Anthropic or OpenAI key) attached to your organization, used instead of platform-managed credentials.
Clickwrap share (share agreement) — The confidentiality agreement an outside reviewer must scroll through and accept before viewing shared documents on the public share portal. Acceptances are recorded per share.
Cluster facts — Facts about your Kubernetes cluster (version, node count, ingress classes, storage classes, cert-manager presence) reported by the deploy agent and fed to the deployment planner.
Deploy agent — A small service you install in your own Kubernetes cluster. It dials out to Forginate over WebSocket using an enrollment key, reports cluster facts, heartbeats, status, logs, and telemetry, and applies the manifests the platform sends it. Forginate never connects into your cluster.
Deploy target — A place deployments can run: either an agent target (your cluster via the deploy agent) or an aws_account target (a vended AWS account). Targets belong to an organization.
Deployment — A running instance of your built application on a deploy target, with its own plan, status, endpoints, logs, and telemetry. See Deployment lifecycle.
Document — A planning artifact (product doc, section doc, design doc) produced by the pipeline. Documents have versions, an approval state, feedback threads, and can be shared externally.
Enrollment key — The bearer credential a deploy agent presents when connecting. Rotatable per target.
Improvement request — A bug report or feature ask filed against a project (by a person, or automatically from a deployment incident). Approved improvements flow into the build pipeline.
Incident — A recurring error pattern the deploy agent detected in your running app, fingerprinted and reported; incidents are auto-filed as bug-kind improvement requests.
Membership — A user's role in an organization: owner, admin, developer, or viewer.
Organization (org) — The billable tenant. Owns members, projects, deploy targets, providers, and billing. Its slug appears in every API path (/api/orgs/acme-corp/...).
PAT (personal access token) — A programmatic credential of the form fgn_pat_..., sent as Authorization: Bearer. Scoped read/write/admin, optionally org-bound and expiring; stored hashed; secret shown once.
Pipeline — The staged flow a request travels: intake → discovery → planning → architect review → build → review → QA → deploy.
Plan (deployment plan) — What the planner proposes to run on your target: Kubernetes manifests (k8s targets) or an ECS task definition + service (AWS targets), plus a plain-English summary. Nothing is applied until you approve.
Project — A software product being built inside an organization; optionally linked to a GitHub repository. Runs, documents, requests, and deployments all hang off a project.
Provider — An LLM backend (Anthropic, OpenAI, OpenAI-compatible, ...). Platform providers are managed by Forginate and metered; BYO providers are yours.
Request — The unit of pipeline work on a project (a build or improvement effort) that moves through the pipeline stages.
Run — One execution of factory work: a single Kubernetes Job/pod running the factory-runner, with live cost tracking, durable events, and logs. Runs can be cancelled and have per-run cost caps.
Run budget (cost cap) — The maximum dollar spend allowed for a run, derived from your plan and the work being done. A run that hits its cap stops rather than overspending.
Separation — Ending Forginate's management of a deployment while leaving the workload running (and, for AWS targets, beginning handover of the vended account to you). Terminal status separated.
Share (document share) — An unguessable capability-token URL that lets an outside reviewer read approved documents for one product — view-only plus comments, no login, revocable.
Teardown — Deleting a deployment's workload from its target. On AWS the ECS service is deleted but reusable scaffolding (account, cluster, roles) remains. Terminal status torn_down.
Tier (model tier) — An admin-managed mapping from a capability level to concrete models and per-million-token prices. The single pricing source of truth; runs report raw tokens and the platform prices them from the tier table.
TOC (table of contents) — The planning stage's document skeleton: the structured outline of section docs that planning then fills in iteratively.
Usage event — A metering record emitted for LLM calls (provider, model, exact tokens, cost). Rolled up into your usage page and billing.
Vended account — A dedicated AWS account created for your org under Forginate's AWS Organization, backing an aws_account deploy target. Costs are passed through with a service margin; on separation the account can be handed over to you.
Vibe editor — The inline AI document editor (the chat-editor service): a chat panel that streams an LLM turn and proposes concrete document patches you accept or reject.