Technical methodology

The pipeline behind every grade.

The technical companion to How the grading works, for scientists, clinicians, and people who build data and AI systems. It documents the evidence model, the mechanism rules, the scoring arithmetic and its caps, where language models do the work and how their output is checked, the verification gates and the audit program. Each rule says whether it is enforced by code or by procedure, and the last section lists what the system does not yet do.

Pipeline state as of 25 October 2026, checked rule by rule against the running code and the canonical pipeline documents of that date. Numbers marked live are computed from the catalog each time the site is built.

107interventions graded
1,391hallmark ratings (13 per intervention)
52pathways on the mechanism map
37pages revised since first build
35pages with checked claims
86ratings tagged Mixed results
How the 1,391 hallmark ratings fall today
Strong 27 (1.9%)Supported 88 (6.3%)Emerging 477 (34.3%)None 799 (57.4%)

Strong is deliberately rare. Most cells are None because most interventions engage only a few hallmarks. Computed from the catalog each time the site is built.

0 · Abstract

What this is, and what is new.

A rule-based, verification-gated pipeline that grades the evidence that a longevity intervention engages the biology of aging, one hallmark at a time. Language-model agents read, extract and propose mechanism scores under written rules; deterministic code computes the evidence scores, every rating and every displayed rating word; every cited study is verified against PubMed on entry. It runs on 107 interventions today.

Each intervention gets a score on each of 13 hallmarks of aging from two axes that are multiplied: a mechanism score anchored to a curated pathway map, and a replication-gated evidence score built only from studies that found an effect. Studies that found no effect can hold a rating down but never add to it. Funding, circulating claims, safety and absorption are reported beside the score on separate rails. The contribution is a methods-and-application framework; its parts build on established techniques (controlled-vocabulary curation, literature triage, GRADE-adjacent appraisal, funding extraction, workflow provenance). What we claim is the integration, at scale:

  1. (i)Three parallel controlled vocabularies (biomarker, disease, pathway) route any study to one 13-hallmark schema by independent evidence signatures, combined in one deterministic score.
  2. (ii)An evidence score with explicit null handling: one vote per trial, a like-for-like Mixed-results hold, and a rule that withholds credit for unstated design facts without asserting them.
  3. (iii)A conflict-of-interest layer that checks every human study in up to twelve places and cannot publish a label, a conflict or independence, that it cannot trace to a field or a verbatim quote in the source.
  4. (iv)An operating model: writer and verifier in different sessions, independent mechanism readers, fresh-session audits with a separate review seat, and every method change shipped as a dated, approved release.

Verification is not validation. The gates below establish internal consistency: the pipeline is traceable and reproducible. None of them measures accuracy against an external ground truth. No gate-pass count on this page is an accuracy figure; section 15 says where validation stands.

1 · Design principles

Seven rules the rest follows from.

Each principle names how it is enforced: code a script exits or recomputes, procedure a run-sheet step or a fresh checker carries it, or both.

01Rules before results

Selection, flag and scoring rules are written before a page is scored and apply to every page. Above the 120-study cap, studies are chosen by design in a fixed order, never by direction of result, and a check guards the share of no-effect trials kept.

code + procedure DR-B selection rules; rescore_v4.py
02Models read; code decides

Language-model agents search, read, extract, propose mechanism scores and draft under written rules. Every evidence score, rating, randomized-trial flag and displayed rating word is computed by deterministic code from the extracted fields.

code rescore_v4.py at deploy; heroWords.ts at render
03Every identifier verified at the source

No PMID enters the catalog unless it is verified against live NCBI E-utilities; if the API is down, the run stops. Batched outputs are keyed by PMID, never by position.

code Step 1c cache build; add path checks author and year; Step 8 R1
04Withhold credit; never assert a flaw

A design fact the abstract does not state costs one deduction, but the page says “not stated”, never “small” or “unblinded”. A trial is excluded only when all three shortfalls are measured.

code study_flags.rct_flag_from_fields; validator Rule 11b
05Funding is shown, not scored

Per-study conflict-of-interest labels are never read by the scoring engine. Two declared exceptions: a pooled analysis’s quality flag weighs single-manufacturer funding, and company-leaning items can block the top stack grade.

code No biasClassification in rescore_v4.py, heroWords.ts or scoring code
06Checks can lower, not raise

A one-point split between mechanism readers takes the lower score. The audit checker can confirm or lower a mechanism score, never raise it. The Mixed-results rule can only hold a rating down.

code + procedure Reconciliation rule; checker brief; MIXED_RESULTS_CAP
07Every method change is dated

Runs and audits never edit the rulebook; they log proposals. Changes ship in batched, approved Doc Releases, are re-applied to every page, and pages carry version numbers.

procedure BOOTSTRAP rule 7; pipeline_proposals.jsonl; _version
2 · Target schema

Aging biology as a fixed set of thirteen targets.

The hallmarks of aging are a consensus set of processes whose disruption contributes to aging and whose modulation can in principle slow it. Here they serve as a fixed, low-dimensional target schema: every finding, whatever its endpoint (a methylation clock, a lipid panel, a hazard ratio), is routed onto these thirteen cells. That shared coordinate system is what lets heterogeneous evidence be combined. Hover or tap a hallmark.

