First, fix your mindset
Progress labels are not words that judge a research theme as ``pass/fail.'' Its role is to briefly showwhat you already have and what is still missing.
Meanings of frequently used labels
| Label | In everyday language | At least what you can say | Things I can't say yet |
|---|---|---|---|
| Partial solution | While progress has been made in some core areas, all conditions are not yet in place. | At least some of the methods, measurements, and comparison axes are working. | It cannot be said that the final victory condition has been reached. |
| Exploration stage | This is an important question, but evaluation methods and public benches are still weak. | It is worth addressing as an issue, and there are initial evidence and hypotheses. | It cannot be said that stable comparison, reproduction, and standardization have been achieved. |
| Unstandardized | Measurement methods and formats vary depending on the person and team. | Although individual studies exist, the common yardstick is still weak. | It is not possible to make fair comparisons between different studies. |
| Undeveloped | Operational rules, audit procedures, division of responsibility, disclosure format, etc. have not yet been finalized. | Practical conditions other than technology remain. | We cannot say that it will cover long-term operation or third-party audits. |
| Lack | We still lack the necessary data, benches, error bounds, comparison tests, etc. | I can see what needs to be added. | It cannot be said that the current materials are sufficient. |
| Undefined | How to determine thresholds, boundaries, and sufficient conditions has not yet been determined. | The problem setting is visible, but the line drawing is not fixed. | It cannot be said that everyone will get the same judgment. |
| Insufficient | Although there is a minimum, it is still not enough for third-party comparisons or strong claims. | There is some foundation. | It cannot be said that the strict verification conditions have been met. |
There are different types of "not enough"
| Expression | What's missing | Example | What you need next |
|---|---|---|---|
| Not enough benches | There is no place to compare the same issues and the same indicators. | ``Lack of unified bench'' | Public data, fixed indicators, baseline, and failure examples. |
| Standards not yet developed | Format, logging, naming, and auditing procedures are not consistent. | “Common audit regulations are insufficient” | Standards, Validators, Templates, and Checklists. |
| Insufficient error bounds | We do not know how far it can be generalized and the uncertainty. | "Insufficient generalized error bound" | Confidence interval, subject difference evaluation, OOD evaluation. |
| Threshold not determined | It has not been decided where to start calling things ``same'', ``sufficient'', and ``safe''. | "Threshold value not determined" | This is a comparison test with pre-registered judgment rules. |
| Undeveloped public operation | There is no way to go beyond third-party supplementary examinations, responsibility sharing, and suspension criteria. | “Operating regulations not yet in place” | Registry, audit log, suspension rules, and publishing procedures. |
Read with examples
| Example | What you want to read in this way | Questions that remain |
|---|---|---|
| U0: Partial resolution/identity evaluation bench unstandardized | There are attempts to measure identity, and there are also partial evaluation axes. | A common bench and thresholds that include interventions are not yet available. |
| U10: Exploration stage / limited actual measurement research | Thermodynamic grounding exists as an issue and there are candidate indicators. | The comparison between the actual measured pipeline and the published pipeline is still weak, and its generalization is still uncertain. |
| U15: Exploration stage / lack of implementation standards | The need for system integration is clear, and the problem set is clear. | There is still no specific standard that connects technical KPIs and stopping criteria. |
It is not a simple matter that "partial solution" is always better than "exploration stage". Partial solution indicates that there is some foundation, and the exploration stage indicates that the comparative basis for the whole question is still weak. You need to read up to the types of what is missing.
Common misreadings
Misread
- "It's only a partial solution, so it's almost finished": Depending on the remaining conditions, rather heavy work remains behind.
- "It's only in the exploratory stage so it's meaningless": There are things that are important, but the basis for comparison is still weak.
- “It says “deficiency, so don’t do everything”: If you don’t read what’s missing separately, you’ll miss the progress.
- “There is no research because it is not standardized”: Even if there is research, there may be no common format or common bench.
- “Underdeveloped means only a lack of technology”: It is often a lack of systems, audits, and open operations.
Where to return next
If you want to read the current status of each U, please go back to Literature Map. If you want to see the progress with dependencies, go back to Technology Roadmap. If you want to distinguish between designed and unimplemented projects, go back to Verification Platform.