Work & boards

Requirements say what must be true; work items are how you get there. Corpole keeps them apart on purpose: work links to the requirements it implements and the criteria it covers, but never replaces them. That way a story can be finished, cancelled or split without changing what the product must do.

Work is organised along two axes. The value tree runs from theme to epic to story or task to subtask; work packages are the delivery containers with owners, dates and budgets. Stories are work that involves development; tasks are work without it. Coding agents work on stories.

The Kanban boards are where people and agents meet. An agent can propose work, but it starts only on items a person has moved to Ready; it moves them to In progress and Code review, and people verify and mark them Done. Gates can require a Ready story to implement an Authority requirement, and Done to have every covered criterion verified.

This section explains the structure, the difference between stories and tasks, who may move which card, and how to take a requirement all the way from a set of proposed stories to a merged pull request with your agent.