H11Chronic inflammation

Persistent low-grade inflammation. Reserved for pathways whose core function is inflammatory signaling; downstream anti-inflammatory effects stay with their primary hallmark.

Four hallmarks marked frontier (H2, H5, H9, H13) are left out of the breadth count in the stack grade (section 11), because today’s evidence cannot reliably move them across a routine. They are rated like any other hallmark.

3 · Architecture

Two sessions, a gate on every step.

Every new intervention runs in two sessions, so the session that writes the research never verifies it. The research session dispatches one subagent at a time and stops. A separate session verifies, maps, scores and builds. Runs are unattended: judgment calls take the conservative option, record both sides, and are reviewed after the run. Tap any step for what it does, its gate, how that gate is enforced and the failure it exists to prevent. Most of those failures happened once; the gate came after.

language-model agents agents plus a code verifier deterministic code deploy
Session 1 · Researchunattended, one subagent at a time
Session 2 · Verify and builda different session; the writer never verifies
Deployscores regenerated from the research file
After deployfresh sessions, page by page
deterministic codeStep 8 · Integration auditcode

Twenty deterministic cross-record rules (R1 to R20): PMID-keyed dictionary integrity, tier consistency, animal studies at human tiers, narrative reviews at L6 or L7, penalty data present, mapping audit trail, the six labels, label sources, direction against good or bad news, null consistency, lookup keys and endpoints present, cross-step PMID consistency, the 6.5 record, animal pooled analyses at L7, trials mis-promoted to L7, and two schema checks.

gaterun_step8.py exits 2 on any failure and writes no Step 8 manifest, so Steps 9 and 10 cannot write theirs.
preventsCross-record contradictions reaching the build.
Go deeperThe manifest chain and the attestation gate

Eleven steps write a manifest: step1c → step2_3 → step4 → step5 → step6 → step6_5 → step6_7 → step7 → step8 → step9 → step10. Each records the upstream manifest as file#sha256, plus the script, step-document and reference-file hashes, the output hash and a timestamp, and is schema-validated before it is written. A writer refuses when the upstream manifest is missing.

Each step script checks that its upstream manifest exists and is schema-valid; it does not re-check the hash. The hash links are walked at deploy: a broken link in a complete chain exits 8, while an incomplete chain (legacy pages) only warns. Steps 9 and 10 manifests are written by the orchestrator through the same helper.

Nine steps also require a fresh re-read of their step documents: an attestation file with three verbatim quotes of 30 or more characters from each required document, younger than 60 minutes (240 in audits).

4 · Language models

Where the models work, and what checks them.

The system is best described as verification-gated, human-supervised automation. Language-model subagents do the reading-heavy work, including proposing mechanism scores and pooled-analysis flags under written rules. Deterministic code computes the evidence scores, ratings, trial flags and rating words. A person approves rules, never an individual score. In unattended runs subagents read and write files only; the orchestrator fetches PubMed records and web pages into dated files that subagents cite from.

StageWhat a model doesWhat checks itEnforced by
Mechanism (DR-A)Two independent readers score MS 0 to 5 per hallmark, with citations.Lower score on any split; map anchoring and citation tiers; a fresh audit checker on every 4 and 5 that can only lower.File-overlap script run by hand; validator warnings; written rules
Study catalog (DR-B)Search, screen and select studies; assign pooled-analysis flags from full text.PubMed supplies every metadata field; every PMID verified; Step 4 re-tiers from PubMed publication types; Step 8 tier rules.Code (Steps 1c, 4, 8)
Claims (DR-D)Find, source and test the claims people are hearing.A fresh checker re-opens every source and re-verifies every PMID; six locked status labels.Procedure; the build drops unknown statuses and strips names
Funding (DR-C)Propose a label for each human study, with a cite-back.Byte-level verify or drop to Pending Review; a person confirms each tie a machine finds.Code (Step 1.5, schema gate, Step 8 R7 and R8)
Endpoint mapping (Steps 5 to 6)Build lookup keys; map endpoints to hallmarks.Literal map lookup; the between-group rule; a two-auditor significance check on trials.Code verifiers (exit 2; duplicate mapping is a hard fail)
Writing (Steps 9 to 10.7)Study summaries, mechanism text, the summary paragraph.Fresh-eyes check against each abstract; a fact-checker on the summary; the count line must match the cache; fabrication and banned-token scans; the page checker.Code (build exits 15 to 20, deploy exit 6); page checker by procedure
Scores and rating wordsNone.Computed by rescore_v4.py at deploy and heroWords.ts at render.Code
RulesNone.A person approves every rule change in a dated release, and never sets an individual score.Procedure

Failure modes designed against

A citation that does not exist, or points at the wrong paperIron Rule at entry; author and year must match on additions; the citation scorer for safety text; re-verification at Step 8.5.
A study’s data merged onto the wrong recordPMID-keyed dictionaries end to end; Step 8 R1; duplicate mappings are a hard fail.
A missing funding record read as “no conflict”The offline cache integrity check; Independent needs a source just as a conflict does; silence becomes a disclosure state, never a label.
Two “independent” mechanism opinions that are really oneSeparate dispatch and separate files; the file-overlap gate; the lower score on any split.
Invented numbers in proseThe count line must match the cache; fabrication and banned-token scans at build and deploy.
Choosing the studies that flatter a resultDesign-ordered selection above the cap; the no-effect share check; audits add large no-effect trials.
A stale copy overwriting newer scoresScores regenerated at deploy from the research file; single-entry splice; concurrency re-check.
5 · Mapping vocabularies

