Draw a mermaid architecture diagram in markdown for: $ARGUMENTS
Conventions
- Boxes are services/components:
svc[bex-api]. Use [(...)] for datastores. Humans (user, developer, operator) are triangles: user@{ shape: tri, label: "user" }.
- A box that is not a long-running service must say so in its label — readers assume boxes are services and ask "where is this running?". Mark scheduled/ephemeral work (
cron["backup pod (spawned nightly, exits when done)"]) and inert config objects (secret["Secret foo (k8s object, created once)"]). Draw humans as triangles: operator@{ shape: tri, label: "operator" }. Never draw a manual procedure as a peer box of running infrastructure: give runbook/recovery flows their own subgraph whose title says it's manual and where it runs (subgraph "disaster recovery — manual runbook, any docker host"), with the human actor inside.
- Arrows are dependency direction:
A --> B means A depends on (calls, reads, deploys to) B — never the reverse.
- Concise but to the point: only load-bearing services and edges. No styling, no colors, no legend. Label an edge (
A -->|gRPC| B) only when the relationship isn't obvious. Default to flowchart TB; use LR only if the graph is much wider than deep. Use subgraph only for real boundaries (cluster, node, network, trust zone, automated vs. manual) — subgraphs are how the diagram answers "where does this run?". An edge may target a whole subgraph by id (subgraph cluster["app cluster"] … op --> cluster).
- If $ARGUMENTS refers to this repo, read the relevant docs/code first — start with the root
CLAUDE.md for the package map, the scoped <package>/CLAUDE.md for the package's architecture, and docs/adrs/ for recorded decisions. Don't diagram from guesswork.
Syntax gotchas that break rendering: quote labels containing (, ), [, {, or -->-like text (a["Queue (SQS)"]); never name a node bare end or graph; subgraph titles with spaces need quotes.
Verify (mandatory, before answering)
- Write the diagram body (no
```mermaid fence) to a unique .mmd file under a gitignored scratch directory — .agents/tmp/ at the repository root, or the current package's tmp/.
- Run:
npx -y @mermaid-js/mermaid-cli@11.16.0 -i <file>.mmd -o <file>.svg — exit 0 means the syntax is valid. (First run downloads a headless browser; that's expected.) The version is pinned deliberately (supply-chain: codex-security #17) — bump it consciously, don't revert to floating.
- On failure, read the parse error, fix the diagram, and re-verify. Never output a diagram that hasn't passed.
Output
A single ```mermaid fenced block, followed by at most 2 sentences explaining the key dependency flow. If the user asked to put the diagram into a file, insert the verified block there instead.
1---2name: mermaid-33description: Create concise, syntax-verified Mermaid architecture diagrams. Use when the user asks to diagram a repository component, document, system, dependency flow, or supplied description in Mermaid.4---56Draw a mermaid architecture diagram in markdown for: $ARGUMENTS78## Conventions910- **Boxes are services/components**: `svc[bex-api]`. Use `[(...)]` for datastores. Humans (user, developer, operator) are triangles: `user@{ shape: tri, label: "user" }`.11- **A box that is not a long-running service must say so in its label** — readers assume boxes are services and ask "where is this running?". Mark scheduled/ephemeral work (`cron["backup pod (spawned nightly, exits when done)"]`) and inert config objects (`secret["Secret foo (k8s object, created once)"]`). Draw humans as triangles: `operator@{ shape: tri, label: "operator" }`. Never draw a manual procedure as a peer box of running infrastructure: give runbook/recovery flows their own subgraph whose title says it's manual and where it runs (`subgraph "disaster recovery — manual runbook, any docker host"`), with the human actor inside.12- **Arrows are dependency direction**: `A --> B` means A depends on (calls, reads, deploys to) B — never the reverse.13- **Concise but to the point**: only load-bearing services and edges. No styling, no colors, no legend. Label an edge (`A -->|gRPC| B`) only when the relationship isn't obvious. Default to `flowchart TB`; use `LR` only if the graph is much wider than deep. Use `subgraph` only for real boundaries (cluster, node, network, trust zone, automated vs. manual) — subgraphs are how the diagram answers "where does this run?". An edge may target a whole subgraph by id (`subgraph cluster["app cluster"]` … `op --> cluster`).14- If $ARGUMENTS refers to this repo, read the relevant docs/code first — start with the root `CLAUDE.md` for the package map, the scoped `<package>/CLAUDE.md` for the package's architecture, and `docs/adrs/` for recorded decisions. Don't diagram from guesswork.1516Syntax gotchas that break rendering: quote labels containing `(`, `)`, `[`, `{`, or `-->`-like text (`a["Queue (SQS)"]`); never name a node bare `end` or `graph`; subgraph titles with spaces need quotes.1718## Verify (mandatory, before answering)19201. Write the diagram body (no ` ```mermaid ` fence) to a unique `.mmd` file under a gitignored scratch directory — `.agents/tmp/` at the repository root, or the current package's `tmp/`.212. Run: `npx -y @mermaid-js/mermaid-cli@11.16.0 -i <file>.mmd -o <file>.svg` — exit 0 means the syntax is valid. (First run downloads a headless browser; that's expected.) The version is pinned deliberately (supply-chain: codex-security #17) — bump it consciously, don't revert to floating.223. On failure, read the parse error, fix the diagram, and re-verify. Never output a diagram that hasn't passed.2324## Output2526A single ` ```mermaid ` fenced block, followed by at most 2 sentences explaining the key dependency flow. If the user asked to put the diagram into a file, insert the verified block there instead.
bex-co