V-Belt Engineer Guide

Use this section when reading V-belt results. V-belt output separates direct identity, conditional fit, close suggestions, upgrades, and rejections.

How To Read A V-Belt Result

1. Confirm the reference belt code and length were resolved correctly.
2. Read the class before reading score or rank.
3. Check whether the path is strict identity, same-section compatibility, cross-family bridge, close length match, or upgrade suggestion.
4. Review tags for antistatic, aramid, drive load, length consistency, cross-family policy, and belt code group.
5. Check technical snapshot fields for section/profile, top width, height, pitch/effective/outside length, construction, cogged/wrapped state, antistatic capability, aramid requirement, and drive requirements.
6. Decide whether the result is direct fit, review candidate, advisory suggestion, or blocked.

Do

• Do treat DROP_IN_FIT as the only direct fit class.
• Do treat CORE_FIT_CONDITIONAL as review-required.
• Do treat all close-match classes as suggestions, not direct replacements.
• Do treat UPGRADE_SUGGESTION as optional/advisory.
• Do check aramid and antistatic requirements.
• Do check length type and canonical length consistency.
• Do explain cross-family bridges as declared policy paths, not universal compatibility.

Don’t

• Do not treat wrapped and cogged variants as automatically equivalent.
• Do not treat close length as drop-in.
• Do not ignore drive requirements in safe mode.
• Do not recommend quarantined 8VX output as normal fit.
• Do not use cross-family candidates without a declared bridge.
• Do not hide inconsistent canonical length evidence.
• Do not treat an upgrade suggestion as a required replacement.

Status Next Actions

Status	Engineer action
OK	Read class, path, tags, drive requirements, and length evidence.
AMBIGUOUS_MATCHES	Ask for full belt code, length type, profile, construction, or manufacturer data.
INPUT_RECHECK_REQUIRED	Resolve conflicting belt code, length, profile, or drive requirement.
NO_REFERENCE	Request full belt designation, length, section/profile, and construction.
ERROR	Do not interpret; retry or escalate.

Tag Next Actions

Tag	What to do next
NON_STANDARD_8VX_QUARANTINED	Treat as special handling; do not use normal fit classes.
CANONICAL_LENGTH_INCONSISTENT	Resolve length evidence before deciding.
ANTISTATIC_CAPABILITY_UNVERIFIED	Confirm antistatic capability if required.
REQUIRES_ANTISTATIC_NOT_MET	Reject for antistatic-required drives.
ARAMID_COMPATIBILITY_REQUIRED	Confirm aramid compatibility or reject.
DRIVE_LOAD_TIER_UNDERSPEC	Reject or select a belt meeting the load tier.
DRIVE_REQUIRES_ARAMID	Use only aramid-compatible candidates.
DRIVE_REQUIREMENT_BLOCK	Treat as blocked until drive requirement is satisfied.
SECTION_COMPATIBILITY_DECLARED	Review declared compatibility details.
WRAPPED_COGGED_SUBSTITUTION	Treat as conditional; confirm pulley and performance impact.
CROSS_FAMILY_BRIDGE_DECLARED	Review bridge policy before using.
CLOSE_MATCH_LP_TOLERANCE	Treat as close suggestion, not direct fit.
CLOSE_MATCH_SECTION_GROUP	Review section group compatibility.
CLOSE_MATCH_CROSS_FAMILY	Treat as advisory only.
COGGED_UPGRADE_SUGGESTION	Present as optional upgrade, not direct equivalent.
CROSS_FAMILY_BLOCKED	Do not use cross-family candidate.
BELT_CODE_GROUP_MISMATCH	Reject or verify input was misread.
NO_POLICY_PATH	Do not recommend; no safe documented route.

Example Workflow

When a result is CLOSE_MATCH_CONDITIONAL with WRAPPED_COGGED_SUBSTITUTION:

1. State that this is not a direct drop-in.
2. Compare belt construction and length evidence.
3. Confirm pulley compatibility and drive requirements.
4. Use only after engineering sign-off.

Never Claim

• Never claim a close match is a drop-in replacement.
• Never claim cross-family compatibility without a declared bridge.
• Never claim antistatic or aramid suitability without evidence.