Three independent routes to the same hallmark.

These are expert-curated controlled-vocabulary mapping tables, not ontologies in the OBO or OWL sense: no formal axioms, no reasoner, and not yet aligned to GO, MONDO, DOID or Reactome identifiers (named work in section 15). Their useful property is parallelism: a study can reach a hallmark through a measured biomarker, a disease endpoint or a documented pathway engagement.

Biomarker to hallmark~350 rowsDisease to hallmark94 diseasesPathway to hallmark52 pathways13-hallmark schemathe fixed target everyfinding routes onto

Studies that measured a molecular or physiological marker (REF1). Each row carries a directness tier (direct, endpoint proxy, inferential), an expected direction, and primary and secondary hallmarks.

row formatBiomarker | Directness | Direction (up / down / CTX) | Primary H | Secondary H | Secondary rule
exampleCRP ↓ (sig) → H11, POSITIVE
Go deeperDirection, context and disambiguation

Each biomarker has an expected direction: up, down or CTX (context-dependent). A CTX row takes its sign from the intervention class set in DR-A (supportive by default; flip classes mitohormesis, anabolic restoration, rejuvenation, efficiency and knockout validation), and a per-study override can set it explicitly; the scorer applies the override first.

Disambiguation is part of the map: chaperone-mediated autophagy is H4, not H5; H11 is reserved for pathways whose core function is inflammatory signaling, so the anti-inflammatory side effects of energy-sensing or antioxidant-response pathways stay with their primary hallmark; stress and mood questionnaires route to H10 only.

6 · One study’s path

How one paper becomes part of a rating.

Follow one randomized trial from retrieval to a displayed word. Step through the stations; the funding lane below runs on the same paper and never touches the score.

station 8 of 11Trial vote

All reports of this trial agree on H11, so the trial casts one POSITIVE vote. A follow-up paper on the same trial would not add a second.

1 vote per trialKey per hallmark
parallel rail · funding and conflicts of interest

On the same study, the funding lane runs separately: harvest, the verify-or-drop gate, the paper’s own disclosure quoted, then a label such as Independent. The label is shown on the study card and never read by the scoring code.

7 · Evidence score

Replication-gated, positive studies only.

The evidence-quality score (EQ, 0 to 5) is set by how many qualifying studies replicate, not by the single best one. EQ 1 and 2 are preclinical; human evidence begins at 3. Each study is first placed on a seven-level ladder by design.

L7Pooled analysis of randomized trialsPer-study ceiling 5. Pooled observational studies go to L5, mixed human and animal pools to L3, animal or cell pools to L2.
L6Randomized controlled trialCeiling 4. Animal trials tagged as randomized are caught and moved to L2.
L5Mendelian randomizationCeiling 4 (also pooled observational analyses). Caps at EQ 3 without a GREEN L6 or L7.
L4Large prospective cohortMore than 1,000 people and more than 5 years; non-randomized human trials are placed here too. Caps at EQ 3 alone.
L3Observational, cross-sectional, case-controlCeiling 3.
L2Animal, in vivoCeiling 2, whatever the design.
L1Cell, in vitro, computationalCeiling 1. Narrative reviews are placed here, whatever they are called.

Only positive-direction studies count. L1 to L5 count study by study; L6 and L7 count once per trial, and only when the trial’s vote on that hallmark is POSITIVE. A trial whose reports disagree (one positive, one not) is MIXED and counts on neither side. A trial takes its best-flagged report’s flag.

L6 trial flag (study_flags.rct_flag_from_fields)
Axisokshort (measured)unknown
Samplen ≥ 80 enrolledn < 80not stated
Duration≥ 8 weeks< 8 weeks (single dose counts as short)not stated
Blindingdouble, single or triple blind or maskedopen label or another measured unblinded designnot stated, or placebo-controlled with no blinding word; n/a for behaviors

Deductions = short + unknown axes. GREEN 0 · YELLOW 1 · RED ≥ 2 · WARNING only when all three are measured short. WARNING is excluded from the evidence score and stays on the page.

L7 pooled-analysis flag (assigned by DR-B from full text, transcribed verbatim)
  • GREEN: a recognized quality tool (Cochrane RoB, GRADE, AMSTAR-2) reported; I² reported; ≥ 5 trials and ≥ 500 participants; PROSPERO or Cochrane methods; no single-manufacturer dominance. Bayesian or network analyses: GRADE high or moderate, ≥ 10 trials, ≥ 1,000 participants.
  • YELLOW: one RED criterion, or most pooled trials at high risk, unexplained I² > 75%, pooled n < 500, fewer than 5 trials, or authors with industry consulting roles.
  • RED: two or more of no quality tool, no I², ≥ 75% of trials from one non-English database, under 50 per arm, no PROSPERO and no PRISMA, nearly all trials funded by one manufacturer.
  • WARNING: predatory publisher, retraction, or every author employed by the manufacturer.
