Wiki

Wiki: U Number Guide

U is a name tag for unresolved problems.

Mind Uploading Research Project

Public Page Updated: 2026-03-19 Reading guide

How to use this page

Read this first to avoid getting lost

This page helps translate the U numbers that appear in the literature map into everyday language. The goal is not to memorize the numbers, but to make it easier to find which block a reader should start with.

  • A U number is a name tag for an unresolved problem, not a level.
  • Similar U labels are grouped into larger problem clusters to make entry points easier to find.
  • The recommended use is not memorizing the numbers, but finding the cluster that matches your interests.
  • For technology and natural-science readers, the default route is U1/U7 -> U4 -> U13 -> U8 -> U3 -> U10.
Best for
People who feel intimidated by labels like U0-U15, and people who want to find the entrance to the literature map.
Reading time
8-12 minutes
Accuracy note
The explanations here are entry-point paraphrases. For exact definitions and the latest status, always return to the main literature map.

Relatively clear at this stage

What we know now

  • U is an internal code used to organize unresolved problems in the literature map.
  • Looking at larger problem groups makes it much easier to see where to start reading.
  • Citation count or the size of the number does not directly express claim strength or importance.
  • For technology and natural-science readers, it is better not to treat U0/U12/U15 as the default entry point.

Still unresolved beyond this point

What we still do not know

  • The content and boundaries of each U may change as the literature map evolves.
  • It has not yet been fixed which U should receive the greatest concentration of research resources.
  • Whether U11's consciousness-metric comparison returns to the main route may change with future prediction competitions and benchmark development.

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.

What you don't need to remember first

The U number is not a memorized item for the exam. The role is a name tag that helps you identify which unresolved problems this document is related to. First of all, it is more important to look at which block is the problem than the number itself.

Looking at big problems

Big problems Main U In everyday language
Definition and evaluation U0 / U11 / U13 / U14 The problem is what to call "same", "successful", and "able to try again".
Measurement and estimation U1 / U7 The question is how much of the brain and behavior can be measured and how much can be estimated.
Causality and implementation stability U4 / U8 / U10 It is a matter of model-conditioned causal claims, reaction to changes in conditions, stability of the closed loop, and physical cost.
Boundaries and identity U3 / U12 The problem is how much to include in the subject and how to handle the identity after branching.
System and public operation U15 This is an operational issue, including suspension standards, disclosure standards, and how to place responsibility.

Entrance by interest

What I'm curious about now First look at U group
EEG, inverse problems, and limits of time synchronization U1 / U7
How to read effective-connectivity / DCM claims without overpromoting them U4
Difference between decode success and WBE claim U13
Long-term closed-loop stability U8
Maintenance-state and support system outside the connectome U3
I want to include physical costs and dissipation U10

Order of viewing first by technology/natural science

Order U Groups Reasons for viewing in this order
1 U1 / U7 First, if we do not fix what is directly observed and what can still be estimated, all subsequent assertion levels will be unstable.
2 U4 This is to avoid misreading a directed graph or DCM fit as discovered causal wiring before candidate model space and observation assumptions are checked.
3 U13 This is to avoid misinterpreting successful decoding or imitation as causal conservation or emulation.
4 U8 The success of within-session does not necessarily mean stable long-term operation.
5 U3 If you do not read sleep/homeostasis, myelin/metabolic support, astrocyte ensemble, and clearance/immune support separately, you will read structural progress too much into long-term subject equivalence.
6 U10 Finally, we bring back dissipation and effective cost as refutation conditions, so that we don't end the discussion with computability alone.
Why U4 now comes before U13

On the public pages, effective-connectivity / DCM claims are already read as model-conditioned causal hypotheses. This guide now mirrors that rule. The reason is practical: if a reader first sees a directed graph and reads it as discovered causal wiring, the later distinction between decode success and WBE-level causal preservation becomes harder to recover. So in the literature route, U4 is now checked before U13.

Group removed from lead line

Although U0 / U12 / U15 are important, they should not be placed at the default entry point for technology and natural sciences. What is needed here is to fix what can be measured, to what extent it can be directly validated, where the closed loop breaks, and what hidden state remains, rather than focusing on identity or institutional theory.

To avoid misreading the U number

Checklist

  • Don't memorize numbers: Start with the problem group.
  • Don't judge by the number of citations: There is a difference between having a lot and being solved.
  • Return to strict definition: When you actually use it, return to the definition table in the main text of the bibliographic map.

Where to return next

Once you understand the meaning of the numbers, please return to Bibliography Map. If the role of the literature page as a whole is still unclear, it will be easier to read if you first look at How to read the literature and evidence page.