Glossary¶
| Term | Meaning |
|---|---|
| Aegis | The npm launcher and its verified native companion that provide account, gateway and Forge commands. |
| Gateway | The command that routes a coding agent's model requests through your Aegis account. |
| Forge | The deployment service and its supported customer workflow. |
| Repository origin | The Git remote that supplies the default repository. |
| Committed source | Source reachable from a commit. The default is HEAD. |
deployment_ref |
The reference printed by an accepted forge deploy; the record of that request. |
| Derived context | Environment, tenant, account, installation and app identity obtained from authorization and repository context. |
| Forge GitHub App | The App Forge uses to read one repository for deployment: installed on the owning GitHub account or organization, granted that repository, and associated with the profile, agent and repository. |
| Operator GitHub authority | The authority used for ordinary source-control operations. |
| Proof packet | Non-secret source, configuration, local HTTP and deployment records kept together. |
| Scaffold diagnostics | The fixed 0.9.4 doctor and status values, corrected by a later release. |
Naming rule¶
Use Forge for the product and Aegis for the CLI. Do not introduce another command namespace or hidden selector.