Sourcing policy

The sourcing policy

This page describes exactly what the engine reads, how it decides a claim is confirmed, and what the label on a finished article means. It is public so the promise is checkable.

What it reads

Only the domains you choose for that subject area. The list is visible and editable, and nothing outside it is fetched — not a search result, not a link found on a page it read.

Search is cheap; reading is billed by the page. So results that share an origin are grouped before anything is fetched, and then one page per origin is read. Fifty results become one search and six fetches, and the forty-four relays become the evidence that a claim is circular rather than confirmed.

Excluded outlets

An outlet is excluded or re-scored only through a sourcing review: the ask, the reason and the topics affected are written down, two members of staff vote, and the decision is published here with its date. Exclusions are reviewed monthly. The current list, each entry with its review and date, is at brenzuri.com/policy/excluded. Anyone can ask for a review; we answer within 10 working days.

How a claim is judged

The finished text is broken into claims, and each one is checked against the origins — independent origins, not source count. Three outlets carrying one wire is one origin.

CorroboratedTwo or more independent origins report it. It reads plainly, with no marking.

Single-sourceOne origin reports it and no other corroborates it. Underlined, and it stays in the text — removing it would hide the most useful thing the check produces.

CircularSeveral outlets carry it, but they all trace back to the same wire. Counting sources calls this corroborated; it is not, so it gets its own colour — it is the state most likely to fool a reader.

DisputedIndependent origins report it differently. Both are primary reporting, so neither is dropped; the disagreement is shown.

ParallelTwo sources say the same sentence about their own separate subjects — each vendor describing its own product. Naive counting calls it corroboration. It is split and attributed instead.

The check happens twice

Claims are checked before the article is written, from what the origins say. Then the finished article is checked afterwards by a second pass against the claims and source excerpts, with figures and quotes matched literally, because the first check cannot see the sentences the writer produced.

The label

An exported article carries one line: whether a human reviewed that exact version. It is computed from the approval record and cannot be set by hand — not by a setting, not by an API key, not by us.

A person approves, always. It is the one point where a company's name goes on the text, so no key, token, agent or staff account can do it.

When a claim cannot be confirmed

You still get the article, and it still costs the same — the reading and the checking happened either way. What you do not get is an article that hides which parts nobody could confirm.