Deployment results and proof¶
A deployment request produces a result you can retain with the commit it describes. Version 0.9.4 is honest about what it does and does not report.
What the command returns¶
On success the human form prints one line:
aegis forge deploy --json prints {"ok": true, "result": …} on stdout. The
result is a redacted evidence summary with fixed keys: schema_version,
caller_request_ref, deployment_ref, execution_intent_digest,
runtime_session_ref and lab_preflight_etag, plus source_sha,
manifest_digest, target_definition_digest and a target_ref that is
always null. It is not a passthrough of the service response, and it
carries no application address or runtime state.
Keep the reference with the repository and commit. It is the record of the request, not a promise about runtime.
What 0.9.4 does not report¶
The reduced CLI has no command that returns the deployed application's
address, no hosted status command, and no rollback or versions command.
forge status, forge versions and forge rollback are refused as unknown
commands. Do not construct an address from the repository or app name, and
do not read a successful deploy line as proof that a route is serving.
The human-readable success line reports the reference alone; with --json
you also get the redacted evidence summary. Neither carries runtime state,
so ask your Forge administrator rather than guessing a URL or status.
Keep useful diagnostics¶
Retain these non-secret facts when investigating a deployment:
- The GitHub origin and the selected repository, ref or commit.
- The manifest and the relevant source diff.
- The local HTTP result from running the app on your machine.
- The
deployment_ref, the command's exit status, and any refusal code.
These records describe one request. A local response and an accepted reference do not establish long-term availability or authorize another operation.
Investigate a failure¶
Read the refusal code first. forge_source_unavailable and
forge_intent_invalid exit 64; the other Forge refusals exit 1. The
code, not the number alone, tells you which stage refused. See
Troubleshooting for each code and its
first inspection.
Historical qualification records¶
The Aegis 0.9 journey retains dated installation, sign-in, delegation and deployment observations from an earlier surface. It is a historical audit record: its package identity, legacy command forms and deployment references describe that audit, not your application or the current CLI.