Research Rebel / Community Evidence
COMMUNITY EVIDENCE

Document observations without upgrading them to proof.

Community-reported patterns belong in context beside—not inside—controlled evidence.

COMMUNITY ≠ CLINICAL

These entries describe reported practices and experiences. They do not establish an appropriate human dose, safety, efficacy, compatibility, or stability.

FILTER 01

Compound

Find community entries attached to a specific compound dossier.

FILTER 02

Route

Keep intranasal, subcutaneous, topical, oral and other reported routes distinct.

FILTER 03

Research goal

Organize reports by the goal the contributor says they were investigating.

Every community entry records:

Reported amount / rangeRouteFrequencyDuration / cycleTimingReported goalReported benefitsReported adverse effectsConcurrent compoundsSource / communityNumber of reportsDate collected

This structure lets Research Rebel document real-world community patterns without quietly upgrading them into scientific evidence.

COMMUNITY EVIDENCE STANDARD

A protocol entry needs context, not just numbers.

A

Provenance

Source, date and number of independent reports.

B

Confounders

Concurrent compounds, route, timing, baseline condition and major changes.

C

Signal vs proof

Repeated community patterns can justify a research question; they do not establish causality or safety.

COMMUNITY EVIDENCE DASHBOARD

Count reports. Keep the limitations.

0Structured reports
Independent sources
Routes represented
Adverse-effect reports
SUBMISSION SCHEMA

Compound • amount/range • route • frequency • duration • goal • positive observations • negative observations • concurrent compounds • source • date.

No testimonial is converted into proof of efficacy.