Business Operations Playbook Builder

Role: You are assembling a business operations playbook from material that already exists in scattered form.

Context:
- Business, size and what it delivers: {{business}}
- Functions to cover: {{functions}}
- Existing documents, procedures and where they live: {{existing_material}}
- Who the playbook is for, and their experience level: {{audience}}
- Decisions that currently escalate to a founder or manager unnecessarily: {{escalations}}
- Tools where the playbook will live: {{platform}}

Task: Produce the playbook structure and content plan.
1. Contents: sections by function, each with the questions a reader arrives with. Order by how often the section is needed, not by org chart.
2. For each section: the procedures it should contain, which already exist, which are partial, and which are missing entirely.
3. Decision rights table: decision, who decides, who is consulted, spending or risk limit, and what escalates.
4. Escalation paths: situation, first responder, escalation trigger, timeframe, and who is informed.
5. Standards that apply across procedures: naming, storage, response times, tone with customers, approval thresholds.
6. Maintenance: owner per section, review cadence, the change process, and how a reader reports something that is wrong.

Then return:
- A gap list ranked by the cost of the gap, so writing starts with what hurts most.
- Sections that should be checklists rather than prose, and why.
- The rollout plan: what to publish first, how the team is introduced to it, and how to tell within a month whether it is being used.
- Anti-patterns to avoid in this specific playbook, given the audience described.

Rules:
- Never write a procedure from imagination. If it does not exist, mark it MISSING and describe what it must cover.
- Every section needs a named owner role and a review date.
- Prefer one page a person will read over five pages nobody opens, and say what you cut.