ecm-capability-manager

You can manage ECM capabilities in JSONL files without the desktop UI by running a bundled Python helper that applies mutations while preserving invariants and appending audit events.

Operations supported for updating capability lifecycle data in an ECM workspace include create, update, move, retire, merge, and delete, all enforced by domain rules for type and lifecycle.

Yes, you can automate capability validation and maintenance directly in your repo by running the helper against ECM workspaces containing ecm-studio.json and re-running validation to ensure model consistency.

Auditing works when moving or merging capabilities in an ECM Studio repository by appending audit events to the JSONL data during mutations, ensuring changes are tracked and validated before writing.

The best way to safely delete capabilities from an ECM JSONL model is using the command-assisted helper, which validates changes against domain hierarchy rules and records audit events before writing.

You need an ECM workspace repo containing ecm-studio.json and ecm/*.jsonl files, and you must use the bundled Python helper to safely perform mutations while preserving structural invariants.