-
Notifications
You must be signed in to change notification settings - Fork 7
FEE 871 Mapping claims and evidence #1247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
KarolaKirsanow
wants to merge
10
commits into
DiscourseGraphs:main
Choose a base branch
from
KarolaKirsanow:mapping-claims
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
d10fc8e
scaffold article
KarolaKirsanow dfe35aa
typo
KarolaKirsanow 117b201
update article
KarolaKirsanow b4a9728
vlence
KarolaKirsanow c3c69df
delete llms.txt
KarolaKirsanow 35ad0da
Merge branch 'DiscourseGraphs:main' into mapping-claims
KarolaKirsanow b4fba2a
Merge branch 'DiscourseGraphs:main' into mapping-claims
KarolaKirsanow 786d105
typos
54ee9b7
convert to mdx
8bf8f7f
revert to md
KarolaKirsanow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
47 changes: 47 additions & 0 deletions
47
apps/website/content/obsidian/fundamentals/mapping-claims-and-evidence.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| --- | ||
| title: "Mapping claims and evidence" | ||
| date: "2026-07-23" | ||
| author: "" | ||
| published: true | ||
| --- | ||
|
|
||
| ## Building an argument | ||
|
|
||
| **Discourse Relations** (_i.e._ supports, informs, opposes) are a means of illustrating the relationships between different discourse nodes related to your animating Question. We can use discourse relations to wire together claims and evidence from a single source, or (perhaps more interestingly) to connect evidence from multiple sources that is relevant to a claim or group of claims. | ||
|
|
||
|  | ||
| _Different claims may be supported or opposed by evidence from different sources_ | ||
|
|
||
| In the image above, a single article provides two different pieces of evidence _supporting_ a particular claim, while an experiment and a simulation result both _oppose_ a second claim. A third source provides both supporting and opposing evidence for a third claim. | ||
|
|
||
| Such a constellation of conflicting claims and evidence is relatively uncommon within a single article (excluding meta-analyses), where claims and evidence share a single author, but very common when sources are intermingled. | ||
|
|
||
| The discourse graph breaks the interpretive frame imposed by the article. Working across analytical boundaries in this way makes the thoughtful use of _relations_ paramount: once freed from the inferential structure of their source material, claims and evidence require solid grounding to be fruitfully integrated into your graph. This includes accurately linking evidence to the relevant claim, evaluating the strength of the evidence (independent of its valence), and often taking a closer look at the method that produced the evidence to assess whether a replication or different approach is warranted. | ||
|
|
||
|  | ||
| _Linking evidence to claims, assigning weights to evidence, assessing sources_ | ||
|
|
||
| ## Orienting your map | ||
|
|
||
| In addition to carrying semantic information about the relationship of different nodes to each other, relations help to orient your graph in conceptual space. | ||
|
|
||
| ### Spotting gaps in methodology | ||
|
|
||
| A researcher clustering sources by methodology, for instance, might find that conflicting support for a particular claim could potentially be resolved by using a method from a more distant conceptual space. | ||
|
|
||
|  | ||
| _Mind the gap: there are ideas for different experiments to be found within!_ | ||
|
|
||
| ### Finding unsynthesized claims | ||
|
|
||
| Similarly, a researcher performing a literature synthesis might find that certain extracted claims require more substantiation -- either by revisiting the literature to make sure all of the authors' evidence has been captured, or by designing a new study. | ||
|
|
||
|  | ||
| _Gap spotting in a literature synthesis_ | ||
|
|
||
| ## Gathering your party and venturing forth | ||
|
|
||
| Just as a map without roads would lack important information about the best routes to places of interest, a discourse graph without relations leaves out important information about which scientific roads are well-traveled -- and which less-traveled paths might lead to treasure. | ||
|
|
||
|  | ||
| _There is no fast travel in science ..._ | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 New documentation page uses the wrong file extension for a plain-text article
The new article is saved as an MDX file (
apps/website/content/obsidian/fundamentals/mapping-claims-and-evidence.mdx) even though it contains only plain prose and images, while the project's documentation rules reserve MDX for pages that use components.Impact: The page deviates from the documented file-naming convention for docs, making the content tree inconsistent.
Convention source and file contents
skills/update-user-docs/references/doc-conventions.mdstates: "Use.mdfor normal prose pages and.mdxonly when the page needs components." The new page contains only headings, paragraphs and image links — noNodeTag,Callout, or other MDX components — so it should bemapping-claims-and-evidence.md, with the_meta.tsslug unchanged (apps/website/content/obsidian/fundamentals/_meta.ts:6). Note the sibling prose page in the same directory isbase-grammar.md.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.