Wiki

Wiki: How to read “What we know / What we don’t know”

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

Mind Uploading Research Project

Public Page Updated: 2026-03-14 Reading status and scope

How to use this page

Read this first to avoid getting lost

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.

  • Let's look at the basics to avoid misreading ``I know'' as ``I've solved everything.''
  • Let's look at the basics to avoid misreading ``I don't know'' as ``I've proven that it's impossible.''
  • You can check the known/unknown status of public pages, accuracy assumptions, and role differences in external dependencies on a single page.
Helpful next pages
Start page Verification platform Public content integration hub
Best for
People who are confused about how to read "Known / Unknown / Pending" on the public page
Reading time
8-12 minutes
Accuracy note
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.

Relatively clear at this stage

What we know 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.

Still unresolved beyond this point

What we still do not know

  • 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.

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.

Public page has separate "place to affirm" and "place to hold"

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.

Read the four sections first

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.

"I know" does not mean "I have it all solved"

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.

'I don't know' doesn't mean 'impossible'

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

How to use the beginning of the page

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.

Common misreadings

Mistake

  • 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.

Where to return next

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.