theory pages reading guide - yasufumi-nakata/mind-upload GitHub Wiki
Strength of argument, design principles, and a map to avoid mixing dependencies
This learning page is generated for GitHub Wiki. The public portal is managed on mind-upload.com.
- Updated: 2026-03-14 / Role: Reading guide
This page is an auxiliary guide to help you distinguish between Mind-Upload's theory-oriented public pages. WBE 101 is an introduction, Perspective is a long research note, the theoretical frame section in Perspective is a design principle, and Roadmap is a map of dependencies, so they do not have the same role.
What we are dealing with here is the difference in the roles of the pages. Please check the validity of the theory and the verification conditions themselves on each main text page.
- Wiki: Guide to reading public pages - This is for people who want to see the differences in roles across the public pages, not just those who are interested in theory.
- Wiki: Theory of Consciousness Map - We will clarify the differences between IIT, GNWT, FEP, and PCI from the beginning.
- Wiki: Identity and copying issues - Compensates for problems with identity and copying that appear on theory pages.
- Wiki: How to read the roadmap - This is for people who only want to check the roadmap symbols and how to read them first.
- WBE 101, Perspective, the theoretical frame section within Perspective, and Roadmap are all theoretical, but their roles are different.
- WBE 101 is the entry point for aligning the strength of the argument, Perspective is a long text listing the basis and limitations, the theoretical frame section within Perspective is the design principle, and Roadmap is the map of dependencies.
- If you separate the roles of pages first, it will be difficult to misread the theory.
- Which combination of theories will ultimately be a sufficient condition is still undetermined.
- Which theory pages will be expanded independently in the future will change depending on the accumulation of points.
The theory pages are all about "theory," but the difference lies in what the page decides. If you first divide it into Introduction, , Design principles, and Dependency map, the reading order will be much more stable.
When you want to decide the next page after getting started with WBE
If you would like to see not only the differences in the roles of the theory pages as a whole, but also where to proceed after WBE 101 in terms of clearing up misconceptions, design principles, long notes, and dependency maps, please take a look at Four routes that dig deeper into theory from an introduction to WBE.
| Page | Main role | First question | What is not enough here |
|---|---|---|---|
| WBE 101 | This is an introduction. Align the strength of your argument. | The first thing you want to do is decide whether this is really close to WBE. | This is not enough to explain the details of the theory and organize the lengthy counterarguments. |
| Perspective | This is a long research note. Lay out theories, measurements, and limits. | This is when you want to follow the supporting points and weaknesses of each theory for a long time with evidence. | It is not suitable for shortening the reading order or extracting only design principles. |
| Theoretical frame clause | This is the design principle. Organize it as a dynamic migration rather than a static copy. | This is when you want to know why this site takes the position it does, beyond the connection between philosophy and engineering. | It is necessary to supplement the extent to which the position has been proven with Verification and Perspective. |
| Roadmap | A map of dependencies. List what to solve first. | This is when you want to know where the theoretical issues fall into measurement, reconstruction, implementation, and verification. | The context of background explanations and criticisms of individual theories has been compressed. |
| FAQ | Q&A at the entrance. Shorten and reduce misunderstandings. | Before we get into the theory, it's time to clear up some common misconceptions. | Since this is a short answer, you will need to return to the main text for detailed explanations of theory selection and limitations. |
| Glossary | Term scaffolding. Match the meanings of words. | It's time to stop at the meaning of theoretical names and measurement words. | The glossary alone does not determine the differences in roles between pages or the strength of the arguments. |
| What I want to know now | First page to open | Next page |
|---|---|---|
| I want to know what stage of WBE the news and announcements are at | WBE 101 | FAQ and Verification. |
| I want to follow the supporting points and weaknesses of the main theories in a long text | Perspective | Theoretical Frame Section returns to design principles. |
| I would like to know the position on the copy issue and dynamic migration first | Theoretical frame section | Perspective to provide evidence and limitations. |
| I want to know which technical issue the theoretical issue falls into | Roadmap | Verification. |
| Before going into the theory page, I would like to clarify a short misunderstanding | FAQ | Go back to WBE 101 or Perspective. |
| The meaning of theory names and terms is ambiguous | Glossary | Theoretical Frame Section and Perspective. |
| Groups that look alike | The difference in one word |
|---|---|
| WBE 101 / FAQ | WBE 101 is a comprehensive introduction, and FAQ is a short answer to your questions. |
| Perspective / Theoretical Frame Section | The Perspective is a long text that lists the basis and limitations, and the theoretical frame section within the Perspective is a section that narrows down the design principles to be adopted. |
| Theoretical frame section / Roadmap | The theoretical frame section is a fixed position, and the Roadmap is a map of which issues that position falls on. |
| Perspective / Roadmap | Perspective looks at the depth of issues, and Roadmap looks at dependencies between issues. |
- Starting suddenly from Perspective: Since there is a large amount of information, it is safer to prepare your argument level in WBE 101 first.
- Read the Theoretical Frame section as a proven conclusion: This is a summary of the design principles, not a declaration that the proof is complete.
- Read Roadmap as theory text: This is a dependency map, with condensed theory background.
- Complete the theory judgment with just a short answer to the FAQ: The stronger the argument, the more you need to go back to Perspective and Verification.
Please use Start Page to return to the entrance, Public Page Reading Guide to return to the role differences of all public pages, and Consciousness Theory Map to return to the basics of theory names.