Case research standard v0.1

Useful patterns, without pretending a forum post is a diagnosis.

The corpus is designed for homeowner decision support—not bulk republication and not AI training on unlicensed content.

The pipeline

Six gates from source to published case

A case cannot skip the provenance, privacy, uncertainty, evidence, or review gates.

Use a documented API, publisher permission, homeowner submission, or link-based research. Record the policy review date.

Retain only what is needed, separate temporary review text, remove handles and contact details, and prevent duplicates.

Extract system, symptom, fixture spread, timing, prior tests, quote scope, and known unknowns without inventing facts.

Rank plausible causes, describe disconfirming checks, assign urgency and confidence, and set a safe DIY boundary.

Prefer codes, government safety guidance, manufacturer documentation, and first-party records; label community consensus separately.

Block cases with unresolved privacy, licensing, attribution, safety, or factual issues. Professional review is stated only when it happened.

Source registry

Status reflects the collection method for this commercial product as reviewed on August 25, 2026.

Questions and ranked answers

ACCESSOfficial Stack Exchange API

Pilot enabled

Store provenance and license; publish only attributed abstractions or compliant excerpts.

r/HomeImprovement, r/DIY, r/Plumbing and future trades

ACCESSReddit Data API only

Awaiting written approval

No automated collection for this commercial lead-generation product until Reddit approves the use case in writing.

Video metadata and embedded instruction

ACCESSYouTube Data API + standard embed

Design ready

Do not download video or captions; keep YouTube attribution and distinguish our analysis from platform data.

Long-form contractor and DIY discussions

ACCESSLink research or written permission

Manual only

Respect robots and publisher terms; do not bulk copy forum text into the case corpus.

Publication guardrails

No names, handles, exact addresses, contact details, faces, license plates, or account identifiers in the public abstraction.
No raw forum post retained in the public database; source URLs and fingerprints preserve provenance and deduplication.
No contractor accusation, legal conclusion, code verdict, or price benchmark from a single anecdote.
No “licensed expert reviewed” badge without an identifiable, completed review event.
Critical safety guidance requires an authoritative source and conservative action boundary.