Produce ONE single self-contained static HTML file named index.html (NO React, NO Next.js, NO frameworks, NO external assets/CDN/fonts — inline SVG + inline CSS only) that renders a professional, enterprise-grade HIGH-LEVEL ARCHITECTURE DIAGRAM for a system called "Triage Workflow Manager". It must render correctly when opened directly as a file:// and look clean for a printed design document: pure white background (#ffffff), crisp 1px borders, generous spacing, rounded corners, soft shadows, a calm professional palette (slate #334155 text, indigo #4f46e5 and teal #0d9488 accents, light fills #eef2ff / #f0fdfa / #f8fafc), and a system font stack. Fixed canvas exactly 1640 x 1080, no scrolling, no interactivity, no animations. All text must be crisp and large enough to read in print (>= 13px). Arrows must have clear arrowheads and short labels; never let arrows cross through text boxes.

The diagram MUST depict these layers, top to bottom, with directional arrows showing data/control flow:

1. ENTRY POINTS (top row): three small boxes "rocket CLI", "REST API", "Scheduled trigger" — all converge with arrows into the loader plane.
2. AUTHORING + LOADER PLANE: "YAML Workflow Definitions" (a document-shaped box) -> "Config Loader & Validator" -> a small pill "content-hash (sha256)" -> a CYLINDER labeled "Immutable Plan Registry" with sub-text "Postgres • versioned, immutable".
3. EXECUTION PLANE (center, visually the heart, largest box): "Deterministic Interpreter" with sub-text "runs as a DBOS workflow • pure control flow". Visually nested inside or attached to it: a DASHED box "Control nodes: decision / fork / loop / end (in-process, NOT journaled)", a box "CEL Evaluator (when: guards)", and a box "Workflow Context (durable state)".
4. STEP EXECUTION: from the interpreter, an arrow to "Type → Handler Registry", which fans out to FIVE handler boxes in a row: "log_search", "file_read", "parse", "metric_query", "llm_agent". Put a small caption under the row: "each I/O node runs as a DBOS @step — journaled, replayed on recovery". The "llm_agent" box has an arrow to an external box "LangGraph Agents".
5. DURABLE SUBSTRATE (a wide foundation bar spanning the full width near the bottom): "DBOS Transact + PostgreSQL" with sub-labels "Workflow & Step Journal" and "crash-safety · retries · resume / replay". Draw thin arrows from the Interpreter and from the handler row down into this bar (writing/journaling).
6. DATA SOURCES (left vertical column, read-only, arrows pointing INTO the handlers): "Log bundles (NTNX-Log-*)", "Live cluster (ssh / ncli)", "Metrics (ClickHouse)", "Files".
7. OBSERVABILITY (right vertical column): "OpenTelemetry traces → Langfuse", "Structured logs → ClickHouse", "Metrics".
8. OUTPUT (bottom, below the substrate): a single emphasized box "Verdict / KB match / Triage report".

Include a small LEGEND in a corner that explains: solid box = durable journaled DBOS step; dashed box = in-process deterministic control (not journaled); cylinder = Postgres-backed store. Add the title "Triage Workflow Manager — High-Level Architecture" at the top and a thin subtitle "config-driven · durable · deterministic replay". Output ONLY the single index.html file, nothing else.