rtfm

To verify API claims, read the actual primary sources like code, documentation, and specifications to confirm feature support and behavior. Then check secondary sources for context before performing a minimal test to confirm the claim.

The best way to check API documentation accuracy is to read the primary sources directly, cross-reference with secondary and tertiary sources for community context, and perform a minimal test before confirming the feature support or behavior.

Yes, you can use a structured verification workflow to check parameter behavior and compatibility. It enforces reading primary sources, checking secondary sources for context, and testing minimally before confirming any system or tool claims.

Reading secondary and tertiary sources when verifying API support provides essential community context, real-world examples, and practical experience that primary documentation may omit, ensuring a rigorous verification process before coding.

You need source verification for product decisions and shipping changes when confirming feature support, parameter behavior, or compatibility. It prevents incorrect implementations by enforcing a rigorous check against primary sources before confirming claims.