Fit belongs to a pair
PlinkBench does not describe a part as universally compatible. A fit answer connects one exact product record to one exact rifle or receiver record. Change either side of that pair and the answer must be checked again.
This matters in product families with many models and revisions. A maker may use one family name across products while still documenting exclusions, model boundaries, or different interfaces. PlinkBench keeps those boundaries instead of smoothing them into a family-wide promise.
What must be on file
The strongest path starts with an explicit first-party statement that names the exact pairing. A bounded maker family statement can also qualify only when the selected rifle or receiver is joined to that statement by a reviewed, deterministic scope record.
Names, measurements, retailer copy, community reports, and the fact that two products look related are not enough by themselves. Those details can help identify what needs research, but they cannot earn Fits.
- The part and rifle or receiver identities are exact.
- The retained maker statement covers the pairing at the scope shown.
- Conditions and exclusions are still represented.
- A separate review confirms that the evidence supports the public answer.
Why independent review matters
The session that first reads a source cannot also be the final authority for a Fits answer. A second review checks the claim, retained source, identity, scope, and policy result. If those records disagree or have gone stale, the pairing stays Not verified.
The review does not make the manufacturer's statement broader. Its job is to confirm that the narrow public answer matches the evidence already on file.
What Fits does not mean
Fits does not mean that every relationship in a complete build has been evaluated. It does not replace manufacturer instructions, establish legal suitability, promise current inventory, or guarantee performance beyond the retained maker statement.
A single part can show Fits while the larger build remains In research. Read the pairing answer and the whole-build status as two different decisions.