Review Process
Every evidence-sensitive page moves through the same stages — before publication and on a schedule afterward.
Last updated: July 11, 2026
A page on Synptide is not "written once and forgotten." It moves through a defined pipeline, and it carries a visible provenance block showing when it was last checked and what version it is.
Before publication
- Evidence search. We gather the primary literature — trials, regulator documents, and reviews — and record the date of that search.
- Drafting. Claims are written against sources, with human and preclinical evidence kept separate and each outcome graded on the A–U framework.
- Fact-check. Load-bearing numbers and every cited link are independently re-verified. Dead links and inaccuracies are fixed before publish.
- Quality gate. A build-time validation step blocks publication of a compound with no regulatory status, a page with a missing source, or a tool with no methodology.
After publication
Content is re-reviewed on a cadence tuned to how fast the evidence moves:
| Content type | Review cadence |
|---|---|
| Approved-medication profile | Every 90 days |
| Research-peptide profile | Every 90 days |
| Regulatory page | Monthly or event-driven |
| Safety-critical page | Event-driven and at least every 90 days |
| Major guide | Every 180 days |
| Calculator methodology | Annually, or when a source formula changes |
| Glossary term | Annually |
On authorship and review credit
Synptide content is produced and maintained by the Synptide editorial team, and pages are credited to The Synptide Team rather than to a fabricated individual byline. Where a page has been checked by a named subject-matter reviewer with relevant credentials, that name appears in the page's provenance block. We do not invent reviewers, credentials, or license numbers to manufacture authority — an absent reviewer name means the page has been through editorial and fact-check review but not a separate named expert review.
Flagging a problem
If something looks wrong, tell us. Our corrections policy explains how we handle it and how fixes are logged.