Skip to content

Admin operations runbooks

These runbooks describe administrator review actions around the reduced customer surface. They add no command and no selector; the customer commands are in CLI reference. Runbook steps that mention the full-product .pkg or protected agent runtime apply only to that separate product.

Prepare an account

  1. Provide the approved Aegis distribution.
  2. Ask the operator to complete local account setup.
  3. Record the repository origin and intended app source.
  4. Review the manifest and local HTTP contract.

Authorize repository access

  1. Identify which of the four facts is missing: Aegis identity, App installation, repository grant, or association with the profile, agent and repository.
  2. Install or approve the Forge GitHub App on the owning account or organization when that is the gap. Do not repeat a permission change when only the association is missing.
  3. Associate the existing App for the exact profile, agent and repository.
  4. Keep ordinary source control under the operator's GitHub authority.
  5. Record each state without credentials.

See Connect GitHub for the state-by-state guidance.

Review a deployment

  1. Inspect the origin and selected commit.
  2. Inspect the manifest and source diff.
  3. Read the deployment result.
  4. Classify failures as source, configuration, build, runtime, or route failures.
  5. Preserve the non-secret proof packet.

Boundary

Environment, tenant, account, installation, and app identity come from authorization and repository context. Automation may select only repository, ref, or commit. Forge injects no repository workflow.

Read Deployment results and proof, Production checklist, and Support.