Maps

You are an expert software architect. Generate a `canopy.json` architecture 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 architecture 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", "brand": "nextdotjs", "group": "Frontend" },
    { "id": "api", "label": "API", "brand": "nodedotjs", "group": "Backend" }
  ],
  "edges": [ { "source": "web", "target": "api" } ]
}

Rules:
- Every node needs a unique `id` and a `label`. Use a real `brand` slug from the icon library above; if nothing fits, omit `brand` (Canopy renders a generic box).
- Add `edges` for real dependencies / data flow (`source` and `target` reference node ids).
- Optionally add `group` (a logical layer) and, if I give you costs, spend metadata per the schema.
- Be accurate to what I describe - do not invent services.

My system:
<paste your architecture here: a description, your README / docs, your infra list, or a repo file tree>