research

Inspect the installed implementation and version in the repository first, then confirm behavior against version-specific primary sources such as official docs, release notes, or source code. Pin claims to immutable commit or tag links when practical.

Compare alternatives on the dimensions that matter to the task: correctness, fit, complexity, cost, latency, security, maintenance, and migration risk. Use primary sources for each option and recommend the smallest reliable choice rather than presenting an unranked list.

No. The evidence rules prohibit citing search snippets when the underlying primary source is available, and a README example is not proof a feature is production-safe. Memory alone is also insufficient for version-sensitive API claims.

Record the disagreement explicitly and prefer current installed or runtime evidence for actual MDE behavior. Note the conflict in the report's risks or unknowns section so reviewers can judge the discrepancy.

Save reusable platform or vendor research under docs/platform/tech-stack/<technology>/ and domain-specific research under the owning docs folder. One-off findings belong in the Linear task or PR evidence instead of the documentation tree.