Decide editorial lifecycle commands against an explicit state machine — declared states, declared transitions, and the actor roles allowed to perform each — and append the accepted ones to a local, hash-chained, append-only event log.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
npm install github:edilec/editorial-status-machineRead the result
This installs the public GitHub source; editorial-status-machine is not published to npm.
Where this check stops
Bounds are enforced and reported by name — maxFileBytes, maxCommands, maxEvents, maxDocuments, maxStates, maxTransitions, maxActors. Exceeding one is incomplete with a finding, never a quietly shorter answer.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.