zindex

Agents create, edit, validate, and render diagrams as durable state - not throwaway output. Structured operations, immutable revisions, 40+ validation rules, and multiple render targets through the Diagram Scene Protocol (DSP).

The protocol

DSP (Diagram Scene Protocol) is the machine interface for diagrams. Agents describe what exists, not how to draw it.

• Semantic, not geometric: Agents declare nodes, edges, and relationships. Layout is computed, not hand-placed.
• Layout engine built in: A Sugiyama-style hierarchical layout pipeline figures out positions, edge routes, and label placement automatically. Agents describe the graph; the engine handles the geometry.
• Patchable: Stable IDs enable incremental updates. Add a node, move an edge - without regenerating the entire diagram.
• Renderer-agnostic: One canonical scene, multiple outputs: SVG and PNG with 4 render themes (clean, dark, blueprint, sketch).
• Deterministic: Same input, same output. Validate ? normalize ? layout ? render. Every step is inspectable.

Why zindex?

Diagrams need validation, layout, versioning, and multi-format rendering - not just markup generation.

1. Incremental editing: Patch-based updates instead of full regeneration. Agents can modify individual elements while preserving the rest.
2. Deterministic execution: Consistent output across runs. Failures are explainable. The pipeline is inspectable at every step.
3. Durable state: Revision history, diffs, stable IDs. Diagrams are versioned artifacts, not ephemeral outputs.
4. Multi-agent ready: Shared infrastructure for multiple agents collaborating on diagrams. Not just a single-shot generator.
5. Domain-aware: Purpose-built for architecture, BPMN workflows, ER diagrams, sequence diagrams, org charts, and network topology - not generic vector shapes.
6. Production-grade: 17 operation types. 40+ semantic validation rules. Auth, rate limiting, PostgreSQL storage.

Where it fits:

Zindex is the middle layer between agent reasoning and visual output.

Zindex is to diagrams what a database is to application state. The agent-native runtime for creating, updating, validating, and rendering diagrams as durable state.