Go deeperWhat a vote is, and what is not a vote
  • One vote per trial. Reports that share a trial key form one trial per hallmark. All POSITIVE gives POSITIVE; POSITIVE beside any NULL or NEGATIVE gives MIXED (neither side); otherwise NEGATIVE if any is negative, else NULL. Applies to the ladder, the Mixed-results tally, the page Evidence word and the Contested and Tradeoff tags.
  • Between-group only. A trial earns POSITIVE only for a difference against placebo or control; a change inside one arm, or ambiguous wording, maps NULL (Step 6, re-read in every audit).
  • Comparator. A no-difference result against an active drug with no placebo arm, or between doses with no untreated arm, is not a no-effect vote. A positive result still counts.
  • Disease inference. A no-effect result reached only through the disease table (a failed progression trial) does not vote against a hallmark; disease-inferred positives still count.
  • Cognitive and mood scales map only with age 50+ or a cognitive complaint, dosing of 8 weeks or more and MS 3+ on the target; since 7 October 2026 an adequate test that found nothing maps NULL.
  • Specified but not implemented: an EQ cap at 4 when every positive GREEN contributor is a cognitive or stress scale (Algorithm §1.4). The scorer does not apply it today.
8 · Mechanism score

A ladder of engagement, anchored to a map.

The mechanism score (MS, 0 to 5) asks whether there is a documented biological route from the intervention to each hallmark, using the most direct pathway when several exist. Every MS of 3 or more must name a pathway on the 52-row map at the claimed tier or stronger; an off-map pathway can support at most 2 until it is promoted after review, and a pathway that lists the hallmark only as a contributing one caps the score at 3. One molecule may hold MS 5 on at most two hallmarks.

MSLabelDefinitionCitation barShown as
5DIRECTThe active molecule binds, inhibits or activates a target in the hallmark’s defining pathway.At least one primary paper: Kd or Ki on purified protein (ITC, SPR, fluorescence polarization, radioligand), a knockout, knockdown or dominant negative that abolishes the effect, or a co-crystal or cryo-EM structure. Never a review. Without it, the maximum is 4.Direct, well-established
4INDEPENDENTA second direct-class engagement of a different target on a mapped pathway. In practice also where a direct engagement lands when the tier-5 proof is missing.Two or more papers, at least one primary experimental; reviews do not count toward the two.Direct
3SECONDARYA downstream consequence of the primary or independent pathway, on a mapped pathway.At least one paper describing the downstream engagement (a review with a traceable chain is still accepted; primary-only is a pending proposal).Downstream
2INDIRECTA biomarker of the hallmark changes in a study of the intervention, with no established pathway. Not a mechanism claim.At least one PMID, any study tier. Also set by Step 6.5 when MS was 0 and positive human evidence reaches EQ 4.Indirect
1HUB ANCHOROne of the eight hub molecules is among the intervention’s targets or effectors and the hub table links it to the hallmark.No intervention-specific citation; applied mechanically to MS 0 cells only.Indirect
0NONENo established link.No citation needed.Not established
Mechanism scores across all 1,391 hallmark cells (live)
7350
1701
1482
1803
1094
495
Go deeperTwo readers, reconciliation, and the audit checker

Two subagents, dispatched separately, write separate files; neither sees the other’s, and the orchestrator never authors a score. Agreement gives that value; a one-point split takes the lower; a split of two or more also takes the lower, records both rationales and flags it for review after the run. A file-overlap gate (word-set Jaccard under 0.60, run by hand) checks the two files were not copied; it does not measure agreement. Every MS of 4 or 5 gets a written reviewer card.

In every audit, a fresh checker who did not score the page re-verifies each 4 and 5 from a dated PubMed packet: the papers exist and say what is claimed; they are primary; none is retracted or under an expression of concern; the map allows the score; the citation rules are met; and how far the lab concentration sits from human blood levels at a real dose (gaps over tenfold are flagged). A requirement it cannot confirm counts as not met. The verdict is CONFIRMED or LOWER; it never raises a score.

Go deeperAmendments, top-ups and special cases
  • Step 6.5: MS 0 becomes 2 when positive human studies on that hallmark reach EQ 4 (not a mechanism claim).
  • Step 6.7: MS 3+ with no positive study triggers a targeted cell and animal search; it never changes MS.
  • Tier 5 for every class since 13 October 2026: substrates of the body’s own enzymes, the active molecule a precursor becomes, and drugs whose bound target is an obligate cofactor of the mapped route. Substrate knockout does not reach 5; a solved structure can.
  • No identified target (for example, a peptide with no known binding partner): the best reachable score is 3, through a mapped downstream node.
  • Lifestyle archetype (the two exercise pages): Strong needs MS 4 rather than 5; the evidence anchors are unchanged.
Go deeperHow these rules are enforced today

Honestly: mostly by procedure. Code checks are the independence gate, an MS range check, validator warnings when an MS 5 cites a review or a shipped MS differs from the readers’ table, and the Step 6.5 record. Map anchoring, the citation tiers, the two-hallmark cap on MS 5 and the reviewer cards are carried by the readers’ rules and the audit checker; no script reads the map. Six MS 5 cells on five older pages are grandfathered pending full re-runs, and some older pages predate the two-reader rule.

