'Recruited' and 'finished' are two different things

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

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

This page is an auxiliary page to help you avoid misreading the status labels that appear on Mind-Upload's proposal and issue pages. There is a difference between a proposal being accepted and implementation and external agreement completed, so we will explain the difference in everyday language.

The explanations here are a reading aid. Be sure to return to the proposal page and issue history for the latest status of individual proposals.

• Technical proposal
• Contribution Guide
• Verification base

• Wiki: How to read the literature and evidence page - Compensate for how proposal pages differ from literature pages.
• Wiki: What to do first in-house and external dependencies - This book is for people who want to break down external dependencies into the preparation work that can be done now.
• Wiki: Basics of verification infrastructure - You can see why achievement conditions and disconfirmation conditions are placed first.
• Wiki Home - You can return to other basic pages.

• Acceptance of the proposal or reflection of the document does not automatically mean completion of the code or collaborative research.
• For externally dependent tasks, you need to read the preparation on your side and the agreement on the other side separately.
• Status labels indicate the location of implementation and publication, not scientific certainty per se.

• The extent to which each proposal is ultimately implemented may change as we proceed.
• The completion timing and conditions of externally dependent tasks cannot be guaranteed by labels alone.

---

On the proposal page, the different stages are ``accepted as a good idea,'' ``written in the main text,'' ``worked into code,'' and ``completed with external agreement.'' Blurring this distinction confuses work that is progressing with work that is still pending.

Label type	In everyday language	What remains
Publish proposal	It has been put forward as a proposal and is open for discussion.	Verification of validity and priority remains.
Proposal acceptance/policy reflection	As a direction, we have judged that it is worth taking.	The implementation method, verification conditions, and publication materials remain.
Document reflection	The condition is as written in the main text.	Code, data, and logs may not be complete.
Implemented	It is a state where there is something that actually moves.	Separate third-party supplementary examinations or audits may be required.
External dependencies	We cannot complete the process alone; we need a partner and a system.	Agreements, contracts, experiments, funding, etc. remain.

• Proposal acceptance: This does not mean that the proposal is completely scientifically correct.
• Document reflection: This does not mean that implementation and joint research are finished.
• Implemented: This does not mean that social implementation and system development have been completed.

What I want to know	Back page
Contents and basis of proposal	Technical proposal
Who can help what now?	Contribution guide
Assumptions of achievement conditions and disproval conditions	Verification infrastructure

To avoid making external dependencies a "waiting box"

This page explains the stage differences. If you want to organize what you can create first after becoming an external dependency, please see Wiki: What to do first in-house and separating external dependencies.