Archify: Diagrams That Refuse to Lie
An executable contract
An agent authors a typed JSON intermediate representation and the Archify CLI compiles one self-contained interactive HTML artifact. It supports guided views, trace animation, search, and dark/light themes. Unknown IDs, overlap, infeasible routes, diagonal crossings, and shared-corridor failures prevent delivery.
Design lessons from validation
Component types are closed; coordinates use columns 0–5; routing should be orthogonal; bias is a 0–1 value. Fan-outs are difficult to label, so one fan-out label at most is a practical rule. Validation errors send the agent back to revise the source rather than patching rendered HTML.
From prototype to showcase
The standard profile supports prototypes, while showcase adds stricter corridor and crossing checks. All six diagrams in the source showcase passed validation. The output is deterministic enough to regenerate, with visual quality treated as a build constraint.
How the pieces connect
Illustrative architecture and workflow.