Handbook

LCDL diagram system

Use fenced ```blueprint-diagram blocks per Kitchen Sink README. Do not use Mermaid in handbook-bound pages (workspace policy).

Updated

Diagram catalog

Diagram Typical placement Suggested KS key
LCDL mental model Home, What is LCDL linear
TaskRunner contract validation Client API, ContractSpec sequence or swimlane
Error and repair loop Repair loops, errors linear or ASCII fallback
RAG evidence flow RAG guide linear / pipeline-style
Enterprise boundary Enterprise architecture swimlane
Agent/Cursor workflow Agents hub sequence
Context budget funnel Guides and tutorials funnel or linear with fallback_ascii

Rules

  • Every diagram must include alt: text in the fenced block.
  • Every diagram must have an adjacent text fallback or short explanation in prose.
  • Use expand: true on blueprint-diagram when the consumer site ships the diagram modal runtime; pair with optional fallback_ascii: for an SVG/ASCII toolbar toggle instead of a separate blueprint-diagram-ascii fence.
  • Keep diagrams conceptual; do not encode secrets, internal URLs, or live gateway details.

Fence examples

Use fenced ```blueprint-diagram blocks per Kitchen Sink README. Do not use Mermaid in handbook-bound pages (workspace policy).