yaml-authoringlisted

# YAML Diagram Authoring ## Basic Structure ```yaml version: 1 docId: unique-document-id title: "My Architecture Diagram" # optional nodes: - id: unique-id provider: aws # Provider name (e.g., aws, gcp, azure) kind: compute.lambda # Service category.type label: "Display Name" # optional parent: container-id # optional, for nesting in VPC/Subnet layout: # optional for child nodes (auto-positioned) x: 100 # optional for child nodes y: 200 # optional for child nodes w: 200 # required for containers (VPC/Subnet) h: 150 # required for containers edges: - id: edge-1 from: source-node-id to: target-node-id label: "optional label" # optional ``` ## Auto-Layout Child nodes (with `parent`) can omit `layout` entirely for automatic positioning: ```yaml nodes: - id: vpc provider: aws kind: network.vpc layout: { x: 0, y: 0, w: 800, h: 600 } # Container: explicit layout - id: ec2_1 provider: aws kind: compute.ec2 parent: vpc # No layout - auto-positioned at (40, 40) - id: ec2_2 provider: aws kind: compute.ec2 parent: vpc # No layout - auto-positioned at (200, 40) ``` **Auto-layout rules:** - 3 columns per row - 60px padding, 160px horizontal spacing, 140px vertical spacing - Explicit `x`/`y` overrides auto-positioning - Cannot specify only `x` or only `y` (both or neither) ## Node Kind Categories The `kind` field uses a hierarchical format: `category.type` or