—Reference · Glossary
Glossary.
Definitions for vocabulary used across the Axiom platform — operational, AI, cloud, and ReleaseOps terms.
- Action proposal
- A persisted request for an agent tool call. Low-risk reads can complete inline; medium- and high-risk writes wait for an explicit administrator decision.
- Approval gate
- The server-side boundary that prevents a proposed write from executing until an authorized workspace administrator approves it.
- Audit record
- The stored record of a tool call, including the requested action, risk, status, actor, and outcome. Audit evidence is not an independent compliance certification.
- Conversation
- A workspace-scoped Agent thread whose messages preserve the context for a sequence of governed requests.
- Deployment target
- The configuration that maps an Axiom environment to an AWS region, ECS cluster, ECS service, and OIDC role.
- Environment
- A named workspace tier such as development, test, or production. Targeting production raises the risk of write actions; it never lowers it.
- GitHub App installation
- The GitHub authorization boundary used to discover repositories and mint a short-lived token scoped to one selected repository.
- Governed AI call
- An AI request allowed only after the workspace passes both the AI-credit check and provider-policy check. Both checks fail closed.
- OIDC
- The short-lived identity exchange used by the tenant's GitHub Actions workflow to assume its configured AWS role without storing an AWS access key in Axiom.
- Provider policy
- Workspace configuration that determines whether AI is enabled and which configured providers and models may be used.
- Repository scope
- The rule that GitHub credentials are minted for one selected repository rather than exposing a broad organization token to an action.
- Rollback
- For the released ECS workflow, restoration of the task definition captured before deployment when the new service does not reach steady state.
- SCIM lifecycle preview
- A safe preview of proposed identity lifecycle effects. It does not perform live provisioning or prove that enterprise sign-in is active.
- Steady state
- The ECS service condition the deployment workflow waits for before reporting success. Failure triggers the workflow's rollback path.
- Workflow dispatch
- The GitHub API action that starts the tenant-owned Axiom ECS deployment workflow with the selected environment and target configuration.
Still blocked?
Include the failed step and error. Never send a password, token, or cloud secret.