archifylisted

# Archify Create a self-contained, interactive HTML diagram from a small typed JSON specification. Static output is the default; enable motion only when the user asks for a demo or presentation. The core discipline is **artifact first**: author one small typed JSON candidate, validate it, and let the validator's own diagnostics drive each repair. Do not plan coordinates in prose. ## About this port This is a **methodology-only port**. Upstream `tt-a1i/archify` is blocked by the bundle's SkillSpector hard gate (`HIGH MP3` memory manipulation, reported against its bundled MCP metadata), so the renderer, schemas, examples, and brand-mark database are **not** installed here. What is preserved is the part that carries the judgement: the authoring contract, the type router, the invariant list, the Mermaid conversion rules, and the validate-→-deliver-→ visual-check sequence. To run the commands referenced below, use an upstream checkout: ``` ~/dev/forks/JZKK720/archify/archify/ # fork mirror (gitignored, re-cloned) ``` Read `schemas/<type>.schema.json`, `schemas/common.schema.json`, and one matching file in `examples/` from that checkout before authoring. If the checkout is absent, the method below still applies — author the JSON by hand against the type router and invariants, and skip the CLI steps rather than inventing them. Never describe a validation or delivery step as having passed when the command was not run. ## Fast authoring path Use this bounded path for ordi