Editorial process
How DEPLOY operates
By Ben Smith, Editor
The methodology page at /methodology documents what DEPLOY records and how it represents the data. This page documents how a record gets published: who researches it, how it is checked against its sources, what a person approves, and how changes are tracked.
Research
Records are researched by automated agents. An agent gathers the facts for a record (a company, a robot model, a deployment, an incident, a regulation) and cites a specific source for each one. Before adding a new record, it checks that the record does not already exist, so new information lands on the existing page instead of a duplicate.
Checking against sources
A separate checking agent, not the one that did the research, fetches each cited source again and confirms that the source actually supports each fact attributed to it. A fact the source does not support is removed or corrected before the record is published.
Mechanical checks then reject a record automatically if it has:
- a fact without a specific source behind it;
- sourcing that comes only from aggregator sites, or only from a homepage rather than the page that states the fact;
- a duplicate of a record that already exists;
- malformed facts.
Published records are not individually reviewed by a person.
What a person approves
Some records carry enough weight that a person approves them before they are published:
- market claims;
- insurance information;
- injuries and deaths;
- legal actions against a named company;
- prices shown as verified.
For everything else, a person spot-checks a random sample of published records every week. Problems found in the sample are corrected.
Every change is logged
Every change to a record is logged and can be reversed. Incidents, status changes, and other trust-bearing facts are never overwritten: a correction is added as a new, dated entry, and the earlier one stays on file. Corrections go through the same source checks as new records, and the public corrections log lists records changed since publication.
Verified vs claimed
DEPLOY labels evidence by its quality. A fact is marked verified when an independent or primary source confirms it, and claimed when the only support is the company’s own statement. When the choice is between recording a claim as fact or staying silent, DEPLOY stays silent. A shorter verified record beats a longer one padded with claims.
Standing rules
- Restraint is the product. An honest “not on record” is better than a padded answer.
- Images are licensed or embedded. Media is hosted on DEPLOY’s own storage or shown through a platform embed; images hotlinked from a manufacturer’s site are rejected.
- One canonical page per thing. Each company, robot, place, and event has one permanent identifier and one canonical page, which other DEPLOY pages link to rather than copy.
See also
Methodology for the framework rubric; corrections for the public log of records changed since publication; funding + independence for the operational independence + sustainability position; conflicts of interest for the relationship-disclosure procedure; about DEPLOY for the masthead; glossary for the strict definitions used across the registry.
Machine-readable: this page as markdown.