What problem does it solve?
It solves the problem of getting an approved AI-produced artifact made externally visible when no playbook-specific submit workflow exists, without guessing and risking incorrect external actions.
Core Features & Use Cases
- Identifies the approved artifact source from the latest draft trail entry and its
artifact_refs.
- Submits external drafts when possible by creating a preview/hold in the operator-wired external system via MCP, and records returned references.
- Holds locally when submission isn’t appropriate by storing the artifact payload for later use by the
commit stage.
- Escalates safely when it can’t proceed by setting
awaiting_operator with a stuck reason and recommended next action.
Quick Start
Ask the system to run the submit step for playbook other, and it will either create an external draft/preview or record the artifact for commit depending on what the artifact_refs indicate.