SOP Generator

# Task
Create a standard operating procedure from the process notes below. Use ONLY the provided information.

# Inputs
- Process name: {process_name}
- Process notes: {process_notes}
- Audience: {audience}
- Goal: {goal}
- Constraints: {constraints}

# Anti-hallucination rules
1. Do not invent steps, tools, or approval requirements not in the source.
2. If a step's details are incomplete, mark it [NEEDS DETAIL] with a note on what's missing.
3. Do not assume organizational hierarchy — use the roles mentioned in the notes.

# SOP structure
1. **Header**: Process name, version (Draft 1.0), effective date (TBD), owner (from notes or [TBD]), review cycle (suggested: quarterly).
2. **Purpose** (2-3 sentences): Why this SOP exists and what it ensures.
3. **Scope**: What's covered and what's explicitly excluded.
4. **RACI matrix**: For each major step, assign:
   - R (Responsible): Who does the work
   - A (Accountable): Who approves/owns the outcome
   - C (Consulted): Who provides input
   - I (Informed): Who needs to know
   Format as a table.
5. **Procedure**: Numbered steps. Each step has:
   - Action (imperative sentence)
   - Owner (role)
   - Inputs needed (what triggers or feeds this step)
   - Output (what this step produces)
   - Time estimate (if inferable)
6. **Exception handling**: What to do when the standard flow breaks. Cover 3-5 common exceptions.
7. **Controls and checkpoints**: Quality gates, approval points, or verification steps.
8. **Compliance callouts**: Any regulatory, legal, or policy requirements that affect the process. Mark [VERIFY WITH LEGAL/COMPLIANCE] if uncertain.
9. **Appendix**: Glossary of terms, related SOPs, or reference documents.

# Output
Return the complete SOP using all sections above.

<source>{process_notes}</source>
<context>
  <process_name>{process_name}</process_name>
  <audience>{audience}</audience>
  <goal>{goal}</goal>
  <constraints>{constraints}</constraints>
</context>
<task>Create an SOP from the process notes above. Use ONLY provided information.</task>
<instructions>
  Don't invent steps or approvals. Mark incomplete steps [NEEDS DETAIL]. Use roles from notes.

  Structure: Header (name, version, owner, review cycle) > Purpose > Scope > RACI matrix (table) > Procedure (numbered: action, owner, inputs, output, time) > Exception handling (3-5) > Controls/checkpoints > Compliance callouts [VERIFY WITH LEGAL/COMPLIANCE] > Appendix.
</instructions>
<output>
  Return the complete SOP.
</output>

Process name: {process_name}
Process notes: {process_notes}
Audience: {audience}
Goal: {goal}
Constraints: {constraints}

Rules: only provided info, mark gaps [NEEDS DETAIL], use roles from notes.

Structure: Header (name, version, owner, review cycle) > Purpose > Scope > RACI matrix > Procedure (action, owner, inputs, output, time) > Exceptions (3-5) > Controls > Compliance [VERIFY WITH LEGAL/COMPLIANCE] > Appendix.

Based on the entire content above, return the complete SOP.