Cite the source of a claim
Create a research brief with a source beside each major claim. Distinguish supporting evidence, conflicting evidence, and background context.Evidence components can point to a specific saved dataset version and quoted passage. Source entries can retain metadata and excerpts with a link to the original destination. A source preview is not necessarily a live website embed. Retained excerpts and metadata describe the saved material; they do not continuously refresh the source.
Compare revisions
Supported comparisons include text, datasets, and images. Label both versions and use stable record keys when comparing datasets.Compare last month’s dataset with this month’s by account ID. Separate added rows, removed rows, and changed values. Include the dataset revisions.
Show a before/after text comparison of the two proposed plans and summarize the practical differences.An old source or broken anchor should be shown as unavailable or unresolved rather than reassigned to a different passage.
Separate facts from assumptions
Pair evidence with explicit assumptions, risks, or a scenario explorer. A calculated result can be internally consistent without its inputs being verified facts. Ask for dates, units, source limitations, and missing information. Keep sample data labeled as illustrative.Review with comments
Use a whole-Page comment for a broad objection or a passage comment for a specific claim. Ask for changes attaches the selected passage and revision to a request for the author. Comments do not grant extra source access. A viewer may be able to read the Page while lacking permission to open a linked private resource. See Comments and passage changes, Data, and Images.Import a result from Git
Use Import Git output to retain Markdown or self-contained HTML from a repository as a Page. Select the repository, provide the full 40-character Commit SHA, and enter the Output path, such asreports/analysis.md.
The imported Page is a snapshot of that committed output. Later commits do not update it automatically. Use Import as new version when you want an existing imported Page to reflect a newer committed result.
Keep the commit and source path explicit when you need reproducible provenance. Importing content does not make the source repository accessible to every Page viewer.