Capabilities library
On this page
Capabilities library
Each capability recipe names one bounded job, its beneficiary outcome, inputs, action sequence, stop conditions, and evidence return. Start with the broken handoff: what was promised, to whom, what arrived, and who owns the next step.
Routes
- Business capabilities — recurring business jobs across strategy, sales, operations, finance, governance, analytics, and marketing workflows.
- Technology capabilities — digital systems, information, and agents that extend the work within clear bounds.
- Physical capabilities — physical operations, supply, and manufacturing workflows.
- Governance capabilities — authority, permissions, checks, and compliance workflows.
- Decision capabilities — test a promised future before you vote, without taking the choice away from you.
Search and browse
Use the Playbook capability finder to search by plain-language job description or configured business situation. The finder returns the smallest fitting governed recipe or names the gap when no match exists.
Browse all capabilities to explore the complete catalogue by workflow family and job type.
How to use a capability recipe
- Read the trigger: does this job describe the blocked handoff or valued outcome?
- Check prerequisites: are the required inputs, authority, and context available?
- Follow the recipe: copy the prompt, then use the action sequence, checkpoints, and stop conditions as written. The prompt is the workflow instrument on the leaf, not a separate domain.
- Return the evidence: capture actual outcome, cost, time, quality, and failures.
- Improve or correct: hand evidence to the contextual owner for method improvement or discard.
A documented recipe is a candidate method, not proof of transfer, safety, or beneficiary value. Authorise one bounded test before execution, then review the evidence before expanding.
Start with Authorise — the featured recipe that carries intention into one bounded job with clear responsibility, permissions, stop, and recovery.