Use case
Runs on Local files
Run editorial and other pipelines
Issue types, statuses and transitions are configuration, so the same tool that tracks code can run a newsroom, a research queue or a review process.
The problem
Not all work is software. A publication moves stories from idea to assignment to research to draft to published, and each stage has rules: no draft without a research packet, no publication without an editor's sign-off. General trackers either cannot express those rules or bury them in admin screens.
How Kanbus helps
In .kanbus.yml you define the issue types, the statuses each one passes through and the transitions allowed between them. Lifecycle hooks run before or after each change, so a hook can refuse to move a story to the next stage until the files that stage needs exist, or scaffold a working folder when a story is created. Policies written in Gherkin describe the rules in plain language and are checked on every change.
Anthus's own newsrooms run this way. Each story is an issue that moves through stages such as idea, assignment, research, report, editor_select, copywriting and published, while agents do the research and drafting and editors make the calls.
What you set up
- Local files in the publication's repository.
- Custom types, statuses and transitions in
.kanbus.yml. - Hooks for the checks each stage needs, and policies for the rules people should be able to read.