HOWTO: Trace the Execution Chain of a HyOps Run¶

Purpose: Follow a HybridOps run end to end using the run record and structured logs to understand what executed, in what order, and why any step succeeded or failed.

Difficulty: Intermediate

Track: Contract-Driven Automation

Overview¶

The execution chain of a HybridOps run spans CLI invocation, module and profile resolution, preflight, ordered step execution, and run-record capture. Each stage leaves a structured trace. This HOWTO teaches you to navigate that trace fluently, whether you are debugging a failure, auditing a change, or reviewing a run you did not execute yourself.

1. The Run ID as Your Anchor¶

Where the run ID appears: CLI output, run record, log directory.
Using the run ID to locate all records from a single execution.

2. Module and Profile Resolution¶

Which module version was resolved and from where.
Profile attachment and policy version used.
Dependency graph walk: which upstream modules were checked.

3. Preflight Trace¶

Input resolution log.
Environment check sequence and outcomes.
Contract digest confirmation.

4. Step Execution Trace¶

Step ordering from the module contract.
Per-step action log paths.
Timing data and its use in performance baselines.

5. Run-Record Collection Trace¶

Which steps produced supporting records.
Record path resolution and timestamp interpolation.
Run-record cross-referencing across a multi-module run.

6. Diagnosing Partial Runs¶

partial outcome: which steps ran, which did not.
Left-behind state: how to identify and remediate.
Safe re-run vs rollback decision.

References¶

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