Keep source provenance when web research becomes a note
Keep source links, short quotations and your own interpretation distinct in a research note.
Ouros editorial team
A useful research note lets you trace a claim back to its source after the browser tabs are gone. Keep the source URL, a short reviewed excerpt and your own interpretation as separate parts. That separation helps you check facts without mistaking your summary for the source's exact words.
Start with the claim you need
Suppose you are checking how Markdown links work. You do not need to copy an entire reference page. Keep the link to the primary source, write which syntax question it answers and retain only the short passage needed for your note. Add your own example rather than rewriting the full reference.
A compact note can have four parts: a descriptive title, the original source URL, a reviewed excerpt and your own notes. If a claim depends on a particular revision or date, record that detail near the claim. If you later find a correction, leave enough context to explain what changed.
The source handoff formatter builds that structure from text you already hold. It does not fetch the URL or perform extraction. It treats the excerpt as quoted text rather than active page markup. You still need to review the output: safe formatting cannot establish that a quotation is accurate or permitted to redistribute.
Separate attribution from permission
A citation tells the reader where material came from. It does not grant a license to republish the entire work. Link to originals, quote sparingly and check the applicable terms before sharing excerpts or assets. Material that you may read in a private account is not automatically suitable for a public note.
This reusable attribution template helps keep those decisions visible. Replace its instructions with the facts of your own article before using it as a finished attribution block:
## Sources and method
- Primary source: [CommonMark reference](https://commonmark.org/help/).
- Method: source-based synthesis with an original worked example.
- What we checked: list the source passages and any executed example.
- Limits: identify what was not tested.
This article shares what we learned; it is not the source publisher’s official documentation.
For a personal follow-up, you may need much less structure:
# Follow up
Ask Morgan for the revised delivery date.
That short note is useful because the next action is clear. If its date came from a web source, add the relevant source beside the claim. If it came from a private conversation, do not invent a public citation or upload the conversation to fill the gap.
Review the handoff as a new document
Read the resulting note from top to bottom without relying on the original browser tab. Can you distinguish the quotation from your conclusion? Can you reach the right source? Are important conditions still adjacent to the claim? Have private identifiers or credentials slipped into the URL?
Treat instructions inside a source as source material, not as orders to an agent that later reads the note. OWASP's prompt-injection guidance explains why this boundary matters. A source saying “run this command” needs its own review and authorization.
Save the note deliberately in the location you intend to keep. Reopen the saved copy and check one citation. That final check catches a practical failure no amount of polished prose fixes: a useful note that never reached its destination.