How to read an entry

The only fixed page on this site. A minute here lets you decide whether any entry is worth trusting.

Five columns, each answering one question

The columns are a way of looking, not a taxonomy. If your question is 'is the SO-101 any good', everything written about it comes together on its object page.

ColumnThe question it answersWhat you find there
BlueprintsCan I actually build thisWhich files ship, what the BOM costs delivered, how long printing and machining take, where the hard step is
Build oneHow do I get one runningPer-type build guides: what counts as an MVP, parts and sourcing, assembly order, software stack, bring-up, next steps
SoftwareWhich library, and what it takesThe layer it sits at, what it replaces, what starting costs, where it bites. Open and closed source side by side
HardwareWhat to buy, without being fooledThe conditions behind the headline number, price tiers, how to choose, common traps
Claim CheckIs this statement trueWidely repeated claims unpacked: what was claimed, what actually happens, where the gap is, when it closes

There is also This Week, which records what is being checked but has not concluded yet. It does not hand out per-item URLs, because stale news accumulates into a burden.

Read the facts strip before the judgement

Blueprint, software and hardware entries open with a facts strip under the title: file formats, licence, price, repository. These are facts, not judgement, which is why they sit separately — the highest signal-to-noise lines on the page are these.

The most important field in every column is 'what we checked'. It states which items were genuinely verified and which were not, in plain words for the ones that were not.

Why this rule matters

Index sites hand you links. Nobody verifies the facts behind the link — editable source or read-only STL, whether the licence allows commercial use, whether the total includes tax — so you either check it yourself or find out after paying. The difference of this site is that field.

Two field structures

'Claim Check' uses a fixed four-field structure:

The claim
The sentence that gets repeated, stated as close to its original wording as possible. It goes first, and it does not get argued with yet.
Reality
What people who built it, reproduced it or took it apart found. Numbers and specific behaviour where possible, adjectives where not.
Where the gap is
The distance is usually not someone lying. It is a different definition, a different scenario, or a sentence that quietly dropped its conditions.
When it closes
The most valuable field, and the one everyone else omits. Calling a claim wrong is easy. Saying precisely when it does hold is what you can actually make a decision with.

Blueprints, software and hardware each carry their own fields, and the build-one column has its own set — all of them ending with the same field, 'what we checked':

Files you get (blueprints)
Editable engineering files (STEP, PCB sources) or read-only exports (STL, PDF). This decides whether you can ever change the structure.
What counts as moving (build one)
Not 'the servos twitch'. The smallest complete state worth continuing from — stated so you can test yourself against it.
What it solves (software)
Which layer of the stack it occupies. Framed as 'link-layer problem or algorithm problem', not as a feature list.
The spec, and what it measures (hardware)
At what voltage, stall or rated, for how many seconds that number was taken. A figure with no conditions is an order of magnitude at best.
What we checked (shared)
Which items were verified, which were not. When we have not replicated something ourselves we say so — and the grade reflects it, without being inflated.
This site's call

Last comes our own judgement. A judgement is not a fact, which is why it sits in its own block: take the facts and the fields above, leave this one if you like.

Four evidence grades

The letter on each entry does not say whether it is right. It says where the conclusion came from.

GradeSourceEnough for
AOfficial document, standard, first-party dataDefinition questions: how a figure is defined, what a licence permits
BAuthoritative secondary, traced to the originFactual questions: which files a project ships, when something was delivered
COur own estimate, labelled as an estimateNobody has measured it but it can be calculated. A C tells you this is arithmetic, not a test result
DFirst-hand builder account: forum, issue, build logGetting-it-running questions. The rarest grade, and the one that expires fastest

A and D are the two ends of the ruler: what the vendor says, and what somebody actually did. The space between them is what this site records. Most entries here currently sit at B — we have checked the public documents but built none of it ourselves. That gap is stated in each entry's 'what we checked', not hidden.

Every entry carries a date

Information in this field expires, and it expires quickly: dependencies move, firmware changes, models get discontinued or renamed. A conclusion with no date is not a conclusion here.

So every entry ends with a 'last checked' date. If that date is more than six months old, put a question mark next to it in your head — not because it was wrong, but because it may no longer hold.

What we deliberately do not do

  • No Q&A. We do not wait to be asked, because an unanswered question damages trust more than no question at all. When there is a conclusion, it becomes an entry.
  • No news reposting. A story is a lead. It becomes an entry only after someone checks it.
  • No 'best' or 'top pick'. Those words carry no information for someone building: it depends on what you are building, not on the thing.
  • No shopping links. There is no affiliate route anywhere on this site.

The machine-readable version

Every entry also exists as structured data: /data/entries.json. All columns share one entry model (object / facts strip / per-column fields / evidence grade / verification record) for search tools and AI systems to read directly. Sitemap: sitemap-en.xml.

If we got it wrong

All of this site's value sits on accuracy; one bad entry costs a good one. Here is how to tell us. Corrections go into the entry with a date — nothing gets quietly edited.