What I would like to distinguish first
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.
Make state labels everyday words
| 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. |
What labels don't mean
Not Mean
- 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.
Where should I go back
| 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.