04 · Public source
DesignCore
A diagram pipeline where the model describes relationships instead of guessing coordinates.
The authored spec stays coordinate-free; deterministic layout and rendering own the geometry that appears in the output.
View sourceProblem
When I asked a model to produce a diagram file, I was also asking it to decide the content, relationships, coordinates and renderer syntax in one shot. A small text change could move the result from readable to broken.
Mechanism
- Accept a graph-shaped spec and reject authored position fields.
- Use Graphviz to calculate geometry, then write Mermaid, draw.io or Excalidraw through owned emitters.
- Require the selected renderer to produce an artifact before recording it in the manifest.
Evidence
- Local tests
- 185 passed
- Isolated example
- Rendered · linted · clean
- Coordinate proof
- x: 120 rejected
- Checks
- Structure · geometry · freshness
Boundary
Verified means rendered plus deterministic checks. It does not prove that a diagram is understandable, beautiful, accessible or conceptually correct.
The renderer stack also has environment constraints; finding a dependency does not guarantee it can run inside every sandbox.