Search the field guide, causes, requirements, and glossary

Editorial standards

Every page here is built from sources you can check, and nothing goes live until Ben Rutter approves it.

On this page8 sections
  1. Sources come first
  2. How a page is made
  3. Field experience
  4. Independence
  5. Safety scope
  6. Corrections and updates
  7. Keeping pages current
  8. Source types

This page sets out the rules every page on OT Wireless follows. It states only what the site’s own build checks or what Ben does on every page, so it promises nothing the process does not do.

Sources come first

Each page keeps a ledger of its sources: the address, title, publisher, the date it was read, and the claim each source supports. The ledger is the review record. Each page’s “About this page” panel shows how many sources it rests on, by type.

Guides and cause pages draw on at least three independent sources. The content check refuses to publish one with fewer. A claim that rests on a single source is listed for review before the page goes live.

Primary sources come first: standards bodies, regulators, protocol owners, vendor technical documentation, and research papers. A vendor’s marketing claim is labeled as a claim.

Specific numbers, formulas, and spec values carry a small numbered link to their source. Every value in the requirements database has one, each entry lists its documents with the date they were read, and “not published by the vendor” is a valid value.

If a claim cannot be sourced, it is not written.

How a page is made

  1. Research. Sources are gathered before any writing starts.
  2. Drafting. Pages are researched and drafted with AI assistance, in the site’s own words and structure. No page rewrites a single article.
  3. Checks. Every change runs an automated content check for sourcing minimums, the safety flag, style rules, and names that must not appear. Drafts from the site’s automated desk also get a separate AI fact check against their sources before Ben sees them.
  4. Approval. Ben reads every page and approves it before it goes live. The production build ships only approved pages, and each page shows the date it was approved.

Signal, the daily digest, is found and drafted by an automated news watcher. Each day’s items go live only when Ben approves them.

The tools run in your browser. They show their working and never call an AI model.

Field experience

Field notes come only from Ben’s own observations, with every company and site name removed. AI drafting never writes first-hand experience. A page without a field note makes no first-hand claim.

Independence

The site carries no ads, affiliate links, sponsored content, or paid placement, and it collects no sales leads.

Wi-Fi infrastructure products are not named, ranked, or compared. When a vendor’s public document supports a point, it is cited by link with neutral attribution.

Ben works in the industry, and his employer is named on the About page. The views here are his own. His employer’s material is never cited, and its products never appear.

No customer, end user, or plant operator is named anywhere on the site.

Safety scope

This site covers availability, not safety engineering. It never tells you a system is safe or how to make one safe. Pages that touch stopping, functional safety, or vehicle speed carry a disclaimer. Safety functions, reaction times, and stopping distances come from the machine builder’s risk assessment and the applicable standards.

Corrections and updates

Every page shows when it was first published and when it was last updated.

Once a page is live, any change beyond a typo or formatting fix adds a dated entry to the page’s change history. An error of fact is labeled “Correction”. Changes are never made silently.

To report an error, message Ben on LinkedIn. Every report is read. No response time is promised.

Keeping pages current

An automated watcher reads new sources and drafts updates to pages they affect. Every update goes through the same approval as a new page. Requirements entries show the date their values were last verified.

Source types

Each page’s “About this page” panel counts its sources by these types.

Standards bodies and labs
Bodies that write consensus standards or publish measurement science: IEEE, IETF, IEC, ISO, ETSI, ITU, 3GPP, ISA, and NIST.
Regulators and government sources
Regulators and government publishers, and the official text of regulations: the FCC, ISED, OSHA, the EU, and the Code of Federal Regulations.
Protocol owners and alliances
The organizations that own an industrial protocol or a wireless certification: ODVA, PI, the OPC Foundation, the Wi-Fi Alliance, and similar groups.
Research papers and theses
Academic papers, preprints, and theses. Not all are peer reviewed; preprints and theses are labeled as such where they carry a number.
Vendor documents
Product makers' technical documentation and design guides. Marketing claims are labeled as claims in the text.
Other sources
Trade press, practitioner writing, and other publishers.

About this page

Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made

First published
Last updated
Change history (1)
  • First published
Cite this page

Plain

Ben Rutter. "Editorial standards." OT Wireless, published October 6, 2026, updated October 5, 2026. https://otwireless.com/standards/

APA 7

Rutter, B. (2026, October 6). Editorial standards. OT Wireless. https://otwireless.com/standards/

BibTeX

@misc{rutter2026standards,
  author = {Rutter, Ben},
  title = {{Editorial standards}},
  year = {2026},
  howpublished = {\url{https://otwireless.com/standards/}},
  organization = {OT Wireless},
}