How Forge works¶
Forge turns committed repository source into an app deployment. It uses repository context and authorization to derive values that are not customer selectors.
Core model¶
| Input | Meaning |
|---|---|
| GitHub origin | Default repository identity. |
Committed HEAD |
Default source snapshot. |
mithran.yaml |
App runtime and exposure contract. |
| Authorization | Environment, tenant, account, installation, and app identity. |
The default deployment reads the origin and committed HEAD. Automation may select only repository, ref, or commit.
Authority model¶
The operator's GitHub authority governs ordinary source control. Forge App authorization begins only when deployment needs repository access. Forge adds no repository workflow to the app.
What the CLI does not expose¶
The customer surface has no environment, tenant, account, installation, or app identity selector.
Local proof¶
A local proof can inspect the manifest, commit, origin, and HTTP response. Such a proof does not establish hosted availability or a public package.