How we verify answers
A UppaGo Resource is assembled from source-verified statements, not written as an article. Each step below says plainly whether it uses a language model, is checked mechanically, or is reviewed — by a person or by a separate model. No Resource is reviewed by an accountant or attorney, and no page names an author or an editorial board, because there is none.
1. A real information need reviewed
Each Resource answers one canonical question drawn from a frozen set of 355 U.S. small-business bookkeeping questions, built from observed search demand and reviewed for distinctness. We do not generate a page per search phrase.
2. An answer contract reviewed
Before any source is read, each question carries a contract: the points a complete answer must establish and the class of authority each point requires (a regulator, an accounting standard, official platform documentation, or a professional reference).
3. Primary and professional sources uses a language model
A language model proposes candidate documents for each question. Every candidate is opened and pinned as a byte-exact snapshot with its URL, publisher and date, and rated for the authority class it can actually satisfy. Sources that cannot be captured are recorded as blocked, never quoted from memory.
4. Exact quoted evidence mechanically verified
A language model extracts candidate propositions from each pinned document. A script then checks every quote character by character against the pinned snapshot; a proposition whose quote is not found verbatim is discarded.
5. Statement verification uses a language model
A separate language-model pass certifies each statement once: the sentence may say no more than its quote, the surrounding context must not qualify it, and its scope must match the source. Every verdict is cached against the exact document snapshot; a changed document invalidates it.
6. Explicit scope mechanically verified
Each published statement carries its own scope — jurisdiction, entity type, platform, accounting basis, effective dates — taken from the source, so a rule for one situation is never read as a rule for another.
7. Coverage measurement mechanically verified
Each contract point is decomposed once into fixed requirements. A statement counts toward a requirement only when it is certified and linked to that point; a script computes whether each point is established, partly established, or not established, and at which authority class.
8. Gaps shown rather than guessed mechanically verified
Where the pinned sources do not establish a point, the page says so on that point. Nothing is written to fill a gap. A page is published only when its summary answer is fully certified and at least half of its points are at least partly established.
9. Independent review and sealing reviewed
Before a release is sealed, a bounded sample of pages and citations is read by an independent reviewer — a person or a separate model, never the model that produced the page; findings are corrected with a recorded reason, never by editing a statement by hand. A release is an immutable archive with a checksum; the site serves that archive and regenerates nothing at request time.
What a page tells you
Under the title: the reviewed date and this page. Under the summary: which points the page establishes, partly establishes, or does not establish, and where a point is established only below the authority class the contract asked for. On every statement: its quote, its source and location in that source, its scope, and the date it was verified. Where a topic calls for professional review, the page says so and says that none has taken place.
Every Resource is also served as markdown and as JSON at the same address, with the same statements, so people and machines read the same substance.