Decided in principle, not yet applied (15 October 2026): an exposure gate that caps a score when the key experiment’s concentration far exceeds human unbound blood levels at the product dose, a requirement that binding change function, and a dose-increment test. The planned sweep is expected to lower several Strong ratings.

9 · Ratings and words

A transparent function, then gates, then words.

The two axes are multiplied, so a strong mechanism with no human evidence and strong human evidence with no mechanism both stay low. The rating is then gated on study anchors, not thresholded on the product alone. Toggle between values and ratings, and between molecules and the lifestyle archetype.

IES = MS × EQ / 5            0 if MS = 0 or EQ = 0;  0 < IES < 0.5 is raised to 0.5

Strong     IES ≥ 4  and  MS ≥ 5 (MS ≥ 4 lifestyle)
           and ≥ 2 positive L4 to L7 studies (one vote per trial)  and  one with n ≥ 100
Supported  MS ≥ 4  and  IES ≥ 2  and  ≥ 1 positive L6/L7 trial vote (GREEN, YELLOW or RED)
Emerging   IES ≥ 0.5
None       IES = 0

Hold       mixedResults  =>  Strong → Supported,  Supported → Emerging   (IES unchanged)
IES and rating by mechanism score (rows) and evidence score (columns)
MS / EQ012345
5
4
3
2
1
0
IES = (MS 5 × EQ 4) / 5 = 4.0Strong, if ≥ 2 positive L4 to L7 studies, one with n ≥ 100; otherwise Supported

The Mixed-results hold, as code

Good no-effect trials can hold a rating down; a pile of weak ones cannot, and a pile of weak positives cannot outvote good no-effect trials. Set the trial counts and watch the rule fire.

Rating before the hold
good positive
1
good no-effect
2
weak positive
0
weak no-effect
0

Good = GREEN or YELLOW trial votes; weak = RED. WARNING trials, and no-effect results reached only through the disease table, are not counted. One vote per trial.

mixedResults = trueEmerginggood no-effect trials ≥ 2 and outnumber good positives. The word is held one step lower; the IES does not change.

Every word on the page, computed

The page’s Evidence, Verdict and Independence words are computed from the data. Ratings, Mixed-results tallies and the Evidence and Verdict words are computed at deploy; the Evidence, Verdict and Independence words are computed again when the page is shown, and the shown values win. Form-dependent is the one label a writer sets.

Evidence (page tile; whole catalog, any direction)
Robust
(≥ 2 GREEN L7, or ≥ 3 GREEN L6 trials counted by trial key) and ≥ 1,000 people (GREEN L7 pooled n plus the largest n of each GREEN trial)
Moderate
≥ 1 GREEN L7 or GREEN L6
Thin
any study at L4 to L7, any flag, any result
Very Thin
nothing at L4 or above
Verdict (page tile), then tags in brackets
Established
lifestyle archetype with a typed Established verdict
Strong on N driver(s)
N hallmarks rated Strong, N spelled out
Supported, not strong
≥ 1 Supported, none Strong
Emerging only
≥ 1 Emerging, none higher
Mechanism only
no hallmark rated and max MS ≥ 3 (in practice: no hallmark has both MS ≥ 1 and a positive study)
Thin everywhere
none of the above
(Contested)
on Strong or Supported hallmarks, ≥ 1 NEGATIVE L7 or ≥ 2 NEGATIVE L6 trials; no quality filter; one vote per trial
(Tradeoff)
exactly one NEGATIVE L6 trial and no NEGATIVE L7, on Strong or Supported hallmarks
(Mixed results)
any hallmark with mixedResults that is not rated None (it can fire on an Emerging hallmark the hold did not lower)
(Form-dependent)
set by the writer from the product-form evidence; the one label a person chooses
Independence (page tile; human studies L3 to L7, at render)
No human studies yet
no human studies
Limited disclosure
classified < 3, or classified < half the human studies (classified = any label but Pending Review)
Mixed: large trials company-funded
company-funded share < 0.5 overall but ≥ half of the L6 trials with n ≥ 100 are company funded
Fully independent
company-funded share 0 (company funded = Industry Funded or Industry-Designed)
Mostly independent
share < 0.34
Mixed funding
share < 0.5
Industry heavy
share ≥ 0.5
Go deeperKnown edge cases
  • The deploy-time (Python) and render-time (TypeScript) word functions differ on edge cases: the render side does not apply per-study direction overrides or mapping tags. No validator compares stored and shown words.
  • “Ranks highest” on a page orders hallmarks by IES, so an Emerging hallmark (MS 3 × EQ 5 = 3.0) can rank above a Supported one (MS 4 × EQ 3 = 2.4).
  • The per-hallmark evidence words are tied to EQ, not study type: EQ 1 reads “Lab cells only” even when the single study is an animal study.
10 · Beside the score

Funding, claims, safety and absorption, on separate rails.

