Glossary

Organizations and authority

• Organization: root tenant and durable owner of applications and their data.
• Creator: person authorized to create or change applications and request deployment.
• Consumer: person who uses a deployed app; does not require a paid creator seat.
• Business owner: accountable for the workflow and its ongoing need.
• Technical owner: accountable for maintenance and technical review.
• Human grant: revocable authority delegated to an AI client, bound to a person, organization, apps, scopes, and expiration.
• Capability: an explicitly authorized resource or operation, such as an app DB or approved integration.
• Risk floor: minimum risk classification computed from capabilities; a creator cannot lower it.

Source and delivery

• Canonical source: the single writable source of truth: managed Forgejo or an external Git provider.
• Change set: source edits with a base/current revision, human and client attribution, build, preview, and review state.
• Source revision: immutable source identity used for a build; never a moving branch reference.
• Artifact: immutable build output and metadata addressed by digest and signed for verification.
• Deployment: an artifact and its policy, capabilities, migrations, approvals, and activation history for an environment.
• Environment: independently scoped production or preview resources within an application.
• Preview: temporary, protected deployment with an isolated database and KV namespace, synthetic data, and expiration.
• Code rollback: switches to an earlier artifact after confirming current schema compatibility.
• Data restore: recovers a snapshot into a new DB, validates it, and switches the binding after approval. It can lose writes made after the recovery point.

Infrastructure and reliability

• Control plane: trusted services owning identity, tenancy, policy, desired state, and workflows.
• Runtime/data plane: gateway, sandboxed applications, binding services, and controlled egress in a runtime cluster.
• workerd: the Workers-compatible execution engine; it must run inside a separate strong sandbox.
• Binding: API and capability to a scoped resource without exposing infrastructure connection credentials.
• RuntimeClass: Kubernetes mechanism selecting the sandbox runtime; actual implementation is a Phase 0 gate.
• Reconciliation: comparing observed resources with authoritative desired state and converging safely.
• Transactional outbox: persists an operation and its dispatch event atomically, then delivers asynchronously.
• Idempotency: repeating an operation with the same identity does not repeat its side effects.
• RPO: recovery point objective, the target maximum data-loss interval.
• RTO: recovery time objective, the target time to restore service.
• eTLD+1: registrable domain boundary; application origins must be on a different one from the control plane.
• JIT: just-in-time provisioning on a valid, authorized first login.
• SCIM: lifecycle provisioning/deprovisioning of users and groups.
• WAF-lite: intrnl's limited request policy controls; not full managed WAF parity.
• Regulated data: information subject to additional legal, contractual, or compliance controls; excluded from the v1 pilot.