Processing and review state dictionary
A non-answer is a valid product state. Status must distinguish incomplete processing, insufficient evidence, reviewer action, and completed work with warnings.
Reference version 1.1 · Updated September 4, 2026
Canonical states
| State | Meaning | Required action |
|---|---|---|
| Queued | Accepted and waiting for the selected processing path. | No review action yet. |
| Processing | One or more owned attempts are active. | Monitor progress and warnings. |
| Partial ingestion | Some source artifacts are available and one or more pages require fallback or retry. | Inspect coverage before relying on results. |
| Evidence connected | A finding has an addressable supporting source. | Review the cited context. |
| Needs review | The system prepared a result that requires accountable judgment. | Assign and resolve with a qualified reviewer. |
| UNKNOWN / needs input | The source cannot support the requested answer or a required input is missing. | Supply approved input, request clarification, or leave unresolved. |
| Conflict | Material sources or methods disagree. | Review both records and document the resolution. |
| Completed with warnings | The workflow completed but retained one or more limitations. | Read warnings before approval or handoff. |
| Valid no opportunities | The completed workflow found no qualifying opportunity under the selected context. | Confirm context and close or revise the review. |
| Approved for handoff | A named person approved the configured next action. | Execute only the allowed handoff. |
Scores are not states
Screening rank, technical fit, pursuit readiness, evidence confidence, pursuit confidence, product-match confidence, and quantity confidence answer different questions. None replaces the processing or review state.
Detail: nine review states and what to do
A non-answer is a valid product state. A processing state, a confidence signal, a verified calculation, and an approval describe different things. None silently substitutes for the other.
| State | Meaning | Reviewer guidance |
|---|---|---|
| Queued / processing | The document or analysis has been admitted and work is not complete. | Use Project Hub or live workflow progress as the lifecycle record. |
| Screened | The lightweight lane produced a score, reasons, signals, and cited pages. | Inspect the basis and promote only when deeper analysis is justified. |
| Evidence connected | The finding has an addressable source path. | Open the source and inspect the surrounding context. |
| Verified | The configured verification requirements for that record were satisfied. | Confirm the remaining human approval required by the accuracy profile. |
| Estimated / ballpark | A bounded method produced a preliminary value with lower rigor. | Use for qualification unless a higher-accuracy path is completed. |
| Needs review | A conflict, assumption, weak support, or decision remains unresolved. | Assign the correct technical, estimating, or commercial reviewer. |
| UNKNOWN / needs input | The approved record cannot support the requested value. | Supply valid source information or preserve the non-answer. |
| Partial ingestion / warning | Core work completed with missing or stubbed page coverage. | Inspect the coverage record before relying on affected findings. |
| Failed | The document or analysis could not complete its required path. | Read the failure state, correct the cause, and retry or rescreen. |
Need help applying this page to an evaluation?Ask a product question