Section
00 91 13
Title
Insights
Scale
NTS
Issued
2026-08-22

We publish when something is measured.

Dated notes on the parts that were hard, with the numbers that produced them. Two so far.

01 / 00 91 13The record
Note 022026-08-22
Rendering

The blank sheet passes every check that looks at the file.

The expensive failure in document generation is not a crash. A crash is loud, it has a stack trace, and somebody fixes it that afternoon. The expensive failure is a sheet that renders successfully and carries nothing: correct title block, correct sheet number, correct paper size, correct file extension, and an empty drawing area.

It opens. It prints. It has a plausible byte count. It passes every check written against the artifact rather than against the drawing — which is most of them, because checking a file is easy and checking a drawing is not.

So the blank sheet has its own regression class in this engine, separate from the rest of the suite. Not a note in a checklist, not a code review habit: a named class of test that fails on emptiness specifically. It exists because the failure recurred, and because a rule that lives only in somebody’s memory is a rule that has already been skipped once.

The wider version of the lesson is unglamorous. When a system can fail silently, the check has to be aimed at the silence, not at the surface it hides behind.

Note 012026-08-15
Grounding

Zero means nothing without its denominator.

The production run of 15 August wrote 11,663 grounded annotations across the set and recorded zero grounding violations. The second number is only worth reading next to the first one.

A grounding violation, here, is any annotation the engine cannot trace back to a source: a dimension with no geometry behind it, a note with no determination, a code reference with no section. The guard is not a warning — an annotation that cannot be traced does not reach a sheet at all.

That is a deliberately harsh rule, and it costs something. It means the engine will leave a sheet less annotated rather than write a plausible note, and a reviewer will occasionally want a callout that is not there. We think that is the correct side to be wrong on. A drawing that says slightly less than it could is a drafting complaint. A drawing that says something nobody can trace is a liability, and it is exactly the complaint every architect raises first about generated documents.

Publishing both numbers is the same argument in a different form. “Zero violations” on its own is a claim about a system nobody has seen the size of.

End of record

Two notes. This is an engineering record, not a content calendar — the next one lands when something is measured, and it carries the measurement with it.

Architect’s seal Unsealed