HOWTO: Run HyOps Preflight and Interpret the Report¶

Purpose: Invoke the HybridOps preflight check, interpret all sections of the output report, and resolve common preflight failures.

Difficulty: Intermediate

Track: Contract-Driven Automation

Overview¶

Before HybridOps executes any module, it runs a preflight phase that validates the full execution contract: inputs, environment state, dependency graph, and module version compatibility. This HOWTO teaches you to read that output fluently: turning a wall of structured text into a clear go/no-go decision.

1. Invoking Preflight¶

Preflight-only mode.
Dry-run mode.
Targeted preflight for a specific profile or pack.

2. Report Structure¶

Input validation section.
Environment reachability checks.
Dependency graph and resolution log.
Contract digest and version pin.

3. Reading Input Failures¶

Missing required keys.
Type mismatches.
Secret resolution errors.

4. Reading Environment Failures¶

Unreachable hosts and how to distinguish network vs authentication failures.
Dependency module not yet applied.
State drift detected.

5. Resolving Version Mismatches¶

Contract version pinning.
Compatible version ranges.
Forcing a version override and when it is appropriate.

6. From Preflight to Run¶

Confirming a clean preflight.
Passing preflight output as a run record records.
Attaching the contract digest to the change ticket.

References¶

License: MIT-0 for code, CC-BY-4.0 for documentation unless otherwise stated.