Funding and conflicts of interest. This is the layer most evidence summaries leave out, and the one we built to fail safe. Every human study (L3 to L7) is checked in up to twelve places, each label must survive the verify-or-drop gate, and the governing rule is to under-assess rather than falsely accuse. That rule cuts both ways: Independent needs a source just as a conflict does, and silence is reported as a disclosure state, never read as a label. Per-study labels are never read by the scoring code.

SourceWhat it yieldsWhere it enters
PubMed recordConflict-of-interest statement, grant list, author affiliationsStep 1c cache; disclosure harvester
PubMed Central full textFunding, conflict and acknowledgment sections; sentences saying who supplied the productStep 1.5 verification (tiers B and C); harvester
Europe PMCFunder records; full text PubMed Central lacksFunding harvest; harvester
OpenAlexFunders linked to the work; best open-access locationFunding harvest; harvester
Crossref Funder RegistryFunders registered by the publisher (by DOI)Funding harvest
ClinicalTrials.govLead sponsor, sponsor class, collaboratorsFunding harvest; DR-C and the registry rule
Open-access copiesLegal free full text located by DOIHarvester
Publisher’s pageFunding and conflict sections shown outside the paywallHarvester
University library accessPaywalled full text, rating-driving trials first, quoted with the access dateCOI pass, one paper at a time
US Patent and Trademark OfficeGranted patents, holders, inventors, status and termPatent check
European Patent OfficeEuropean patents and worldwide legal eventsPatent check
PubMed author countsThe top author’s share of the ingredient’s literatureAuthor-concentration check
Industry-DesignedIndustry-funded, author tiesThe manufacturer paid and at least one author is employed by or affiliated with it. Both halves verified.
Industry FundedIndustry-fundedThe manufacturer paid; no manufacturer-employed author.
Researcher-AffiliatedResearcher-AffiliatedAn author disclosed a financial tie (consulting, advisory, board seat, equity or employment), whatever the funding.
Supplement SuppliedProduct suppliedAn academic-led study in which the manufacturer supplied the product only.
IndependentIndependentGovernment, academic or non-profit funding with no manufacturer involvement.
Pending ReviewNo statement in the paper · Abstract only · Still being reviewedNo label yet. The page says which: the full paper states nothing, only the abstract could be read, or a source awaits classification or a person’s confirmation.
Go deeperVerification, review and what readers see
  • Three evidence tiers. A proposed label cites a structured field (grant, registry sponsor, affiliation), a PMC XML element, or a verbatim quote. Step 1.5 re-checks it against the cache or the stripped XML (normalized substring match); a failure drops the label and logs it. Industry-Designed needs both halves verified separately; one half yields Industry Funded or Researcher-Affiliated.
  • Registry rule. A ClinicalTrials.gov sponsor of class INDUSTRY makes the trial company funded; OTHER, NETWORK or NIH counts toward Independent.
  • Human review. Every tie found by machine, and every label that would change, waits in a review queue for a person; nothing in the queue is applied until decided. Every author-inventor match needs a person’s approval against affiliation or disclosure evidence.
  • Quotes. At most two passages per study from the paper’s own disclosure (full text first, then the publisher page, the PubMed record and the grant list), trimmed at a sentence boundary.
  • No names in our text. The fixed one-sentence notes name no company, researcher or grant; a content validator blocks names and corporate suffixes at deploy. The quoted disclosure carries the names.
  • On the page. The funding section opens with a summary whose percentages use only the studies we could check as the denominator, with unknowns counted separately; a three-part bar; results by funding (what company-tied and untied studies found on aging drivers); a who-does-the-research line when one author is on more than half of the ingredient’s literature (shown after a person approves it); the patents; then every study with its label and quote.
Go deeperPatents

The patent check searches the US Patent and Trademark Office (Open Data Portal) by invention title and named holders, and the European Patent Office (Open Patent Services) for European patents and worldwide legal events. Pages list granted medical-preparation patents (CPC A61) whose title names the ingredient, active patents first. Status comes from the office record: in force; in force but possibly ending sooner (a terminal disclaimer is flagged, never guessed); expired; or expired for unpaid fees. A US term runs 20 years from the earliest non-provisional or PCT filing plus any term adjustment.

Go deeperWhere funding is used by rule

Two declared places. A pooled analysis’s quality flag weighs single-manufacturer funding of the pooled trials, all-employee authorship and authors’ consulting roles, because that is part of appraising the analysis. In the stack grade, items whose classified studies are at least half company funded (with three or more classified) block Exemplary when they reach 30% of the stack. Nowhere else does funding enter a rating.

Claims. Up to six per audited page (three pages built before the cap carry more), label claims always included, the rest ranked by independent repetition. Each card reports what was tested and found, attributed to the trials, under one of six locked statuses; it never confirms, denies or grades a claim and never names who made it. A fresh checker re-opens every source before a claim ships. 35 pages carry a checked claims section today.

Safety and cautions. Ingredient-level safety from about a dozen source types (FDA, EFSA, Health Canada and TGA actions; LiverTox; upper intake limits; NIH ODS; systematic case reviews; the page’s own trial adverse events), quoted exactly from dated fetches. Single case reports and adverse-event tallies without a denominator are excluded. Cautions carry one of four severities and one to three stating sources, re-checked at Step 8.5; older pages carry an earlier format until audited.

