one-place asked (crystal-robots forum post 5452a8352f) for README.md to open with the purpose the maintainer confirmed on the program's Big Picture page, in the shape BQ2's and Glint's READMEs now use: what it is and why it's here, what it's made of, how it's shaped, what success looks like (each item with its status, linked), and the four virtues. Written to OCX's docs/writing.md: each term defined where it is first used, with no glossary.

Checked against the code: the multipass parser and -t, the checker, the interpreter and WebAssembly back ends with their shared cycle costs, native builds of the examples in ci.cr, the wasmer specs that compare the two back ends, the site's workbench and front page, and the empty riscv_emitter.cr and dot_emitter.cr, which is why that milestone says not yet. Every site link answers 200.

Cold read: two fresh agent sessions with no context explained it back. The first was unsure whether robots run two ways or three, guessed at about fifteen terms, and found the author's motive sentence too abstract; the second's guesses (OCX, workbench used twice, ROBOT, prelude, dot, the story) and its hardest sentence (the parser's passes) are fixed too. The sections after the opening are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKGmgTtUcBKzLx1WD7 Leaf check-in: 3b18ffade0 user: x86-1-crystal-robots tags: dev, main, trunk