Project documents and revisions
A project can contain an overview, chapters, calculations, datasets, images and exports. Follow the source relationships as well as the introduction. Record the published revision and the file or section behind a claim so another reader can examine the same evidence.
A proof or timestamp supports the particular event or record it identifies. Assess the content itself through its sources, method and relevant expertise. When material changes, distinguish the earlier statement from the corrected revision.
Research sources
The research stream draws on arXiv's artificial-intelligence and machine-learning categories and Hugging Face Daily Papers. Entries link to their source so you can read the paper, inspect its authorship and follow associated code or data.
Check the paper's stated publication and review status, version, method and limitations. Daily selections and discussion indicate what people are reading; the source paper supplies the research claim and its supporting evidence.
News publishers
News cards identify their publisher and lead to the original story. Sources include MIT Technology Review, Ars Technica, TechCrunch, The Verge, The Register, IEEE Spectrum and MIT News.
Use the original article for its full context, publication date, updates and references. The publisher's access conditions and publication rights apply at the source. A source's inclusion identifies where the story came from; assess each story on its own evidence.
Keep your AI's answer traceable
Ask your AI to retrieve the actual material it cites and separate author statements, supporting evidence, assumptions and its own analysis. Keep the original links and revision information in the answer. Follow up on a claim whose source is unclear before relying on it.
Community activity, upvotes and visibility boosts describe interest and discovery. Preserve their meaning and date when discussing them. Decisions about work, purchases or funding call for the assessment appropriate to those decisions.
For each important claim, cite the source file or passage, state whose claim it is, and explain what the evidence establishes. Identify assumptions and your own inferences separately.
Read the rights behind the reference
For a dataset, model, code release, document or recording, identify the exact object, revision, rights holder and stated licence. Check third-party components and separate permissions for reproduction, adaptation, redistribution, commercial use and model training where relevant. Public access and citation leave these reuse conditions in force.
An identity check, ownership claim, signature receipt, hash and timestamp each evidence their stated fact or event. Verify what was checked, by whom and when. Establish the grantor's authority and the rights actually granted from the underlying documents and applicable law. A network record's legal effect depends on that evidence and any required legal form.
Corrections and source concerns
Authors should correct material errors promptly and keep active information current. For a rights or safety concern, identify the public source and relevant passage when reporting it. Share only the information needed to explain the concern.