# Make an AnyRouter Explain figure Explain a concept as one isometric figure of a real physical object whose working IS the concept, then check it and upload it to AnyRouter Explain (https://anyrouter.dev/apps/explain). ## 1. Write the figure Write one JSON object that matches the JSON Schema at https://anyrouter.dev/apps/explain/schema.json. Fields: title, object, summary, hint, driver, parts, steps, takeaway. All text is plain text. Geometry: parts sit on a 12 x 12 floor grid (integers). x, y is the corner cell; w, d the footprint; h the height 1 to 8 (ignored for plates). A part stands on the bench, or sits `on` a part listed earlier and stays inside its footprint. Parts on the same surface never overlap. `driver` is the part the reader drags. Each step lists the part ids it lights and a short live readout. How these figures work (the Anatomy rules): - The object is the explanation. Invent one real, recognisable machine, tool or instrument whose mechanism maps one-to-one onto the concept. Never labelled boxes, arrows or a flowchart. - Every figure is highly detailed, however small the idea: build it the way the real object is built, with the parts that hold the parts (feet, rails, bushings, end stops, a label plate). A few slabs is unfinished work. - Truth first: collect the real numbers, counts and thresholds before inventing the object. The readout must be true at every step and change as the machine runs. - Many small precise parts on a 12 x 12 floor grid. Each part sits on another part or on the bench; nothing floats or intersects. - Four-tone shading: every solid shows a top and lit, mid and dark faces. Tone hierarchy: base "lo", structure "mid", the subject and the parts to watch "hi". - Painter's order: parts are drawn back to front, bottom to top, so hosts come before the parts they carry. - A framed card: a short title, a one-line interaction hint and a live readout line that is always true. - Calm motion: the reader drags or presses one driver part, and each step lights 1 to 4 parts. ## 2. Quality rules The server checks the schema, every reference (hosts, driver, step parts), the rules below and the drawn layout. A figure that breaks one is refused. - Build the real machine from at least 12 parts (a few slabs is unfinished work). - Use the tone hierarchy: a "lo" base and at least one "hi" part for the reader to watch. - Walk the machine through 3 to 6 steps. - Each step lights 1 to 4 parts. - The readout changes from step to step, like a live instrument. - Every step has its own title. - Plain text only: no HTML, entities, markdown fences or script URLs. - No control, zero-width or bidi characters. - No URLs or domains in the figure's text. - No placeholder text (TODO, lorem ipsum, Part 1, ...). - Short lines fit the figure on a phone: hint <= 40, readout <= 32, step title <= 48, part label <= 28 characters. - Every part is big enough to see (at least 10px a side at the figure's size). - The figure fits its frame, assembled and pulled apart. ## 3. Check it, then upload it Use an AnyRouter API key (`sk-ar-v1-...`, from https://anyrouter.dev/dashboard/keys) as a bearer token. The body wraps the figure: `{"payload":

, "visibility": "unlisted"}`. Visibility is `private` (only you), `unlisted` (default: anyone with the link, not listed) or `public` (listed in the Collection after review). Change it later with `PATCH https://anyrouter.dev/api/v1/apps/explain/submissions/` and `{"visibility": "public"}`, or `anyr apps visibility explain public`. Check without saving (`validate_only=1`): ```sh curl -sS "https://anyrouter.dev/api/v1/apps/explain/submissions?validate_only=1" \ -H "Authorization: Bearer $ANYROUTER_API_KEY" \ -H "Content-Type: application/json" \ --data @body.json ``` A valid figure returns `{"valid": true}`. A refused one returns HTTP 422 with `error.metadata.issues`: a list of `{path, code, message, fix}`, such as `{"path": "parts[3].on", "code": "host_missing", ...}`. Fix each issue and check again. Upload: ```sh curl -sS "https://anyrouter.dev/api/v1/apps/explain/submissions" \ -H "Authorization: Bearer $ANYROUTER_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(sha256sum body.json | cut -c1-32)" \ --data @body.json ``` The reply has the figure's `url`. With the anyr CLI, `anyr publish explain figure.json --dry-run` checks and `anyr publish explain figure.json` uploads (the file holds the figure itself, not the wrapper). ## Or upload a figure built with the /anatomy skill A standalone page from the anatomy kit (`node build.mjs`, plus `node build.mjs --light`) or a lone SVG from `figureSvg({ standalone: "dark" })` uploads through the same endpoint. The payload is `{"format": "anatomy-html" | "anatomy-svg", "content": "", "content_light": "", "summary": ""}`, at most 2 MB per file. The server checks that it is a kit figure (`class="iso-figure"`, `class="iso-plate"`, an `