Glossary

One meaning per word: a word lusine uses means one thing, the thing below, everywhere in lusine's documents. Where a word had several meanings, one kept the word and the others took other words; the column on the right is those other meanings' old phrasing, which doclint refuses in every document it checks, naming the word.

A game has a glossary of its own, docs/GLOSSARY.md in the game, for its words (Boules': the arm, the terrain, the jack). doclint reads lusine's and the game's for the game's documents. A game's word may add a meaning in the game's tree; it may not redefine one of lusine's, and doclint refuses a game glossary that lists a word this one has. The library never learns a game's word.

Words

Word	Its one meaning	Not (refused)
Bool	the quantity kind that is one bit of the matter	Flag(, flag kind
flag	a command-line flag, --name
record	one change a host hands the running program between steps: a store, an append, a removal or a clear	Record(
field	a physical field, the physics' word	Field(
Copy	a buffer's contents transferred whole into another buffer	View pass, View(
view	the camera's view, and the site's live views of data
layer	a directory of kernels/, its kernels' references and proof pages, and the namespace lusine.<layer> (library/lusine/<layer>/) its kernels have once ported to Trait; nothing else, so a namespace of the library's that holds no kernels (lusine.materials) is no layer	layered over, mod layer
overlays	what a mod does to the game's directory: the mod's file at a path replaces or adds to the game's, and a path the mod does not hold is the game's
the reference	a kernel's numpy form, its .py body under kernels/, kept as the kernel's test beside its draft-5 form in library/lusine/; a proof page shows it in its reference cell	numpy arm, hand arm, hand_arm
arm	a test arm: one assertion a selftest records
board	the issue board
kind	the one meta-word, always qualified: a space kind, a pass kind, a quantity kind, a camera kind, a display kind
gate	a commit or pull-request gate, a row of tools/gates.py; a game's gate that computes is always a logic gate
baked	a library table's or row's values computed by its source from a pinned law at build and stored as points, for a law that needs a sum, an integral or an iteration; its name says approximate, and a value as cheap as a lookup is a kernel, never baked
step	a simulation step; a step of a workflow's job is a job step	workflow step

A document that must name an old phrase (this page is one) puts <!-- doclint: allow-word --> on that line.