Absorption and form. A GREEN, YELLOW or RED absorption flag (shown as High, Moderate, Low) with the main barrier named, and a product-form note where the source decides the outcome. Absorption never enters an intervention’s score; it enters only the stack engine.

11 · Stack grade

Breadth times quality, minus redundancy, gated on exercise.

The member’s Longevity Intelligence Report grades a whole routine in five words (Exemplary, Solid, Mixed, Thin, Speculative), with no number shown. The grade reads each item’s per-hallmark rating and applies the rules below, in order; caps only lower a grade. Size is neutral: the penalties are shares of the stack.

QuantityDefinitionRule
Strong anchorany hallmark (frontier included) with a stack item rated Strongnone: Thin, or Speculative if no item is Strong or Supported anywhere
breadthFracaddressable hallmarks (13 minus the 4 frontier) whose best item is Strong or Supported, over 9Exemplary ≥ 0.8 (8 of 9); Solid ≥ 0.4 (4 of 9)
q (quality)items rated Strong or Supported on at least one hallmark, over all itemsExemplary ≥ 0.65; Solid ≥ 0.45
strongBeyondExercisehallmarks where a non-lifestyle item is rated StrongExemplary ≥ 3
redundancyFracshare of absorption-adjusted credit lost to same-group overlapExemplary < 0.12; ≥ 0.30 caps at Mixed
pileMaxitems in the largest same-group pile present≥ 3 blocks Exemplary; ≥ 4 caps at Mixed
conflictFraccompany-leaning items (≥ 3 classified studies, ≥ half company funded) over all itemsExemplary < 0.30
redAbsorbRED-absorption items taken by mouthExemplary needs < 3 and < 25% of items
foundationresistance or cardiovascular training presentabsent: caps at Mixed
minimumdistinct graded itemsfewer than 2: no grade
grade(stack):
  if items < 2                      -> no grade
  if no Strong rating anywhere      -> Speculative if nothing Strong/Supported, else Thin
  clean = redundancy < 0.12 and pileMax < 3 and conflict < 0.30
          and redAbsorb < 3 and redAbsorb/items < 0.25 and strongBeyondExercise >= 3
  if breadth >= 0.8 and q >= 0.65 and clean   -> Exemplary
  elif breadth >= 0.4 and q >= 0.45           -> Solid
  else                                        -> Mixed
  cap at Mixed if redundancy >= 0.30 or pileMax >= 4
  cap at Mixed if no exercise
Go deeperOverlap groups and absorption factors

Items that work through the same route are grouped (each item in at most one group). Within a group, items are sorted by absorption-adjusted value and the item at rank r counts × decayr: the strongest in full. Decay bands: 0.15 tight (same node or pool), 0.45 same class, 0.85 complementary.

GroupDecayMembers
NAD pool0.15NMN, nicotinamide riboside, nicotinamide
Stilbene / SIRT10.20resveratrol, pterostilbene
Glutathione pool0.20NAC, glutathione
Carnosine synthesis0.15beta-alanine, carnosine
Nitric oxide layers0.85citrulline, pine bark extract, beetroot
NF-κB inhibitors0.50curcumin, omega-3
Antioxidant generation0.45astaxanthin, CoQ10
AMPK activators0.45berberine, alpha-lipoic acid, metformin
Senolytic flavonoids0.30fisetin, quercetin
Growth-hormone axis0.30growth hormone, tesamorelin, sermorelin
Prebiotic fiber0.45inulin, psyllium, resistant starch, butyrate
Mushroom glucans0.45turkey tail, chaga, reishi, shiitake, maitake, cordyceps
Joint matrix0.45collagen, hyaluronan, glucosamine, chondroitin, MSM
Choline sources0.30alpha-GPC, citicoline, phosphatidylcholine
Vitamin K2 forms0.20MK-7, MK-4

Absorption factors: GREEN 1.0, YELLOW 0.6, RED 0.3, unknown 0.8; exercise and injected products 1.0. They change per-hallmark coverage (bar length and gap detection), the overlap share and the ranking of suggested additions, not breadth or quality.

Per-hallmark coverage is min(100 × (1 − e^(−0.036·S)), 98), where S is the summed IES after the absorption factor and the overlap decay (items at IES 0.5 or more). It sets bar length and gap callouts only. A weighted 0 to 100 composite still exists in the engine but is never shown and is not read by the grade.

12 · Verification

Seventeen gates, and how each one is enforced.

Software-style quality assurance applied to evidence synthesis. Code gates halt the step that runs them. Several gates are scripts a person runs before deploy, and stop the run by procedure. Some checks are warnings by design. Tap a gate.

gateVerify or drop
wherestep1_5_coi_verify.py
on failurelabel dropped to Pending Review

Byte-level check of each conflict claim against the cache or PMC XML.

Two invariants stated in full. The Iron Rule: no citation enters unless its identifier is verified against live NCBI E-utilities, and if the service is down the run stops rather than approximating. PMID-keyed dictionaries: every batched output is keyed by identifier, never by position, so a study’s data travels with its identifier and cannot be merged onto the wrong record. Both exist because the opposite once happened. Note what the Iron Rule is not: there is no re-query of PubMed at deploy; identifiers are verified on entry.

