how it works
How a note is made
Every note on this site is produced by the same automated pipeline. Nothing is written from memory; every fact points at a passage we stored from a real source.
1. A question
A worker model proposes one research question in one of the six fields, phrased as a title of the form topic: how / why / what …?. Only software counts: things that can be built and run. Hardware appears as a design study, never as a build.
2. Sources and passages
Public indexes of papers and code are searched for that question. Each source is stored with its title, authors, year, identifier and URL; from each source we store passages of at most 1 400 characters with a locator (abstract, section heading, README line range). Papers are primary sources; official documentation and code are secondary; an encyclopaedia entry may be read for background but is never cited. A note needs at least four citable sources, two of them primary.
3. Claims
A worker model extracts 8 to 14 claims, each a single checkable sentence tied to exactly one stored passage. A claim that combines passages, adds outside knowledge or cites a passage that only hints is not allowed.
4. Independent review
A different model sees each claim with only its passage and rules: supported, supported with limits (with the condition the claim dropped), or rejected. Rejected claims never reach the text. Every verdict is shown in the claim record at the foot of each note, with the passage excerpt.
5. Draft
The note is written from the verified claims only. Every factual sentence ends with the number of its source. Every note has two practical sections: how to build it or use it, and what we would build from it. Where the evidence is indirect or missing, the note says so.
6. Revision
A stronger reviser rewrites the English to be simple and exact without losing meaning: no fact added or removed, no number changed, no name or technical term rephrased, every citation mark kept. A diff guard checks that every number, name and citation of the draft survived; a revision that loses any of them is rejected.
7. Arabic edition
The same reviser translates the final English into Arabic. Names and technical terms stay in Latin script; numbers stay as they are; the same guard applies. The English page is the reference edition.
8. Publish gate
A note is published only if it has at least six verified claims, every claim points at a stored passage with a locator and a URL, both practical sections exist, the title follows the form, the Arabic edition is complete, and the note cost less than its ceiling. Notes publish automatically when they pass; an unpublish command exists for the owner.
Cost and cadence
The pipeline runs every two hours towards three notes a day under a fixed monthly budget written into the code. Spend and the last run are public at /status.json.
Names
Research may name any paper, lab, company or model it cites. Our own tools are described by what they do, never by an outside brand: the models in the pipeline are a worker model, an independent reviewer and a reviser; our own decision model is called sam.