Core concepts
Learn the terms used for agent changes, governance, and delivery.
These terms describe the authoritative objects an external agent and human governor share.
| Term | Meaning |
|---|---|
| Organization | Owns members, roles, credentials, and Backends. |
| Backend | Stable Organization-owned boundary for Environments and delivery routing. |
| Environment | Isolated logical state whose active generation backs management and delivery. |
| Resource Revision | Immutable value, tombstone, provenance, and content hash for one logical resource. |
| Projection Manifest | Immutable set of exact Resource Revision selectors for Draft, Candidate, Release, or Published perspective. |
| Change Set | Versioned explicit changes over an exact resource manifest, or Organization scope for Backend bootstrap. |
| Candidate | Immutable validated proposal containing normalized operations, diff, impact, policy inputs, requester, and digest. It never mutates managed resources. |
| Approval | Expiring human decision bound to an exact Candidate digest, policy version, authorization version, and approver permission. |
| Operation Definition | Versioned schema, policy, quota, cancellation, recovery, queue, audit, and deterministic handler contract. |
| Operation | PostgreSQL-authoritative execution record with state, attempts, lease/fence, item outcomes, quotas, audit, and result. |
| Published manifest | Exact immutable state served by Delivery REST/OpenAPI, media, webhooks, and Context MCP. |
| Preview target | Trusted frontend destination for a short-lived Candidate-bound rendered preview. |
| Environment Alias | Stable delivery name that resolves to one Environment without granting management access. |
Structured CMS semantics still include Data Types, Components, Fields, Content, Assets, locales, Vocabularies, Terms, Releases, webhooks, image configuration, and lifecycle. External agents inspect schemas and propose these resources; the console does not provide human authoring forms.
An Organization role combines fixed PermissionKeys with explicit selectors. Effective access is additive, but one role must contain both the permission and every required matching scope. Tool visibility is a usability filter; each proposal, execution, approval, retry, and queued safe point rechecks server authority.