Quickstart

You are an expert software architect and workflow designer. Generate a `canopy.json` map for Canopy (https://canopy.8starlabs.com).

First, read Canopy's machine-readable docs so you use the exact schema and only valid icon slugs:
- Map schema (every field + accepted values): https://canopy.8starlabs.com/docs/maps/architecture-as-code.md
- Icon / brand slugs: https://canopy.8starlabs.com/docs/maps/icons.md
- Full docs in one file (optional): https://canopy.8starlabs.com/llms-full.txt

Then, from the system or workflow I describe at the bottom, output ONLY a valid canopy.json - a single JSON object, no prose and no markdown code fence - shaped like:
{
  "name": "<short map name>",
  "nodes": [
    { "id": "web", "label": "Web app", "tech": "Next.js", "brand": "nextdotjs", "x": 80, "y": 120 },
    { "id": "agent", "label": "Review agent", "tech": "OpenAI", "brand": "openai", "purpose": "Classifies inbound requests", "x": 320, "y": 120 },
    { "id": "approval", "label": "Human approval", "tech": "review step", "brand": "generic-approval", "x": 560, "y": 120 }
  ],
  "edges": [
    { "source": "web", "target": "agent", "label": "submits request" },
    { "source": "agent", "target": "approval", "label": "needs review" }
  ]
}

Rules:
- Every node needs a unique `id` and a `label`. Use a real `brand` slug from the icon library above; for internal workflow steps use generic slugs like `generic-workflow`, `generic-agent`, `generic-approval`, `generic-webhook`, `generic-job`, or `generic-decision`.
- Add `edges` for real dependencies, handoffs, data flow, approval flow, or workflow order (`source` and `target` reference node ids).
- Optionally add `tech`, `spend`, `purpose`, `billing`, `x`, and `y` per the schema.
- Be accurate to what I describe - do not invent services, apps, agents, or manual steps.

My system or workflow:
<paste your architecture or workflow here: a description, your README / docs, your infra list, SOP, AI agent flow, customer journey, or repo file tree>