source-driven-development

To verify an API signature against official documentation, you look up the official docs, cite the source, and explicitly mark any unverified claims. This prevents relying on outdated memory for API signatures.

The best way to check if a library API behavior changed in a new version is to perform version-aware verification against official documentation. This confirms exact behavior at the target version rather than relying on assumptions.

You need to look up official docs for framework integration when using version-sensitive libraries, encountering uncertain API signatures, or debugging behavior that may differ from model memory. This grounds decisions in current documentation.

When researching framework APIs, you document unverified claims by explicitly marking them during your official-doc lookup. This source-driven approach requires citing official documentation to separate verified behavior from assumptions.

Yes, you can use this approach to debug version-specific issues with version-sensitive libraries. It applies to implementation work by requiring official documentation lookup and source citation to confirm exact behavior at the version in use.