Skip to content

CLI Surface

The DAG command surface is organized around lifecycle intent: validate definitions, execute runs, inspect evidence, classify replay/diff, and manage portability/configuration concerns.

Visual Summary

flowchart TD
    dag[bijux dag]
    dag --> validate[validate canonicalize lint]
    dag --> execute[run replay prove verify]
    dag --> inspect[status explain node artifact-inspect]
    dag --> compare[diff why-rerun why-cache-missed]
    dag --> ops[cache adapters export import config policy]

    execute --> inputs[inputs and run settings]
    execute --> output_mode[output mode and reporting]
    inspect --> run_state[run and node state]
    inspect --> artifacts[artifact evidence]

Command Families

  • definition: init, validate, canonicalize, lint, graph-lint, fingerprint
  • execution and replay: run, replay, prove, proof-summary, verify, fsck
  • inspect and history: status, explain, node, runs ..., artifact-inspect
  • comparison: diff, why-rerun, why-cache-missed, trace-artifact
  • operations: cache ..., adapters ..., export, import, config ..., policy ...

Global Flags

  • --json: machine-readable output mode
  • --quiet: reduced human-oriented output noise

Code Anchors

  • crates/bijux-dag-cli/src/main.rs
  • crates/bijux-dag-app/src/commands/mod.rs
  • crates/bijux-dag-app/tests/cli_contract.rs
  • crates/bijux-dag-app/tests/command_surface_routing_contracts.rs

CLI Surface Rules

  • command additions require docs and contract test updates
  • classification commands must preserve explicit outcome vocabulary
  • hidden or deprecated paths should remain tested until removal is intentional

Next Reads