Improve a playbook
Turn records, suggestions, and new versions into a learning loop.
- Preserve the outcome and problem in the case.
- If the problem will recur, create a suggestion against its base version.
- Review the suggestion against the current definition.
- Publish a corrected immutable version.
- Resolve the suggestion as applied with the result version ID.
epismo playbook suggestion create <playbook-id> \
--base-version-id <version-id> \
--title "Clarify review evidence" \
--content "Add required evidence and acceptance criteria to Step ABCD"
epismo playbook version publish <playbook-id> \
--base-version-id <latest-version-id> --request @revised.json
epismo suggestion resolve <suggestion-id> \
--status applied --result-version-id <new-version-id>Do not generalize every one-off exception, and do not apply an old-base suggestion to latest without re-evaluating it.
Improve a client copy and its source separately
Keep client-specific adjustments in the client’s independent copy. Review its records with the client team, agree on the change, and publish a version of that copy. If the lesson also improves your standard method, submit a separate suggestion against the relevant source version. Copy updates and source updates do not merge or synchronize automatically.
A suggestion is visible to the parent playbook’s current audience. Remove client names, private records, and internal references that audience should not see; explain the general rule and the evidence that can be shared. Source editors assess the proposal against their current version before publishing. If the client owns the copy, its owner or workspace managers choose a maintainer who already has edit access and belongs to that owning workspace. Team access alone does not transfer ownership or maintenance responsibility.