The final pass

Two passes over a finished draft: whether it is the right document, and whether it holds together.

#Compilation as the smaller half

Everything in this section compiles. A file can satisfy the grammar exactly and still be the wrong document: two scenes nobody asked for, a canvas that decorates the argument rather than carrying it, a number typed in beside the mark that computes it. So the pass that catches those runs first, and the mechanical one after it.

#The first pass: the right document

  • It teaches the topic the header's title names, and nothing was added that the topic did not call for.
  • Every scene earns its place — none exists for variety, for length, or to use a construct the document had not used yet.
  • Every construct is there because the content needed it.
  • The headings alone are enough to navigate by, and none of them gestures where it could name.
  • Each detail reads on its own, full screen, with no narrative beside it.
  • Every number was computed and every external fact checked against a source or cut.

#The second pass: the mechanical checks

  • It compiles, and every construct it uses is one the reference documents.
  • Every === has a cue anchored to it — the compiler refuses an anchor past the last marker, and says nothing about a marker nothing fires on.
  • The first scene opens on prose, and the headings use more than one level.
  • No pronoun is left pointing at a sentence that became a heading.
  • Every multiline node carries a multiline attribute group.
  • No : true or : false; booleans last; hyphenated keys spaced.
  • Durations of a second or more are written in seconds.
  • No size or width except where the attribute is the geometry.
  • Each mark is declared once, with highlights and spotlights nested inside the cue that brought it in.
  • Domains are omitted where a shape has to be true and authored where the layout fills the frame, and neither is padded past the data.
  • Ticks match what the prose asks the reader to read, and each hue means one thing across the whole document.
  • Every definition carries a term that stands alone in a glossary, and every note is an aside rather than the next step of the argument.
  • Maths is LaTeX everywhere LaTeX is legal.
  • Bulk rows are in @data and repeated expressions in @let.
  • Every computed number in the prose is a !value rather than a typed figure.
The editor compiles as it goes and marks what it rejects, so the mechanical half of this list is answered by the source panel. The first half is not answered by anything, which is why it is first.