Wiki

Wiki: How to use summary, original text, and issue history

The summary is the entry point, and the decision is to return to the original source.

Mind Uploading Research Project

Public Page Updated: 2026-03-14 Summary vs source

How to use this page

Read this first to avoid getting lost

This page is an auxiliary guide that organizes how to use Mind-Upload's public page and wiki as an 'entrance for summaries.' There are times when a summary is enough to get an overall picture, but when you need to use it as evidence, make a judgment, revise it, or refute it, you need to go back to the original text, DOI, issue history, and primary research. This page is for reading while aligning those boundaries.

  • Distinguish between situations where you can stop with a summary and situations where you should return to the original text.
  • Illuminates the differences in how to read Papers, Research Harvest, Proposals, and Issues in one page.
  • This is an auxiliary line to prevent the misreading of ``I know it because I read the summary.''
Helpful next pages
Literature map Collection of papers Technical proposal
Best for
People who want to distinguish between situations where they can stop at the summary page and situations where they should return to the original source.
Reading time
8-12 minutes
Accuracy note
We are dealing with reading rules here. When evaluating individual papers or proposals, be sure to check the original page or source.

Relatively clear at this stage

What we know now

  • Many public pages and wikis are useful as a summary entry point to get the big picture first.
  • You must return to the original source when using it as evidence, citing it, or making corrections.
  • The original source to go back to is different for literature archive, literature map, proposal organizer, and issue history.

Still unresolved beyond this point

What we still do not know

  • Future scrutiny will determine which documents and proposals ultimately remain as central evidence.
  • Some summaries will be updated further in the future, and there may be more original sources to return to.

Learn the basics

Check the basics in the wiki

What the wiki is for

The wiki is a learning aid. For the project's official current synthesis, success criteria, and operating rules, always return to the public pages.

Summary is an entry point, not a final verdict

The summary page on this site is useful, but it is not the only way to make a final decision. A summary may suffice at thegetting the big picture stage, but when it comes tousing it as evidence, revising, or rebuttingit is necessary to go back to the original text and history.

When you can stop with a summary

What I want to do Why a summary is enough
I want to know the role of the page You can understand the scope of the page by looking at the page intro and accuracy note of the public page.
I want to take a quick look at what points are being discussed Papers and Research Harvest summaries allow you to quickly grasp the location and volume of issues.
I want to decide which page to return to next The wiki's route page is designed to help you decide the next page.

Scenes that always return to the original source

What I want to do Back to Reason
I want to cite the paper as evidence DOI, original abstract, primary research This is because the details of the method, evaluation, and limitations are lost in the summary.
I want to judge the validity of the proposal Original clause, Technical Proposal, Issue history This is because the integrated summary alone does not reveal the context of acceptance or rejection or the changes in discussion.
I want to open an issue Target page text, evidence link, original paper if necessary Because we need to determine exactly where it stopped.
I would like to make a counterargument or suggestion for correction Original page text and referrer This is because it cannot be determined from the summary alone whether the claim is really made.

The destination to return to is different for each page

Page Part used as summary Back to
Papers List by year, Japanese translation summary, 5 point arrangement DOI, Original Abstract, Original Paper
Research Harvest Map by U, current label, evidence example Individual paper, DOI, and textual basis of corresponding U
Proposals Integrated text, status label, issue correspondence matrix Original clause, Technical Proposal text, Issue history
Issue Status table, evidence links, quick reference table Target page body, implementation location, source for organizing external dependencies

Reading order when lost

  1. Identify "what the story is about" in the summary.
  2. Decide whether to use the story as evidence.
  3. If you want to use it as evidence, always go back to the original text, DOI, and issue history.
  4. If you want to make corrections or suggestions, go back to the main text of the target page and locate it.

Common misreadings

Mistake

  • Read abstract publication as accepted: Abstract publication and final evaluation are separate.
  • Use only reviews and secondary summaries as primary evidence: In important situations, it is necessary to return to the primary research.
  • Determine the correction location using only the issue's rationale link: It is safer to go back to the main text of the target page.
  • Determine whether or not to make changes based solely on the integrated text of the Technical Proposal: You must also check the discussion and original clauses of the original issue.
When you want to confirm whether you really want to proceed after reading the summary

If you have checked the original source but would like to see step by step whether there are any conditions or corrections missing, please see Difference between "I understand" and "Go to the next step".

Where to return next

If you want to go back to the role differences in the literature page, How to read the literature and evidence page, if you want to go back to the proposal page status, How to read the proposal and status labels, if you want to go back from papers to participation, The straight path from literature to implementation/participation Please use.