Border surveillance reference: glossary, acronyms, readiness levels

Most of this site argues something: that range is not coverage, that a framework is not a network, that autonomy is a statement about driving. Arguments need context, and context costs a reader time they may not have come to spend.

These three pages are the opposite. They assume nothing, argue nothing and are built for somebody who has met a term in a document and wants to know what it means before going back to the document. That is a different job from explaining, and mixing the two produces pages that do neither well.

The three lookups answer three different shapes of question, which is why they are three pages and not one. The glossary answers what does this word mean here. The readiness scale answers how far along is this thing, which is the question behind almost every disagreement about whether a system exists. The comparison tables answer how do these sit against each other, and they are the only place on the site where figures from different sources are set side by side deliberately. Each is usable on its own by somebody who never reads the other two.

The separation also serves a second purpose. A glossary that defines terms as the source documents use them is a check on the rest of the site: if a page here used a word in a way the glossary does not support, one of the two is wrong, and both are visible.

There is a discipline that comes with that, and it is the part most reference pages skip. These entries do not define terms the way this site would prefer them defined. Where two instruments use the same word differently — and in this field they routinely do, because research vocabulary and operational vocabulary grew separately — both readings appear, with the document each belongs to. A single tidy definition would be easier to read and would quietly take a side.

The same rule applies to scales. Where the sources give a numbered scale, the entry uses it and names the instrument it comes from. Where they do not, no scale is invented to fill the gap, even when one would make a table look complete. A missing row is honest; a fabricated one is not recoverable by a reader who has no way to tell the two apart.

Definitions age, which is the running cost of keeping a section like this. A term shifts meaning when a new instrument adopts it, and an entry written against the old one becomes quietly wrong rather than obviously wrong. Every entry therefore carries the document it was taken from, so a reader who suspects it has moved can go and check rather than take this page's word for it.

Acronyms deserve a note of their own, because they are the most common way a reader gets quietly lost. In this field an acronym is rarely unique: the same three letters can name a programme, a piece of equipment and an administrative body, and the reader is expected to know which from context that a search result does not carry. The glossary therefore expands acronyms in full and says which domain each expansion belongs to, rather than assuming the one the reader is most likely to have met.

There is also a vocabulary problem that no glossary can fully solve, and it is worth naming rather than hiding. Research language and operational language describe the same equipment with different words and different implied claims. A research document will call something a capability at a readiness level; an operational document will call the same thing a system in service or not mention it at all. Neither is wrong within its own register, and a sentence that moves between the two without saying so has changed its meaning without changing its words.

Finally, these border surveillance reference pages are built to be arrived at directly. A reader who lands on the glossary from a search engine, takes one definition and leaves has used this section exactly as intended, and none of the three pages assumes anything read before it. That is why they carry no argument: an argument would need the reader to stay.