Glossary

Use this page to align user, admin, and security-review language across Forge docs. Product pages say Forge. Command and manifest surfaces use MAP where MAP is part of the command, workflow, variable, or API identifier. Use the names exactly as shown in commands and files.

Term	Meaning
Forge	Mithran's app deployment and serving platform. Forge snapshots source, reviews deploy inputs, builds apps, places runtime capacity, and routes traffic through the Forge edge.
MAP	The command/API namespace used by deploy surfaces such as map, map-deploy.yml, MAP_INSTALLATION_REF, and apiVersion: map.mithran/v1. Treat these as identifiers to use exactly as documented.
aegis	The installed CLI entry point for setup, sign-in, doctor checks, and Codex-related commands.
map	The deploy-related CLI command group used for onboarding, doctor checks, deploy, and publish.
Account context	The customer setup context that supplies the setup link, GitHub App, control-plane endpoint, hostname pattern, and tenant/account refs used by Forge. See Account context and app environments.
Forge GitHub App	The GitHub App that reads source from repos the customer grants. Use the App shown by the customer setup link.
GitHub organization	The GitHub account or organization that owns repos and GitHub App installation settings.
Repository grant	The set of repos the customer grants to the Forge GitHub App. Source fetch can only use granted repos.
Tenant	The customer authorization boundary Forge checks for app, deploy, and access activity.
Account	The customer workspace or business account under a tenant.
Project	The grouping that ties apps and repos to a product area or owner under an account.
App	A Forge-deployed service with a mithran.yaml, app ref, runtime, and route.
App ID	The DNS-friendly value in metadata.app_id. For self-service apps, keep it aligned with the app ref label, usually app:<metadata.app_id>.
App ref	The route and version identity used by Forge, such as app:my-app. Hostnames are built from this ref.
mithran.yaml	The app manifest committed at the repo root. It describes app identity, runtime startup, environment mapping, and public-edge exposure.
Capability	A service declared in capabilities[]. These docs focus on HTTP services.
Runtime	The managed execution environment where the customer app process runs after build and placement.
App environment	An app-level deploy target such as preview or production. It can appear in app_env, deploy status, route aliases, and map deploy --env. Do not confuse it with account context.
Preview app environment	An app environment commonly used for branch-based builds before production release.
Production app environment	The app environment reached by release/* branches or release/* tags in these docs.
Deploy	The act of asking Forge to review, build, place, and route a specific commit or ref. Built-in deploys start from GitHub App webhooks; operators and automation can request deploys directly with map deploy. Deploy can succeed before the clean public host is moved to that version.
Publish	The act of pointing an app's clean public URL at a reviewed version that reached Succeeded or Promoted.
Version	An addressable app build recorded by Forge after a successful deploy. map versions <app> lists versions and shows which one is published to the clean public URL.
Clean public URL	The app hostname users open after publish. In production, an app served as app:my-app uses https://my-app.apps.mithran.cloud/.
Public edge	The Forge edge path that serves app hostnames and applies exposure behavior.
public exposure	public_edge.exposure: public. Forge serves the app route without platform auth.
protected exposure	public_edge.exposure: protected. Forge keeps platform auth required before traffic reaches the app.
none exposure	public_edge.exposure: none. Forge keeps the non-public route shape.
Route	The mapping from an app hostname to the app version and runtime target.
Route propagation	The short interval between a deploy programming the edge and the hostname being reachable everywhere. During that interval, unknown_hostname can appear.
Source fetch	The control-plane step that reads a granted repo through the Forge GitHub App so Forge can build the requested commit.
GitHub App webhook	The default deploy trigger. GitHub sends it when an onboarded repo pushes a built-in deploy ref such as refs/heads/main, refs/heads/release/*, or refs/tags/release/*.
Deploy workflow	.github/workflows/map-deploy.yml, the optional GitHub Actions workflow used for custom-CI deploys.
Control plane	The Forge service that receives deploy requests, checks onboarding, snapshots source, reviews deploy inputs, coordinates build/runtime/route work, and returns status.
Review gate	The control-plane review step that must pass before Forge builds and routes a deploy.
Escalation packet	The customer-collected evidence needed for escalation: repo, app hostname, refs, manifest, deploy status, control-plane response, observed error, and custom-CI workflow run when applicable.

Naming rules

• Say Forge when referring to the product, platform, edge, control plane, security model, or docs path.
• Say account context when referring to the setup link, GitHub App source access, API endpoint, hostname pattern, and tenant/account refs used for a customer account.
• Say app environment when referring to app_env or map deploy --env values such as preview or production.
• Use Account context and app environments when a page needs to explain both values.
• Keep MAP where it is part of a command, workflow file, environment variable, API version, or GitHub App display name.
• Do not rename map commands, MAP_* variables, map-deploy.yml, or apiVersion: map.mithran/v1 in customer repos.
• Use deploy for creating or re-running a reviewed version, and publish for moving the clean public URL to a reviewed version that reached Succeeded or Promoted.