13 · Audits and change log

Every page re-audited by a session that did not build it.

The audit program brings each deployed page to the current bar without a fresh deep-research pass. One page per fresh session; a separate review session checks each finished audit; a page whose problems are too broad to patch gets a full re-run instead. As of 22 October 2026, 35 of 107 pages were done; the live count of pages revised since their first build is 37.

  1. 1TriagePage checker, synonyms, legacy test. A pre-schema page stops here and is queued for a full re-run (major version).
  2. 1.5Data integritySizes, durations and blinding re-decided from the live abstract; one trial key per trial; within-group positives nulled; comparators checked; registry-industry trials relabeled; out-of-scope studies dropped.
  3. 2Missed studiesFixed searches minus the catalog. Small literature (40 or fewer human trials): add every in-scope study. Large: up to 20, at least 5 to large no-effect trials when the pool has them.
  4. 3AdditionsNew studies run through the same steps: cache, relevance, tier, router, mapping, summaries, funding.
  5. 4Mechanism checkA fresh checker re-verifies every MS 4 and 5 from a dated PubMed packet and can only confirm or lower.
  6. 5Claims and cautionsClaims research and its checker; cautions and their checker.
  7. 6RewriteOne writer and a fresh fact-checker.
  8. 7ShipVersion bump, validator and page checker clean, every rating move explained in a dry run, deploy, live check, run record.
Go deeperVersioning and the rulebook

1.0 is the first build. A minor bump (1.1) is an audit correction, an added study or a score-moving rescore; a major bump (2.0) is a full re-run; patch versions mark non-rating changes such as retraction removals and rule-change redeploys. Each page shows its last review date and version.

Runs, audits and reviews never edit the canonical documents. They append one structured line per issue to a proposals log; changes land only in batched, approved Doc Releases, inside existing files, and are re-applied to every page. A proposal earns a change only if it fixes a code defect, corrects a wrong statement, or names a failure seen in two sessions.

Method change log

  1. 2026-10-22AuditsLatest audit deployed (fisetin v1.1). The audit checklist stands at 35 of 107 pages done.
  2. 2026-10-20FundingEuropean Patent Office connected (Open Patent Services): European patents and worldwide legal status. Layered claims backfilled on 31 pages.
  3. 2026-10-19FundingPatent check: granted US medical-class patents listed as in force or expired; an author is linked to a patent only after a person approves the match. Funding section opens with an overview of the studies we could check.
  4. 2026-10-19ClaimsLayered claim view: a one-line answer, then what was tested, what it found and the gap, then the studies.
  5. 2026-10-15decided, not appliedDecided in principle, not yet applied: an exposure gate comparing lab concentration with human blood levels, a binding-must-change-function test and a dose-increment test; trial-vote refinements; popularity-first audit order.
  6. 2026-10-14MechanismA drug whose bound target is an obligate cofactor of a mapped route counts as direct (tubulin added to map row 17).
  7. 2026-10-13Catalog120-row hard cap per run; design-ordered selection above it; a no-effect share check; product as sold; other routes out; acute-window and expression-of-concern exclusions; at most 20 cell or animal studies in a large literature.
  8. 2026-10-13MechanismThe tier-5 test applies as written to substrates, a precursor’s active molecule and obligate cofactors; a 5 cites a primary paper, never a review; structure, Kd and knockout papers searched before scoring; map row 52 (adenosine receptors).
15 · Limits and validation

What is not yet done.

The honest gap is validation. Everything above shows the pipeline is self-consistent and traceable; whether its mappings and scores are correct is a separate question, not yet answered empirically. Three studies would answer it.

study 1Inter-annotator agreement

Independent domain experts re-grade a blinded sample; report agreement (Cohen’s or Fleiss’ kappa) on mechanism scores, ratings and hallmark mappings.

study 2Funding labels against a gold set

Score the labels against hand-labeled funding and affiliation determinations; report precision, recall and the rate of correct Pending Review deferrals.

study 3Standard-ontology alignment

Map the three vocabularies to GO, MONDO or DOID, and Reactome identifiers so the disease and pathway layers interoperate and can be audited externally.

Known gaps in the running system

Procedure where code could bePathway-map anchoring, mechanism citation tiers and the two-hallmark cap on MS 5 are enforced by readers and the audit checker, not by a script. The page checker and the PMID alignment check are run by hand.
Specified but not implementedThe cognitive-only evidence cap described in the scoring specification.
Decided, not yet appliedThe mechanism exposure gate and its companion tests (15 October 2026).
CoveragePages not yet audited carry older cautions and no claims section. Some older pages predate the two-reader rule.
FreshnessThere is no automatic weekly refresh yet; pages change through audits and rule releases.

The ratings cannot be bought: no company can pay for a rating, and the rules above apply to everything graded. That is what makes the conflict-of-interest layer worth building: it faces outward, at the studies.

The plain-language version is How the grading works. The source of record is the canonical pipeline (BOOTSTRAP, AUDIT, the STEP and REF documents, the research prompts and the Pathway Map), the scoring specification, and the scoring code itself, which governs where a document and the code disagree.