researchlisted

# Technical Research Produce the smallest body of evidence needed to answer the question or support a decision. Prefer verified primary sources over familiarity, popularity, or plausible recollection. ## Respect the Research Contract - Work read-only unless the user explicitly asks for implementation or a saved research artifact. - When research is a dependency of another workflow, return the findings to that workflow instead of creating an unnecessary document. - Do not broaden a focused question into a general survey. - Do not present an inference, recommendation, or absence of evidence as a sourced fact. ## Frame the Decision Define: - the exact question to answer; - the decision or implementation it informs; - the relevant product, language, package, platform, jurisdiction, or standard; - the versions, dates, environments, and constraints that affect applicability; - what evidence would be sufficient to stop. Inspect the local repository first when it can establish installed versions, active configuration, existing contracts, or current behavior. ## Use the Correct Source Route Prefer sources in this order: 1. official specifications, product documentation, API references, standards, and source repositories; 2. official release notes, migration guides, security advisories, issue trackers, and maintainer statements; 3. original research papers and first-party technical reports; 4. reputable secondary analysis for discovery, context, or independent corroboration;