Glossary

This glossary is the source of truth for Infrared's vocabulary. The product, the API, the CLI, the docs and the AgentRoles all use these terms and only these terms. If a word is in the "never say" column, replace it.

Change management

Term	Meaning	Never say
Product	The unit Infrared builds, releases and manages change for: one or more repos released together. The Product resource.	project, app (when you mean the whole Product), service
Release	A versioned set of Changes to a Product, cut together and promoted together.	version bundle, drop, sprint
Change	One unit of work moving toward a Release: an issue plus the pull request that implements it, whoever wrote it.	ticket (for the whole unit), task, job
AgentRole	A defined job an agent performs: its mission, triggers, evidence, guardrails, permissions and the org's opinions. The AgentRole resource.	persona, bot, agent type, skill
AgentWorkflow	An ordered set of steps (AgentRoles, human gates, promotions, automatic actions) that a Change or a scheduled job moves through. The AgentWorkflow resource.	pipeline, flow definition, playbook
AgentWorkflowRun	One run of an AgentWorkflow, with each step's phase, verdict, usage and evidence. The AgentWorkflowRun resource.	pipeline run, job run, execution
Opinion	A named, editable piece of guidance inside an AgentRole that an org can change or switch off.	rule (unless it is enforced), prompt
Verdict	A step's final word, such as VERIFIED, MERGE WITH FOLLOW-UPS or BLOCK.	result, score
Evidence	A proof a step captures and attaches to its AgentWorkflowRun: a screenshot, video, report, log, comment, diff, SARIF file, metric or document.	artifact (ambiguous), attachment
Dead-letter	Hand work an agent cannot finish to a named human, with the run paused at that step.	fail silently, drop
Catalog	The default set of AgentRoles and AgentWorkflows seeded into every new org, versioned (for example v0.1.0). Not the same as the gitops catalog.	template library
Tailoring	Rewriting an org's AgentRoles from analysis of its repos (phase 5).	fine-tuning

Tenancy

Term	Meaning	Never say
org	The tenancy and RBAC boundary in Infrared. Each org's resources live in the namespace ir-org-<org>. The Organization resource.	tenant, workspace, account
platform org	The one org that administers the control plane itself, created by the setup wizard.	root org, admin tenant
team	A group of people and bots inside an org, used for ownership and escalation handles like @platform/reviewers.	squad, group

Clusters and gitops

Term	Meaning	Never say
management cluster	The cluster Infrared runs on. It runs Argo CD and manages itself and every workload cluster.	hub, control cluster, admin cluster
workload cluster	A cluster that runs Products' zones, managed from the management cluster.	spoke, child cluster, runtime cluster
cluster template	A tagged module in infrared-iac-modules that builds a cluster, for example aws/k3s-node.	blueprint, cluster recipe
gitops repo	An org's git repo that holds the desired state of its clusters and Products. Infrared creates, hydrates and bootstraps it. The GitopsRepo resource.	config repo, deploy repo, manifests repo
gitops catalog	The component definitions (cert-manager, kpack, Argo CD and others) that the gitops template hydrates into a gitops repo. Not the AgentRole catalog.	charts folder, addons
registry	The registry/clusters/<cluster>/ tree in a gitops repo: one folder per cluster listing the Applications that cluster runs.	inventory, cluster list
app-of-apps	The Argo CD pattern where one root Application points at the registry and creates every other Application.	root chart, umbrella app
Application	An Argo CD Application: one component or Product zone synced from git to a cluster. Capitalized.	app (lowercase, for the Argo object), deployment
AppProject	An Argo CD AppProject: the boundary for which repos and clusters a set of Applications may use.	project
sync wave	The Argo CD ordering annotation. Lower waves sync and become Healthy before higher waves start.	phase, stage, order
Synced / OutOfSync	Argo CD's sync status: whether the cluster matches git. Always verbatim, with an icon and the word.	in sync, drifted, up to date
Healthy / Progressing / Degraded / Suspended / Missing	Argo CD's health status, verbatim, with an icon and the word.	green, red, broken, OK, down
environment	A class of zones with the same purpose: Pre-release or Release.	stage, tier
Pre-release	The environment for zones that run candidates, such as rc.	staging, dev
Release (environment)	The environment for zones that serve users.	production (as a label), prod
zone	One running instance of a Product on a cluster, such as rc or prod-us-east, belonging to an environment.	environment (when you mean one instance), namespace, stage
promotion	Moving a Product's pin from one zone to the next through a pin PR.	deployment, rollout, push
pin	An exact image reference, tag@sha256:<digest>, recorded in the gitops repo. A pin PR changes one.	version (alone), latest, floating tag
metaphor	The sample app Infrared uses to demonstrate and test delivery end to end.	demo app, hello world

Build (kpack)

Term	Meaning	Never say
builder	A kpack builder: the ordered buildpacks and stack used to turn source into an image.	build image, Dockerfile
ClusterStore	A kpack resource listing the buildpacks available to builders cluster-wide.	buildpack registry
ClusterStack	A kpack resource naming the build and run base images.	base image set
Image	A kpack Image resource: one app's source-to-image definition. kpack rebuilds it when source, buildpacks or the stack change. Capitalized when you mean the resource.	build config, job

Components

Term	Meaning	Never say
Infrared	The control plane as a whole.	the platform (as a name), IR
infrared-operator	The controllers and CRDs. The CRDs are Infrared's data store.	backend, server
infrared-api	The REST API at /v1, described by OpenAPI.	backend
infrared-cli (ir)	The command-line client.	tool
setup wizard	The seven first-run steps in the UI that take a fresh install to Ready.	onboarding, installer