Publishing a Playbook

Saving source does not publish a Playbook. Doku treats authoring and publication as separate boundaries so the exact source, build result, version, availability, and approvals can be reviewed together.

From Draft to published version

1. Create or open a Playbook Draft backed by its Playbook Repository.
2. Edit the package files and run the available structural checks.
3. Commit the Draft revision you want to promote.
4. Create a Promotion Request for that frozen source.
5. Resolve validation, policy, safety, or approval requirements.
6. Complete promotion to produce an immutable Published Playbook Version.

A Playbook Run binds to a Published Playbook Version. Later edits do not silently change work already in progress.

What promotion validates

Promotion is where Doku turns authored source into a product-safe package. Expect checks around:

• package identity and authored version;
• Playbook SDK compilation;
• Outcomes, Claims, Variables, Capacities, Skills, and the Task graph;
• referenced instruction and page-content files;
• availability and publisher policy;
• required human approval for consequential publication paths.

Versioning guidance

• Increase the version when the promoted package behavior or contract changes.
• Keep the slug and package identity stable for the same Playbook.
• Review Claim and evidence changes carefully; they change what “complete” means.
• Treat narrower connector requirements as a meaningful trust improvement.
• Make page copy describe the version being published, not future behavior.

A Git push, Draft save, or successful local check is not a Doku publication. Publication happens only through a completed Promotion Request.