A guide to using the page intro, known/unknown, wiki links, and overview as an entry point

This learning page is generated for GitHub Wiki. The public portal is managed on mind-upload.com.

• Updated: 2026-03-06 / Role: Reading guide

This page is a companion wiki that explains how to read the guidance blocks that commonly appear at the top of public pages. Before entering the main text, it helps you align the role of the page, the boundaries of its claims, and the route back to the learning wiki.

This page explains reading rules. For the facts and technical conditions behind any specific point, always return to the main text of the relevant public page.

• Start Page
• Verification base
• Public Content Integration Hub

• Wiki: Guide to reading public pages - Click here if you want to know the differences in the roles of pages.
• Wiki: How to read 'What we know/what we don't know' - You can find out more about the meaning of known / unknown.
• Wiki: 3 ways to use this site - We will organize how to use this site as a whole: entry, learning, and participation.

• Public pages begin with a common format for the page's role, intended audience, accuracy assumptions, known/unknown, and wiki navigation.
• By simply reading the opening block before entering the main text, you can decide whether to use the page as an entry point or return to the wiki first.
• Even if the page is long, if you use the guide and floor plan at the beginning, it will be easier to avoid the situation where you have to read the entire page to understand.

• It is not possible to make a final judgment on individual points just by looking at the opening block.
• The contents of wiki links and recommended pages are not fixed because the depth required for each page is different.

---

This wiki is an auxiliary page that provides information on how to read before entering the main text of public pages. As an information portal, the public page first indicates ``what this page does,'' ``how much does it assert,'' and ``where can you learn more about the background?''. You can check the common rules on one page.

Conclusion first

At the beginning of the public page, it will be easier to get lost if you read the following from the top: Role, Target audience, Accuracy assumption, Known/Unknown, and Wiki guideline. That's enough for the main text.

First element	What to see	Points that are easy to misread
How to read this page	Look at what the page does, what it grabs first, and where it goes next.	If you think this is the entire summary of the main text, you will overlook the role description.
Suitable for people/reading guidelines	Determine whether you are currently reading the page.	This is not a guideline for the difficulty level, but for the reading order.
Accuracy Assumption	See what the page does not affirm and what it withholds.	It's not a decorative statement, it's a boundary line of affirmation.
What we know now	Let's see what is relatively clear.	Reading "fully resolved" is an overstatement.
What we don't know yet	Confirm that the issue cannot be resolved on that page alone.	This is not a column that reads "proved to be impossible."
Check the basics on wiki	Check the entrance back to background information.	It is not a bonus, but a formal round-trip route to the learning layer.
Floor diagram on page	Understand the section structure of long pages first.	This is not a substitute for a table of contents, but rather a guide to help you decide where to read first.

Check
1. How to read this page to see if the page is an entry, a blueprint, or a practice.
Check the
2. Suitable people/reading guidelines to see if it is suitable for you.
3. Let's first look at the extent to which we are not asserting the accuracy assumption.
4. What we know now / What we don't know yet Establish boundaries before reading the text.
5. Look at the wiki links and if you don't have enough background knowledge, go back to the learning page first.

This includes page intro, highlights, and recommended pages. In short, it first tells you, ``What is this page supposed to do?'' ``What should I grasp first, even if I don't read everything?'' and ``Where can I go next to gain understanding?''

• page intro: Read as an explanation of the page's role, not the main text.
• Highlights: It is not a collection of conclusions and assertions, but an introduction to key points that can be easily lost in the main text.
• Recommended pages: These are not helpful links, but suggestions for public pages you should read next.

This column is for orienting yourself before reading. In particular, the premise of accuracy is important and makes the difference between whether a page affirms the possibility or whether it is a foundation for confirming whether something is possible.

Common misreadings

The ``premise of accuracy'' is the scope of the page, not a polite note. If you skip this part, it's easier to read Verification as a success declaration page, or read FAQ as a final conclusion page.

Known/Unknown on the public page is a column for determining "what can be said strongly" and "what remains unresolved." Even if there are strong expressions in the main text, it is important not to read them into stronger arguments than in this column.

Heading	Meaning	Reading methods to avoid
What we know now	This is a relatively stable statement based on current methods and evidence.	Read as "Enough is enough, no need for further verification."
What we don't know yet	Includes unresolved issues, non-agreement, lack of evidence, external dependencies, etc.	It is read as "I have come to the conclusion that it is completely impossible."

Instead of turning the main text of the public page into a long textbook, background explanations are moved to the wiki. Therefore, wiki links are not an optional extra, but a formal entry point to use when you stop understanding.

• Stop at a term: Return to glossary or basic wiki.
• Stop at reading: Return to public-page-reading-guide or route-related wikis.
• Stop on strength of evidence: Return to claims-and-evidence and known-unknown systems.

On long pages, a page diagram and For high school students: words that appear on this page appear after the beginning. The diagram is used to understand the positional relationship of the clauses, and the easy-to-understand terminology section is used to create a foothold for the words that will appear in the main text.

Recommended usage

If you have a long page and cannot read it in order from the beginning, open the relevant section first in the diagram, and only return to the terminology section or Glossary if there are many words you do not know. You don't have to read everything equally.

• Read recommended pages as a collection of evidence: This is where you go next, not in order of strength of evidence.
• Read known_points as a declaration of success: Relatively stable facts, not a declaration of resolution of the entire issue.
• Read unknown_points as pessimism: This is an open inventory, not a reason to stop research.
• Postponing wiki links too much: If you read the main text without enough background, it's easy to lose sight of the different roles of public pages.

If you want to sort out the differences between public pages, go to Public page reading guide, if you want to dig deeper into the meaning of known/unknown, go to How to read ``known/unknown'', and to return to the entrance, go to start page Please use.