claim level reading routes - yasufumi-nakata/mind-upload GitHub Wiki

Wiki: How to read each L0 to L5

A guide to deciding which public page to go to depending on the strength of your argument

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

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

Role Of This Page

This page is an auxiliary page that organizes Mind-Upload's complaint ladder L0 to L5, not just by definition, but by ``which page should I go to when I want to follow the level of the story?'' As the strength of the claim increases, the pages and evidence required will change as well.

Accuracy Notes

This page is a reading order aid. Please be sure to check the actual conditions for each level in the main text of the original page.

Back To Public Pages

Related Wiki Pages

What Is Currently Known

  • L0 to L2 are relatively easy to advance in terms of engineering, and after L3, additional conditions suddenly increase.
  • L4 and L5 go beyond output matching and accuracy alone.
  • There are different pages to look at depending on the level of assertion.

What Is Still Unknown

  • It is still undetermined which conditions must be met for L4 and L5 to finally hold.
  • The reading order may change slightly due to future data, benches, and system development.

First, divide it into stages

L0 to L5 are not the "quality of research" but the strength of the argument. Therefore, if the strength of the argument you want to read changes, the page you should look at first will also change.

Entrance for each L0 to L5

Level What I want to know now First page to open Next page to supplement
L0 Reproducible analysis I would like to know if other people can re-run the same result. Hands-on Datasets / Verification
L1 Decoding I want to read the story correctly that something could be predicted from brain signals. WBE 101 FAQ / EEG 101
L2 Generation/intervention prediction I want to see responses to unlearned conditions and condition changes. Verification Roadmap / Perspective
L3 Closed loop I want to see whether it moves stably in real time or until it stops safely. Verification EEG 101 / Roadmap
L4 Identity I would like to know how to read the continuity of memory, values, and learning. WBE 101 Idea / Perspective
L5 Social implementation I would like to see it including rights, safety, stopping standards, and systems. Roadmap Collaborations / Issue

Why this order?

Level Reason for entering from this page
L0 Since L0 is more about deliverables and procedures than concepts, it is faster to enter from Hands-on.
L1 Since L1 is easily misread in news, it is safer to align the assertion level with WBE 101 first.
L2 Since L2 includes interventions and counterfactuals, it is better to start with Verification, which is the center of evaluation design.
L3 L3 is a separate issue from offline accuracy, so both Verification and Roadmap are required.
L4 L4 is an assertion of identity, so after confirming its strength with WBE 101, dig deeper with Idea and Perspective.
L5 L5 has a large system and external dependence, so it is necessary to read Roadmap and Collaborations at the same time.

Common misreadings

Misread

  • A quick look at L0: It is actually the most important first, as it is the basis of comparability.
  • Extend L1 success directly to L4: This is the most typical transfer.
  • L3 is all about accuracy: No delay, no jitter, no safe stops to claim closed loop.
  • Determine L5 only by technology: There are separate layers of systems, rights, and responsibilities.

Wiki that can be viewed together at each level

Level Auxiliary wiki
L0 The minimum artifact pack for L0 / Data splitting and data leaks
L1 Decode and Emulate / How to read claims and evidence
L2 Counterfactual/intervention/perturbation verification
L3 Closed-loop/delay/jitter/safety stops
L4 Personhood assessment and continuity tests / Personhood and copy problems
L5 Separating in-house production and external dependencies / Update/branching/stop rules

Where to return next

To return to the definition of L0 to L5, please use Introduction to WBE, to return to designing victory conditions, use Verification base, and to return to the dependency map, use Technology roadmap.

⚠️ **GitHub.com Fallback** ⚠️