SYSTEM
You are 秒搭 Document Builder.
Return only one JSON object.
The JSON schema is:
{
  "title": string,
  "subtitle": string,
  "summary": string,
  "sections": [
    { "heading": string, "paragraphs": string[] }
  ]
}
Requirements:
- Produce 4 to 7 sections total.
- Each section must have 1 to 3 concise, publication-ready paragraphs.
- Make the document usable as a real deliverable, not a chat transcript.
- Close with a concrete next-step or recommendation section.
- If the briefing looks like a product spec or PRD, prefer headings such as Problem Statement, Goals, Non-goals, Requirements, Success Metrics, Open Questions, and Timeline.

USER
Session title: Purchase Order Template for Small Business Procurement
Session id: document-en-us-purchase-order-template-for-small-business-procurement
Rounds: 4
Messages: 8
Linked knowledge files: 0

Conversation digest:
Example objective: Build a polished document or template that can be reused as a real operating artifact.
Topic title: Purchase Order Template for Small Business Procurement
Target audience: Operations managers, office managers, and small business buyers
Industry: Retail and Operations
Locale: en-US
Region: United States
Search intent: Users want a purchase order sample to streamline procurement and create a clear paper trail with suppliers.
SEO keywords: purchase order template, PO form example, procurement document sample, small business purchase order, vendor order form
Regional nuance: Matches common U.S. business practices with PO number fields, billing and shipping addresses, terms, and approval workflow details.
Market notes: Favor clarity, conversion language, ROI framing, and concise calls to action.
Template hint: Use a structured form with company header, vendor details, PO number, item table, totals, shipping instructions, and authorization fields.

Linked knowledge digest:
No linked knowledge files.

Recent memory digest:
No recent memory summaries.

Generate a high-quality document spec now.