What problem does it solve? Security reviews and architecture documentation need clear diagrams of how authentication and API-key trust boundaries work, but drawing them by hand is slow and risks leaking real keys, tokens, or secrets into shared artifacts. ## Core Features & Use Cases - Trust-boundary diagram generation: Builds a three-zone security diagram (public zone, boundary frame, authenticated zone) via the ExcaliDash MCP server, with key verification, scope/RBAC, rate limiting, audit logging, and rotation/revocation controls on the boundary. - Mandatory secret redaction: Enforces typed [REDACTED_*] placeholders for API keys, bearer tokens, HMAC/JWT secrets, and database URLs before any tool call, keeping only the public exd_ prefix literal, and re-scans exports as a backstop. - Quality-gated output: Runs a lint, score, repair, and validate loop until the drawing scores at least 95 with zero hard blockers, then saves, versions, and exports it. - Use Case: Ask for a diagram of how partner clients present an exd_ API key to a gateway that HMAC-verifies it, checks scopes, rate-limits, and audits before reaching protected Orders and Billing APIs, and receive a scored, redacted, exportable Excalidraw drawing. ## Quick Start Ask the AI to diagram your API-key authentication flow showing public clients, the auth gateway with key verification, RBAC, rate limiting and audit, and the protected services behind it, with all keys redacted.
