Architecture

Forge has four connected boundaries: repository source, authorization, runtime configuration, and deployment results.

Flow

1. The GitHub origin identifies the default repository.
2. Committed HEAD identifies the default source.
3. Authorization derives deployment context and app identity.
4. Forge App authorization begins when deployment requires repository access.
5. Forge builds and starts the app described by mithran.yaml.
6. Forge returns the deployment result.

Authority separation

The operator's GitHub authority performs ordinary source-control operations. Forge uses its App authorization only for repository access required by deployment. Forge injects no repository workflow.

Selectors

Automation can select only repository, ref, or commit. The customer cannot select environment, tenant, account, installation, or app identity.

Proof

The manifest, origin, commit, local HTTP result, and deployment result form a useful proof packet. The packet does not establish hosted behavior beyond accepted evidence.