| Status | Meaning |
|---|
OK | Matching completed and returned a normal result payload. Interpret candidates using product-specific classes. |
AMBIGUOUS_MATCHES | Input points to multiple possible references or candidates. User confirmation or more specificity is required. |
INPUT_RECHECK_REQUIRED | Input conflicts, is too weak, or is unsafe to treat as confirmed. |
NO_REFERENCE | No reference product could be resolved. |
ERROR | Unexpected runtime failure. |
| Status | Meaning |
|---|
RESOLVED_AUTOMATIC | One usable reference was resolved automatically. |
AMBIGUOUS_MATCHES | Multiple plausible references exist. |
INPUT_RECHECK_REQUIRED | Anchors conflict or sparse context is unsafe. |
NOT_FOUND | Resolver found no matching reference. |
NOT_SUPPORTED | Product, variant, or request shape is outside support. |
| Product | Classes |
|---|
| UCP pillow block bearings | GREEN, YELLOW, RED |
| Deep groove ball bearings | DROP_IN, CONDITIONAL, REJECT |
| Roller chains | DROP_IN_FIT, FIT_OR_BETTER, PENDING_VERIFICATION |
| V-belts | DROP_IN_FIT, CORE_FIT_CONDITIONAL, CLOSE_MATCH_STRICT, CLOSE_MATCH_CONDITIONAL, CLOSE_MATCH_CROSS_FAMILY, UPGRADE_SUGGESTION, REJECTED |
| Ball valves | DROP_IN, FIT_OR_BETTER, PROBABLE_DROP_IN, REQUIRES_MODIFICATION, POSSIBLE_MODIFICATION_PATH, ENGINEERING_CONFIRMATION_REQUIRED, PROBABLE_TECHNICAL_MATCH, REJECT |
Tags and reason codes are product-specific. Do not define them only in this shared glossary; keep the authoritative explanation in the affected product page:
- UCP pillow block bearing result bands and risk flags:
products/ucp_bearings/result interpretation
- Deep groove ball bearing reason codes and gate flags:
products/dgbb/result interpretation
- Roller chain gate tags and pending reasons:
products/roller_chains/result interpretation
- V-belt policy tags and warning codes:
products/v_belts/result interpretation
- Ball valve evidence, blocker, and procurement tags:
products/ball_valves/result interpretation
Ball valve rows can be technically interesting without being actionable. procurement_release_allowed must be true and procurement_blockers must be empty before a result is documented or displayed as procurement-ready. Discovery and recheck rows are for clarification only.