Deliverables library

Reachable from the left menu, it gathers every deliverable of the active project: meeting preparations, user stories and process models.

Each deliverable starts as a Draft and, when you are happy with it, becomes Validated (reversible). You can duplicate it to explore a variant without losing the original.

Copy a deliverable’s text in one click, or grab the BPMN 2.0 export for a process model, to open in your diagramming tool.

The AI critiques a deliverable without regenerating it: it raises objections, and you decide on each. A safeguard against blind spots that keeps your text intact.

Each objection carries its lens: Verification when it targets the deliverable’s writing quality (ambiguous, untestable, contradictory), and Validation when it targets alignment with the business need. A deliverable can be flawless in form and still be the wrong thing to build. The BABOK separates these two tasks (7.2 and 7.3), and so do we.

From at least two deliverables, the AI cross-checks them (with the project context) to spot gaps and contradictions to arbitrate: a story with no matching process step, a requirement nothing covers, a term drifting from the glossary. This is what the BABOK calls traceability (task 5.1).