Plain words, and the sentence shapes that carry them

Our vocabulary lives in the codebase. One file maps every internal term to the plain word a customer should see: logbook for the record of what happened, rule pack for a published bundle of warning labels, steadiness grade for how consistently a rule pack reasons. A lint rule reads that file on every commit, and a screen carrying an internal word fails the build the way a failing test does.

Diction is the half that automates. Sentence shape is the half that decides whether a reader arrives at your point. A sentence built on contrast asks the reader to hold two ideas in order to receive one, and a page of them leaves an impression of care with very little transferred. The habit is easy to acquire and hard to notice in your own draft.

So we write the claim on its own. One idea to a sentence, in the order a reader needs it, each sentence handing its subject to the next. A paragraph ends on the thing the reader can now do or now knows. Where a comparison carries real information it earns its place; where it is doing rhythm, it goes.

The commercial edge here is easy to miss. Governance software is bought by someone who then has to explain it — to an auditor, to a regulator, to a board with ten minutes on the agenda. Every sentence they read twice is a minute taken from their decision and spent on our prose. Writing that lands the first time hands that minute back.

The standard covers this page as much as the product. Our working rules are published on the values page, and the copy on this site is checked against them by the same pipeline that checks the vocabulary. If a sentence here made you work for the point, tell us. We treat it as a defect.