Source-Grounded Research
Build conclusions from evidence that can support the exact claim being made.
Workflow
- Restate the research question and the decision it informs.
- Search current sources when facts may have changed, the user asks for research, or direct attribution would help.
- Prefer primary authorities: official documentation, original datasets, statutes, filings, research papers, provider status, or first-party announcements.
- Use discovery pages, aggregators, and community discussion to find leads or understand reactions, not as substitutes for factual authority.
- Capture the source URL, publisher, publication or observation date, relevant units or population, and any material limitation.
- Compare sources on the same definition and time basis. Flag incompatible scopes instead of forcing a ranking.
- Distinguish observed facts, source claims, inference, proposal, and unresolved questions.
- Recheck volatile facts immediately before reporting them.
Knowledge lifecycle handoff
When the user is building a traceable research or publication lifecycle, prepare source records compatible with knowledge-contract.v1 rather than inventing a second schema. For each material source, preserve a stable project-scoped ID, canonical publisher URL, publisher and author identity, publication and retrieval dates, as-of meaning, access conditions, license, methodology warnings, domains, topics, tags, entities, verification status, limitations, and relationships.
The source record is a handoff, not a publication decision. Catalog inclusion does not prove endorsement, permission, maintenance, or model fitness. Route an authorized end-to-end research, model, outcome, evaluation, and publication workflow to research-to-publication-lifecycle when that skill is installed.
Evidence rules
- Link the page that directly supports each material claim.
- Keep quotations short; prefer faithful paraphrase.
- Preserve original publisher URLs rather than search-result or repost links.
- State when access limitations required an alternative readback method.
- Do not manufacture precision from incomplete, stale, or differently defined data.
Output
Lead with the conclusion, then give a concise evidence table containing Finding, Status, Source, Date, and Limit. End with unresolved questions or recommended verification where needed. When a knowledge-lifecycle handoff was requested, also return the proposed source IDs and public-safe source fields without writing them unless the user authorized a named destination.
1---2name: source-grounded-research3description: Research a question using current primary sources, preserving publisher URLs, dates, units, provenance, and uncertainty. Use for web investigations, fact checks, comparisons, or recommendations where current evidence and precise attribution matter.4license: MIT5---67# Source-Grounded Research89Build conclusions from evidence that can support the exact claim being made.1011## Workflow12131. Restate the research question and the decision it informs.142. Search current sources when facts may have changed, the user asks for research, or direct attribution would help.153. Prefer primary authorities: official documentation, original datasets, statutes, filings, research papers, provider status, or first-party announcements.164. Use discovery pages, aggregators, and community discussion to find leads or understand reactions, not as substitutes for factual authority.175. Capture the source URL, publisher, publication or observation date, relevant units or population, and any material limitation.186. Compare sources on the same definition and time basis. Flag incompatible scopes instead of forcing a ranking.197. Distinguish observed facts, source claims, inference, proposal, and unresolved questions.208. Recheck volatile facts immediately before reporting them.2122## Knowledge lifecycle handoff2324When the user is building a traceable research or publication lifecycle, prepare source records compatible with `knowledge-contract.v1` rather than inventing a second schema. For each material source, preserve a stable project-scoped ID, canonical publisher URL, publisher and author identity, publication and retrieval dates, as-of meaning, access conditions, license, methodology warnings, domains, topics, tags, entities, verification status, limitations, and relationships.2526The source record is a handoff, not a publication decision. Catalog inclusion does not prove endorsement, permission, maintenance, or model fitness. Route an authorized end-to-end research, model, outcome, evaluation, and publication workflow to `research-to-publication-lifecycle` when that skill is installed.2728## Evidence rules2930- Link the page that directly supports each material claim.31- Keep quotations short; prefer faithful paraphrase.32- Preserve original publisher URLs rather than search-result or repost links.33- State when access limitations required an alternative readback method.34- Do not manufacture precision from incomplete, stale, or differently defined data.3536## Output3738Lead with the conclusion, then give a concise evidence table containing `Finding`, `Status`, `Source`, `Date`, and `Limit`. End with unresolved questions or recommended verification where needed. When a knowledge-lifecycle handoff was requested, also return the proposed source IDs and public-safe source fields without writing them unless the user authorized a named destination.
JovaniPink