C8 Ops CLI

Low-level commands do work. c8volt ops finishes workflows.

The ops command group is the operator-facing layer for predefined Camunda playbooks. Each command composes lower-level c8volt behavior such as discovery, tree traversal, delete planning, incident lookup, confirmation, waiting, JSON output, and report writing. The goal is not to hide the primitives. The goal is to make the whole operational outcome repeatable. Discovery-oriented ops workflows page through all matches by default; --batch-size tunes page size only, and --limit intentionally caps the frozen scope. Human, JSON, and Markdown output identify whether discovery completed or was user-limited.

Playbook Index

Workflow Command Use when
Execute Smoke Test c8volt ops execute smoke-test You need to prove a profile can connect, deploy, run, walk, and clean up.
Execute Retention Policy c8volt ops execute retention-policy You need an auditable cleanup of old finished process instances.
Purge Orphan Process Instances c8volt ops purge orphan-process-instances You need to find and delete orphan child process instances.
Purge Process Instances With Incidents c8volt ops purge process-instances-with-incidents You need to delete process-instance families selected from incident filters.
Purge All Process Definitions c8volt ops purge all-process-definitions You need to delete selected process-definition versions after impact planning.
Repair Incident c8volt ops repair incident You need to repair incidents selected by key, stdin, or incident filters.
Repair Process Instance c8volt ops repair process-instance You need to repair active incidents discovered from selected process instances.

Shared Shape

Every ops playbook page follows the same structure:

  • the problem the command solves
  • when to use it
  • the command at a glance
  • the lower-level c8volt commands it composes
  • an ASCII workflow diagram
  • what --dry-run does
  • what real execution does
  • report behavior
  • a VHS demo script
  • failure and safety notes

Safety Model

Ops commands should feel boring in the best way: they discover, freeze, plan, validate, execute, verify, and report.

discover candidates
        |
        v
freeze target set
        |
        v
build c8volt plan
        |
        v
validate safety
        |
        +--> --dry-run: report plan, mutate nothing
        |
        v
confirm or run under automation
        |
        v
execute lower-level action
        |
        v
wait and verify
        |
        v
write audit report

Reports And Demos

Ops reports should be stable structured data first, then rendered to Markdown or JSON. Markdown is for operator review. JSON is for agents, CI, and audit pipelines.

Demo recordings live as VHS scripts under demos/vhs/. The scripts intentionally show preview-first usage before deletion, cleanup, or repair execution.

Table of contents