Methodology · version 1.0
The Compound Library combines Aliquot's canonical logging catalog with a separately maintained web reference catalog and editorial evidence layer. Missing evidence remains visibly missing; it is never filled with marketing copy or inference.
App-supported names originate from Packages/AliquotCore/.../Compounds.json. Additional
web-only reference names live in a separate reviewed catalog. A deterministic build step produces
web slugs and verifies that every stable ID appears exactly once.
Public status, summaries, evidence type, citations, limitations, review dates, and route-matched PK statements live in one reviewed content record per library identity.
Public competitor indexes may identify names worth reviewing, but Aliquot does not import their summaries, rankings, community reports, dosing material, or visualizations. Published statements are independently written from the original FDA, ClinicalTrials.gov, PubMed, or publisher source.
Animal, in-vitro, vendor, influencer, and unsourced claims are not promoted into human claims.
A pharmacokinetic estimate is public only when the route is explicit and matches the statement. Intravenous data is not relabeled as subcutaneous data. Combination entries do not inherit a synthetic half-life from their components.
If a source is missing, stale, ambiguous, route-mismatched, or insufficient for the proposed sentence, the sentence is withheld. A sparse page means “not published by Aliquot,” not “safe,” “ineffective,” “legal,” or “approved.”
Every public entry includes a last-reviewed date, next-review date, reviewer label, status-as-of date, and internal review note. Build validation rejects entries more than 90 days past review.
Publication states
| State | Meaning | Public build |
|---|---|---|
| Draft | Incomplete or awaiting evidence review. | Excluded |
| Reviewed | Required metadata and citations passed validation. | Included |
| Withheld | Known identity with prose intentionally suppressed. | Excluded; sparse reviewed record may replace it |
Web tools mirror the existing Aliquot calculator formulas in TypeScript. Golden fixtures cover representative values, unit boundaries, invalid input, and rounding. Results never select an amount or cadence for the user.
Library search is client-side. Calculator inputs are not sent to an Aliquot server, written to browser storage, added to URLs, or captured by telemetry. The Cloudflare Pages deployment is static and has no database or account layer.
Report a source, identity, or calculation issue to [email protected]. Include the page URL and the primary source. Corrections update the review record and date.
Aliquot does not publish vendor or sourcing information, benefit promises, diagnostic or efficacy claims, dosing recommendations, personalized advice, or implicit storage/discard rules.