u number guide - yasufumi-nakata/mind-upload GitHub Wiki
U is a name tag for unresolved problems.
This learning page is generated for GitHub Wiki. The public portal is managed on mind-upload.com.
- Updated: 2026-03-19 / Role: Reading guide
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.
The explanations here are entry-point paraphrases. For exact definitions and the latest status, always return to the main literature map.
- Wiki: How to read the literature and evidence page - For readers who want to understand the role of the literature map itself first.
- Wiki: Basics of WBE - For readers who want to see the big picture behind the U numbers first.
- Wiki Home - A route back to the other foundational pages.
- 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.
- 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.
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.
| 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. |
| 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 | 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.
- 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.
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.