The empty spec/ folder is the feature

Three NOKTRA instruments share a design decision that looks, at first glance, like a missing feature. RAM Toolkit ships with no MIL-HDBK-217F coefficients. Ch10 Viewer ships with no IRIG 106 packet layout. SECS/GEM Workbench ships with no SEMI wire constants. Out of the box, each one tells you plainly that it is blocked, and parses or computes nothing that depends on the standard.

The mechanism is the same in all three: a plain-text file in spec/, next to the executable, that a human fills in from their own copy of the standard — each value with a citation to the section and page it came from. The loader refuses any row without a source. Fill the file in and the whole product comes alive, with no rebuild and no code change.

Why ship it empty? The first reason is legal and boring: these standards are licensed documents, and their constants are not the tool vendor's to redistribute. But the deeper reason is about failure modes. A reliability figure derived from a half-remembered coefficient, a flight-test channel decoded with a guessed byte offset, a SECS frame parsed with a format code lifted from someone else's implementation — these do not fail loudly. They produce plausible numbers that are wrong, and plausible-but-wrong is the most expensive failure class in verification, because it is discovered after the analysis, by someone else.

The transcription step converts an invisible risk into a visible chore. Yes, someone must spend an afternoon with the handbook and a text editor. In exchange, every constant in the pipeline has a name attached — this value, from this table, on this page, entered by this person. When an auditor asks where a number came from, the answer is a citation, not an archaeology project. RAM Toolkit goes one further: every report states which spec excerpts were in force when it was generated.

There is also a quiet capability hiding in the mechanism. Because the layout is data, not code, a non-standard variant — a vendor's private extension, a program-specific framing — is handled by editing a text file, not by requesting a build from the vendor. The gate that enforces honesty doubles as the extension point.

The pattern generalises to a rule worth stealing: when a tool's correctness depends on a document it cannot legally or reliably contain, the tool should carry the document's shape and refuse to guess its contents. Shipping less, loudly, beats shipping more, wrongly.