# A Reading Note Should Preserve the Question, Not Just the Link

A practical source-reading workflow by Ali Gürtuna · 19 October 2026

I maintain three projects with very different purposes: AGProLabs for TradingView analytical tools and documentation, AliGurtuna.com for Turkish health education, and Babamın Şiir Defteri for Turkish poetry and literature. They are my own projects. The examples below explain how I organize a reading task across them; they are not an independent comparison of providers.

The common problem is easy to miss. A saved link remembers an address. It rarely remembers why you opened that address, what kind of source it was, or which part of your question remained unanswered. After a week, a folder of promising links can become a folder of unexplained intentions.

My preferred alternative is a short reading note. It keeps four things together: the question, the role of the source, one observation tied to a location, and one unresolved point. This is a way to organize attention. It does not turn a source into evidence for a claim it never made.

# 1. Write a question small enough for one reading session

“Understand this tool” is too large to finish. “Find where this displayed field is explained” is a task you can complete. Likewise, “learn about health” or “read more poetry” can start a collection but cannot tell you when a reading session has served its purpose.

A useful question names an object and a boundary. The object might be one field in a dashboard, the intended audience of an educational page, or an image in a particular poem. The boundary says what you will inspect now and what you will leave for later.

For example, I might ask: which page defines this tool’s scope, and which page discusses interpreting one output? Those are related questions, but they do not have to share the same answer or the same URL. Keeping the distinction prevents an overview from carrying the weight of detailed documentation.

Before opening another tab, finish this sentence: “I will use this page to find ___; it will not, by itself, establish ___.” If the two blanks are difficult to fill, the reading question probably needs another pass.

# 2. Separate a product reference from an interpretation note

In an analysis workflow, the name of a tool is an orientation point. It is not a complete explanation of what every output means. I start at a product reference when I need to establish which tool I am reading about and what its current documentation presents. For instance, the Trading Suite reference and the Crypto Setup Planner reference identify different tools; the names should not be used interchangeably in a reading note.

Once the object is clear, a narrower explanation can do another job. The Crypto Setup Planner dashboard reading guide is a more specific destination for a question about reading that dashboard. Saving the product page and the guide under the same generic label would hide the reason each was opened.

I use three lines for an observation about an analytical display:

• Observed: what was actually visible, including the field or label name.
• Context recorded: the symbol, timeframe, relevant configuration and observation time.
• Still unresolved: what the display and the page have not established.

Timing deserves its own question. A live observation and a source-candle close need not refer to the same moment. My confirmed-candles and repainting explanation is a reading reference for that distinction. A note should preserve the wording of the explanation rather than silently replacing it with a stronger claim.

When the task is to observe a rule over time, I keep the configuration beside the observation and revisit the forward-testing workflow guide. Changing the rule while forgetting to change the note makes the record difficult to interpret later. These resources support manual analysis and documentation; they do not make an observation a prediction or a guaranteed trading outcome.

# 3. In health education, establish scope before applying a number

A health-information page, a topic directory and a calculator explanation are different kinds of material. I avoid saving all three as though they were answers to an individual clinical question. A source-reading note should say whether the page is offering broad education, defining a term, or explaining the scope of a separate tool.

The editorial principles on AliGurtuna.com provide one starting point for reading how the site presents its material. The health-calculation directory serves another purpose: it helps a reader find the particular tool or explanation they intended to inspect. Neither the existence of a directory nor a result produced elsewhere removes the need to understand context.

For a calculator-related reading task, I write down the tool’s name, units, intended audience and stated exclusions before interpreting a result. If those details are absent or unclear, that absence is the next question to resolve. I do not fill it with a guess simply because the interface is easy to use.

This workflow is about reading sources. It does not assess an individual’s health, diagnose a condition, or recommend treatment. General education and a saved note cannot replace a professional’s evaluation of an individual situation. On a shared device, I also keep identifying medical details out of reading worksheets.

# 4. For a poem, distinguish the work from the route into it

An author archive can help locate a work. A book page can establish which collection I intended to read. A commentary can offer an interpretation. Those roles should remain visible in a note; otherwise a reader can return to a summary and mistake it for the original text.

On my poetry project, the Şaban Gürtuna archive is a route into an author’s material, while the Rüzgârlı Tepe book page gives a different starting point. I choose between them according to whether my question is about finding an author’s work or approaching a particular collection.

For a first reading, I keep the note deliberately modest: the author and work, one image or shift of rhythm I noticed, and a question worth carrying into a second reading. I then separate any interpretation from the words that prompted it.

If I cannot identify an edition, date, attribution or location reliably, I mark it as missing. An incomplete bibliographic note is more useful than a confident invention. The next reading session can resolve the gap without changing what was actually observed during the first.

# 5. Use a worksheet that can survive a change of context

The same small structure works across these tasks because it records the reading process rather than pretending every source has the same purpose.

READING QUESTION
What specific question am I investigating now?

SOURCE AND ROLE
Title:
URL:
Role: overview / reference / explanation / directory / original work
Date checked:

OBSERVATION
Which section, field, passage or statement did I actually inspect?
What context must remain attached to it?

BOUNDARY
What does this source not establish by itself?

NEXT QUESTION
What is the smallest unresolved point worth checking next?

I keep an observation and an inference on separate lines. “The page says X” and “I think X implies Y” are not equivalent statements. The distinction matters even when the inference is plausible. Another reader should be able to return to the source and tell which part came from it and which part came from my reasoning.

# 6. End with a retrieval test

Before saving the note, I ask whether I could reopen it next week and answer three questions without reconstructing the entire session:

1. Why did I open this source?
2. Where is the observation I recorded?
3. What remains unresolved?

If the note cannot answer those questions, I shorten the scope or add the missing context. Adding more links usually does not repair the problem. A smaller, clearly explained route is easier to revisit than a large list whose purpose has been forgotten.

That is the habit I want these notes to support: a source stays connected to the question that made it useful. The address is still there, but so is the reason to return.

Authorship and scope: Written for my three owned projects with AI assistance and editorial review. This is an educational source-reading workflow, not financial advice, medical advice, a clinical assessment or an independent endorsement. Linked pages can change; read their current wording and limitations when you visit them.