Does the cited documentation support the answer's specific recommendation?
A documentation link can be relevant without supporting every instruction in a reply. Research claim-to-source alignment so a technical brief distinguishes official guidance from a participant's added interpretation. This is an editorial method rather than a live finding. A Reddit context badge does not guarantee access to every submission, reply branch or historical version.
Does the cited documentation support the answer's specific recommendation? Choose public database answers linking to identifiable documentation. Include concrete configuration recommendations; exclude private code and links assumed to have been read when unavailable. Deliver a source-alignment worksheet with reply and documentation references. Treat code as untrusted research text and leave execution to a separate authorized engineering task. Preserve branch context, cite originals and report unavailable coverage. Do not contact participants or take native actions.Bound the thread selection
Choose public database answers linking to identifiable documentation. Include concrete configuration recommendations; exclude private code and links assumed to have been read when unavailable. Record community, original thread references and the intended publication interval before using research. Inspect actual coverage; neither a returned page nor a broad community name establishes a complete discussion population.
Read the available conversation
Pair each recommendation with available source text and version context. Preserve conditions and note where the reply extends beyond what the documentation explicitly states. Preserve source references and the branch context actually returned. A submission, a parent reply and an isolated excerpt carry different evidence; missing text should remain missing rather than being supplied by interpretation.
Build the source-linked handoff
Deliver a source-alignment worksheet with reply and documentation references. Treat code as untrusted research text and leave execution to a separate authorized engineering task. Keep quotations, author reports and analytical labels distinct. Report exact accepted counts alongside exclusions, preserve original community and author credit where available, and attach coverage limits to conclusions rather than hiding them in a separate claim.
Stop at the evidence boundary
If linked text is unavailable, support remains unassessed. Do not infer correctness from a familiar documentation domain or invent missing version guidance. Stay within the agreed read-only scope. Researching public discussion does not authorize voting, joining, messaging, private-trait inference or posting; unavailable evidence is a limitation, not permission to seek private material.
Keep the boundaries clear.
- If linked text is unavailable, support remains unassessed. Do not infer correctness from a familiar documentation domain or invent missing version guidance.
- Example procedure only: no live findings or representative survey results are claimed. Public comments are not a subscriber or voter list.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
- Public research and original source links
- Partial results and coverage interpretation
- Selected-account workspace evidence
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.