ShojikuWrite YAML. Get documents.
Invoices, receipts, application forms, manuscript paper. Two YAML files and one JSON render to byte-identical PDFs on every machine — an engine built for AI agents.
Skip to content
The banner above is output from the engine this site describes — one 200mm×90mm template (templates.yml). The two vertical columns on the right are a manuscript-paper
char_grid; the red seal is an ellipse stamped over the blank cells.Edit the YAML. Render it right here.
The editor holds a real bundled example. Rendering happens in the WASM engine inside your tab — nothing is uploaded. The Latin example renders immediately on ~1.2 MB of fonts; one click fetches BIZ UD Gothic (9 MB) for the Japanese one.
For the documents other engines give up on
Shojiku grew out of Japanese business paperwork: vertical-writing book typography, 200-character manuscript paper, an A3 résumé spread, an application form whose blank and filled versions render from one template without a single point shifting. Swap the locale pack and the same receipt renders in Traditional Chinese, Simplified Chinese, or Hindi — the geometry never moves.
 |  |
The gallery holds every bundled example; CI byte-compares each one on every run.
One engine, all the way to verification
Authoring, checking and shipping all pass through the same engine. Signing and verification are CLI operations and use no network.
- validate — machine-readable diagnostics with stable codes, before anything renders.
- preview — one PNG per page; look before you ship.
- render — the same input produces the same bytes from the CLI, Docker, every SDK and the browser.
- sign — an incremental-update signature; the file stays a readable PDF.
- verify — reports the byte range the signature actually covers, and names what it did not check.
The tutorials walk the whole path; the playground shows how the template language behaves.
Hand the loop to an AI agent
The MCP server ships in the same Docker image. An agent writes YAML, validates, looks at the preview, and iterates against diagnostic codes — the loop this engine was designed around. Details on the agents page.
There is a GUI. It is one way in, not the only one.
The Designer is a visual editor over the same engine, reading and writing the same files your agent does. Open a document in the GUI, fix it in YAML, open it in the GUI again.