Get AI summaries of any video or article — Sign up free
Advanced Note Taking in Tana with QCE! thumbnail

Advanced Note Taking in Tana with QCE!

CortexFutura Tools·
5 min read

Based on CortexFutura Tools's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

QCE structures notes around explicit questions, candidate answers (claims), and literature-based support or contradiction (evidence).

Briefing

QCE—Question, Claim, Evidence—turns note-taking into a structured reasoning system that makes it easy to synthesize what research says while exposing gaps in understanding. Instead of collecting notes as a pile, QCE organizes thinking around specific questions, the competing answers (claims) that literature proposes, and the supporting or opposing evidence for each claim. The payoff is practical: every time a claim gets tagged with evidence, the system can automatically aggregate what’s known for and against it, and the resulting “synthesis” view makes it clear what still lacks coverage.

The workflow starts with questions written explicitly in Tana, such as “Who came up with the idea of a research-focused university model?” For each question, the system expects multiple possible answers. In QCE terms, those possible answers become “claims.” Claims are treated as first-class objects in Tana via a “claim” super tag, which is configured to link each claim back to the exact quote it was derived from. That means a claim like “Wilhelm von Humboldt is responsible for introducing the model of the research university” doesn’t float free; it carries provenance through a linked quote and source.

Evidence is then added through an “evidence” super tag. Evidence entries can support or oppose a claim, and the configuration ensures that evidence automatically accumulates inside the relevant claim. Concretely, the claim super tag includes live searches that pull in all supporting evidence and all opposing evidence associated with that claim. As soon as new evidence nodes are tagged, the claim’s evidence lists update immediately—so the researcher can see, in one place, what the literature supports and what it contradicts.

Once claims are wired to questions, the system scales up. A “question” super tag is set up with a topic field and a synthesis area. The synthesis area uses live searches to collect all claims that inform a given question, plus live searches that track sources through multiple reading stages (e.g., “to process,” “to integrate,” and “integrated”). This staged source pipeline matters because large books often answer multiple questions; a global “read/unread” flag can’t capture whether a source has been revisited for a new angle. By tagging sources with the specific question context, the workspace keeps the reading workflow aligned with the reasoning workflow.

An example centers on the history of the research university model. Quotes attributed to Wilhelm von Humboldt are used to create claims and evidence, and the synthesis view then shows which claims connect to the question, which sources are currently being processed for that question, and what evidence exists for or against each claim. The system also makes missing information visible: if a question’s synthesis contains claims but no sources to process, it signals a gap—such as an unanswered “why” behind the model’s invention.

Overall, QCE in Tana is presented as a way to build a navigable knowledge graph for any topic: questions anchor the structure, claims capture competing answers with citations, evidence accumulates automatically, and synthesis views reveal both what’s supported and what remains uncertain.

Cornell Notes

QCE (Question, Claim, Evidence) provides a note-taking structure that links what someone wonders about to what the literature says and how strong that support is. In Tana, questions are tagged, then possible answers become claims, and quotes or passages become evidence that can either support or oppose each claim. Live searches inside the claim super tag automatically aggregate supporting and opposing evidence, so each claim’s status updates as new notes are added. A question-level synthesis area then gathers all claims that inform a question and tracks sources through multiple reading stages (to process, to integrate, integrated). This setup helps researchers synthesize efficiently and spot gaps where a question has claims but lacks evidence or remaining sources to read.

How does QCE prevent notes from becoming an unstructured archive?

QCE forces every note to attach to a specific reasoning role: questions define the target, claims represent candidate answers, and evidence supports or opposes those claims. In Tana, the “claim” super tag is configured with live searches that pull in supporting evidence and opposing evidence tied to that claim, so the workspace continuously reflects the current state of support. The “question” super tag then gathers the claims that inform the question into a synthesis area, turning scattered reading into a structured argument map rather than a folder of excerpts.

What makes a claim more useful than a standalone statement?

A claim becomes actionable when it carries provenance and context. The system links each claim to the quote (and source) it was derived from, using a field that references the quote node. It also records which question the claim informs (via an “informs question” field promoted into the claim super tag). That way, when a researcher sees a claim in synthesis, they can immediately trace back to the exact textual basis and the question it answers.

Why split evidence into “supporting” and “opposing” rather than mixing everything together?

Support and opposition answer different epistemic questions: what the literature backs versus what it challenges. The claim super tag is set up with separate live searches for evidence where the “supports claim” field is set to the claim’s parent and where the “opposes claim” field is set to the claim’s parent. As a result, the claim’s view shows two distinct lists, making contradictions and weak points easier to spot during synthesis.

How does the system handle the reality that one book can answer multiple questions?

Instead of relying on a single global read/unread status, sources are tagged with stage-specific fields tied to the question context. The question synthesis area includes live searches for sources in three stages—“to process,” “to integrate,” and “integrated”—and each search filters sources based on a field that references the relevant question node (using parent/grandparent logic depending on the hierarchy). This lets the same source appear under different questions with different progress states, reflecting how researchers revisit the same material for new angles.

What does “gap detection” look like in this workflow?

Gaps show up when the synthesis view has claims but lacks evidence coverage or remaining sources to read. For example, if a question’s synthesis lists related claims but the “sources to process” section is empty, it signals that the researcher may not yet have gathered enough literature to answer the deeper “why/how” behind the claims. The structure makes uncertainty visible because evidence accumulation and source pipeline are both tied to the question and claim objects.

Why use live searches and super tags instead of manual linking?

Live searches automate aggregation. Once the super tags define how fields relate (e.g., evidence supports/opposes a claim; claims inform a question; sources belong to stage fields), tagging a new node updates the relevant synthesis views automatically. This reduces repetitive bookkeeping and keeps the workspace consistent as the research grows.

Review Questions

  1. When would you create a new claim versus adding more evidence to an existing claim in this system?
  2. How do parent/grandparent references affect which nodes a live search returns in Tana’s hierarchy?
  3. What signals in the synthesis view suggest that a question still lacks enough evidence to support a conclusion?

Key Points

  1. 1

    QCE structures notes around explicit questions, candidate answers (claims), and literature-based support or contradiction (evidence).

  2. 2

    In Tana, claims are linked to the exact quote they were derived from, preserving provenance for later synthesis.

  3. 3

    Evidence is categorized as supporting or opposing a claim, and live searches aggregate both categories automatically inside each claim.

  4. 4

    A question-level synthesis area collects all claims that inform the question, creating a single argument map per topic.

  5. 5

    Sources are tracked through multiple reading stages (to process, to integrate, integrated) per question, avoiding misleading global read/unread flags.

  6. 6

    Using topic fields lets related questions and their synthesis views be grouped, making it easier to navigate large research projects.

  7. 7

    The system makes knowledge gaps visible when synthesis contains claims but lacks evidence or remaining sources to read.

Highlights

QCE turns note-taking into a reasoning workflow: questions → claims → evidence, with support and opposition kept separate.
Claims become traceable by linking them directly to the quote and source they originate from.
Live searches inside super tags automatically aggregate evidence and claims, so synthesis updates as new notes are added.
Staged source tracking per question handles the common problem of one book answering multiple questions.

Topics

Mentioned