Breaking down the work that looks like 'waiting for the other person' into preparation work

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

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

This page is an auxiliary page for reading the ``external dependencies'' that come up many times in the operation of Mind-Upload, not as a reason to stop, but as a target for decomposition.The focus here is to distinguish between things that can be created first with this repository and things that require a partner or system.

This page is an aid to help separate the work. This page alone cannot guarantee that an actual agreement, contract, IRB, or equipment use will be established.

• Contribution Guide
• Collaboration candidate
• Verification base

• Wiki: How to read suggestions and state labels - We will first sort out the differences in stages such as proposals, document reflection, and external dependencies.
• Wiki: Basics of verification infrastructure - Explains why requirements specifications and judgment conditions are created first.
• Wiki Home - You can return to other auxiliary pages.

• Even for externally dependent tasks, requirements specifications, judgment conditions, public log formats, comparison tables, etc. can be created in-house first.
• It will be easier to move forward if you organize the minimum deliverables and request details on one page before approaching the other party.
• Whether it's an issue or a joint research project, it's important to clearly state what can be done right now.

• Which external candidates will actually agree and on what terms will depend on factors on the other side.
• IRB, contract, funding, and equipment availability timing will be determined outside of this page.

---

Externally dependent tasks are work that cannot be completed by itself. However, that doesn't mean that you can't do anythingfor us. You can make preparations before making a request, judgment conditions, public log format, comparison table, etc. in advance.

When you want to decide the next page after the participation page

After reading Issues and Collaborations, if you want to see in one page whether you should move on to small modifications, condition design, working from literature, or L0 implementation preparation, please see Five paths to follow after participation/collaboration page.

Type	What you can do now with this repository	Becoming externally dependent
Experiment	You can create requirement specifications, evaluation indicators, stopping conditions, public log formats, and pre-registration drafts.	IRB, subject recruitment, equipment usage, and measurement data acquisition are dependent on external parties.
Joint research	You can create a one-page summary, minimum deliverables, request scope, comparison table, and reanalysis plan.	Co-author agreements, contracts, partner approvals, and data sharing conditions are externally dependent.
Standardization proposal	You can create specification drafts, difference tables, sample logs, and assumed use cases.	Community adoption, official specification reflection, and external review are externally dependent.
Funds/systems	You can organize the purpose, minimum scope, deliverables, and required budget.	Formal decisions on adoption, budget allocation, legal decisions, and system design are externally dependent.

Preparations	Minimum contents	Why is it necessary
One page summary	Purpose, what you want from the other person, and what you already have.	This is so that the other person can quickly determine what you are talking about.
Minimum deliverables	This definition narrows down the minimum scope to one.	If the request is too large, it will be difficult to reach an initial agreement.
Judgment conditions	What should we do to move forward? What should we put on hold? What should we do to fail?	This is to prevent the goal from shifting as the story progresses.
Publishable preparation	Specification draft, QC log example, comparison table, BIDS template, checklist.	This is because it makes it easier to show how serious you are and how specific you are.
External dependency boundaries	Who needs to make decisions regarding IRB, equipment, contracts, legal matters, approval of the other party, etc.?	This is to avoid confusing immediate work with waiting work.

Scene	What I want to fix first	Things that become external dependencies
When creating an issue	Where you stopped, what you lacked, conditions for progress, and conditions for disproving.	If we need experiments or legal matters, we will cut it out as a separate track.
When looking at joint research candidates	The scope of what you want to ask the other party for and the deliverables that you can produce first.	Agreement, co-authorship, data usage conditions, and equipment usage remain.
When submitting a standardization proposal	Difference tables, samples, and points that are lacking in the current standard.	Remains subject to community review and formal adoption.

• "Do nothing now because it depends on external sources": Specifications, comparison tables, log formats, and minimum deliverables can be created first.
• ``It's progressing because it's written in writing'': The preliminary preparations to hand it over to the other party and the actual agreement being reached are two different things.
• "The bigger the plan, the better": If you don't cut the minimum scope at first, neither requests nor issues will work.
• "Treat external dependencies as complete in the main text": This should be especially avoided, and should be written separately from in-house changes that have a trail.

Please return to Contribution Guide to return to how to write an issue, Collaboration Candidates to organize joint research candidates, and return to Verification Platform to solidify requirements specifications and judgment conditions.