Aligning the boundaries between assertion and reservation to read as an information portal

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

• Updated: 2026-03-14 / Role: Reading status and scope

This page is an auxiliary guide to help you avoid misreading the What we know now'', What we don't know yet'', and ``What we can/can't say on this page'' on the Mind-Upload public page. As an information portal, the public page first indicates what can be asserted and what should be reserved. It is used to read the meanings.

This article deals with how to read public pages. To check the authenticity of individual theories and techniques, be sure to return to the original page text and evidence.

• Start page
• Verification platform
• Public content integration hub

• Wiki: Guide to reading public pages - This is for people who want to decide in advance which public page to read from.
• Wiki: How to read partial solution/exploration stage/undeveloped - This is for people who want to see the meaning of progress labels in more detail.
• Wiki: What to do first in-house and external dependencies - This is for people who want to take a closer look at separating external dependencies from changes that can be made now.

• The public page is designed as an information portal that indicates the strength of your assertions and the extent of your reservations.
• ``What we know now'' refers to what can be said relatively strongly within the scope of that page.
• By separating things we don't know yet'' and external dependencies,'' we can reduce excessive expectations and misinterpretations.

• The extent to which issues can be moved to ``known'' in the future will depend on the progress of research and development.
• Strong claims like L4 and L5 continue to have many unresolved issues.

---

The public pages of this site are not the place to make any assertions. Rather, I separate what I can say relatively strongly now, what I can't say yet, and what is not the role of this page, so that readers don't mistakenly jump to strong conclusions.

Display	How to read	Easy to misread
What we know now	This can be said relatively strongly within the scope of that page.	It is a stretch to read that the entire field has been finalized.
What we don't know yet	These are the parts that remain unresolved, lack of conditions, lack of evidence, lack of agreement, etc.	Reading it as "proved impossible" is another story.
Accuracy Assumption	Indicates what this page does not assert and the scope of its defense.	It should be read as a demarcation line, not a cautionary tale.
External dependencies	These are tasks or conditions that cannot be completed using this repository alone.	It is incorrect to read that ``I can't do anything right now.'' You can make the preparations first.

How to say public page	Actual meaning
Requires standards, shared infrastructure, evaluation, and auditing	It means that the arrangement of requirements is relatively stable. This does not mean the implementation is complete.
Conditional advancement can be created with EEG	It means that comparable progress can be made within a limited range. The whole WBE thing is not a proven story.
Do not assert your identity or consciousness on the entrance page	It means that it is not an entrance role. That doesn't mean it's unnecessary.

Unknown type	What kind of shortage is it?	Where to look next
Insufficient evidence	Necessary data, comparison, and disproval conditions are missing.	Verification
Conditions undetermined	It is unclear what needs to be met to move forward, and what needs to be met to be put on hold.	Roadmap / Verification
Lack of consensus	There is still no cross-disciplinary agreement on issues such as identity and system design.	WBE 101 / Collaborations
External dependencies	External conditions such as IRB, equipment, contract, collaborative research partners, etc. are required.	In-house production and external dependencies

First element	What is it used for
page intro	Check the role of the page. First, decide whether it will be a theoretical text, practical work, or an operational hub.
accuracy note	Check the extent to which the page intentionally makes no claims.
known / unknown	Separate what is a relatively stable foundation and what remains unresolved.
wiki links	We supplement the assumptions that tend to stop there with study pages.
recommended pages	Determine the public page to return to after that page.

• Reading “I know” as a completion report: Most of the time it is an arrangement of necessary conditions or relatively stable assumptions.
• Reading "I don't know" as negative proof: Unresolved or insufficient evidence is different from proof of impossibility.
• Read accuracy note as decoration: It is actually important information that determines the boundaries of the assertion.
• Leave external dependencies as a hold box: First, you need to cut out the preparations that can be made in-house.

If you want to go back to the role differences of public pages, go back to Guide to how to read public pages. If you go back to the detailed meaning of progress labels, go back to How to read partial solutions, exploration stages, and undeveloped. If you go back to separating external dependencies, go back to Internal prework and external dependencies.