Audit: QRS - Cortagen for Health & Longevity
Audit conducted on 31/08/2026 23:41 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 85 |
| Failed | 0 |
| N/A | 8 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | Spot-checked every populated span against the ER: protocol figures, tier items, contraindications, interactions, all six biomarkers and cadence all trace to literal ER text. |
| 1.2 | Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. | 🟢 | Cautious ER phrasing carried over: “Convention, not published study”, “No human equivalent published”, “Not established in humans”, “No established target for Cortagen”. |
| 1.3 | The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). | 🟢 | No strengthening or softening; contraindication qualifiers (5 years, past 3 months, Child-Pugh C, eGFR <30) match the ER exactly. |
| 1.4 | The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. | 🟢 | No cross-category relabelling. Benefit- and Risk-Modifying Factors are not surfaced as gates; gates come only from the ER’s own contraindication and interaction lists. |
| 1.5 | PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. | 🟢 | No PMIDs, study names, years or NCT identifiers appear. Every named agent (ciclosporin, Epitalon, Cerebrolysin, warfarin, omeprazole, etc.) appears in the ER for the same fact. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions introduced. |
2. Focus, Tone & Audience
| # | Description | Result | Comments |
|---|---|---|---|
| 2.1 | The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. | 🟢 | Matches the ER’s deflationary, evidence-state-first register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Objective and data-driven; empowerment is delivered by making the evidence gap explicit and supplying a full monitoring frame rather than by encouragement language. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence state; no prescriptive instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No advice framing; targets and cadence are presented as reference points, mirroring the ER. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommend”, “advise” or “guidance” language anywhere in the sheet. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address; marker_5_target uses “the individual’s own baseline”. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are either plain-language in At-A-Glance or standard clinical names in the Monitoring table. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every item is a stripped noun phrase; rationales and citations removed throughout. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No direct address to the reader. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Framing assumes a proactive, risk-aware self-experimenter (sourcing risk, self-injection, self-tracking). |
| 2.11 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Protocol, monitoring cadence and qualitative logging all assume willingness to follow an effortful regimen. |
| 2.12 | The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Not written for a general audience; assumes engagement with an unapproved research-chemical peptide. |
| 2.13 | Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. | 🟢 | Risk/benefit weighting is audience-appropriate: supply-chain risk and attribution problems are foregrounded. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. | 🟢 | “anti-aging” does not appear. |
| 2.15 | The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Formal register throughout; “pins-and-needles” and “cells in a dish” are ER-verbatim and, in At-A-Glance, required by 7.4. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All fixed headings, gate headings, tier labels and Monitoring column headers are byte-identical to the template. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template span names present; marker_#* expanded to marker_1..6 and qualitative_item# to qualitative_item_1..5. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Structural diff against the template shows changes confined to variable regions; CSS, footer and the website=”evidence_review” / “audit” / “full_review” spans are untouched. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” | N/A | No ER section mapped into the QRS is empty. The unpopulated Benefits/Risks High and Medium tiers are governed by 12.5 / 13.5 (display:none), not by empty-state phrasing. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | Bold ER labels reproduced verbatim: “Circulating human protocol”, “Published animal course”, “Time of day”, “Persistence of effect”, “Time to effect”, “Half-life”, and all seven interaction labels including their (monitor)/(caution) qualifiers. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label paraphrased or invented. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present in the file. |
| 4.5 | The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. | 🟢 | Budget is tight but within one A4: At-A-Glance held to 55 words, contraindication rationales stripped, the ER’s four-column monitoring table condensed to three. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Metadata comment is at line 2, immediately after <!doctype html>. |
| 5.2 | Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. | 🟢 | YAML opened at line 3 and closed at line 13; the title text before it is outside the block. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | Inside an HTML comment; not rendered and not duplicated elsewhere. |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | All values trimmed; only duration is quoted, correctly, because “00:03” contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: cortagen_2026-0831-2215_Opus_ER.md |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | qrs_prompt_version: 26.7.02 matches the QRS.md version badge. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | qrs_creation_date: 2026-0831-2319, correct YYYY-MMDD-HHMM form. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | qrs_creator_ai_nickname: Opus |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | Single word, no version. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | qrs_creator_ai_fullname: Opus 5 |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | Nickname plus version number, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches the file on disk. |
| 5.13 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Confirmed alongside 5.4. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | “Cortagen for Health & Longevity - Quick Reference Sheet”; ampersand entity-encoded. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | “Cortagen for Health & Longevity” matches canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 08/31/2026 correctly derived from qrs_creation_date 2026-0831. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | “Opus 5” |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | No badge, alternate-names line, version stamp or variant marker; header carries only the template elements. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion into what the compound is, what its founding claim rests on, the state of safety data, and the conflict of interest. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 55 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Four sentences map to four distinct Conclusion passages. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “four-amino-acid peptide”, “cells in a dish”, “which genes a cell reads” used in place of tetrapeptide, in vitro and transcription. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years or sample sizes. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes or statistics. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All eight items come from the ER’s “Populations who should avoid Cortagen” list. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All eight ER contraindications represented, in ER order. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Eight <li> elements inside the stop_items span. |
| 8.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | Trailing rationales stripped, e.g. “since no reproductive or developmental toxicology has ever been published” and “given untested effects on chromatin decondensation”. No dash-trailing clauses remain. |
| 8.5 | Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Thresholds and windows preserved and compressed into parentheses: “(eGFR below 30 mL/min/1.73 m²)”, “(Child-Pugh Class C)”, “within the last 5 years”, “within the past 3 months”. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation inside parentheses in its contraindication list. |
| 8.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. |
🟢 | Section is populated; the ER does identify populations that should avoid the intervention. |
| 8.8 | If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | Section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items come from the ER’s Key Interactions & Contraindications bullets. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All seven ER interactions present; none duplicates a contraindication (the immunosuppressant interaction is distinct from the transplant-recipient population gate). |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Seven <li> elements inside the caution_items span. |
| 9.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | Mechanistic rationale and consequence/mitigation clauses stripped from every bullet; only label plus agent list retained. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Every named example drug preserved, including all three anticoagulants, all four transporter substrates and all four OTC agents. |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation inside parentheses in its interaction list. |
| 9.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. |
🟢 | Section is populated; the ER does identify interactions. |
| 9.8 | If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three action cells trace to ER Protocol bullets. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Covers the human dose, the only published (animal) course, and dosing time — the three implementation aspects the ER Protocol section actually specifies; remaining bullets are comparative or absent-data. |
| 10.3 | If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | Three distinct actionable aspects exist and all three sets are used. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine action fields carry ER-derived content. |
11. Time to Effect
| # | Description | Result | Comments |
|---|---|---|---|
| 11.1 | The three sets of [time] items cover the three most important time-to-effect aspects from the ER | 🟢 | Persistence of effect, time to effect and half-life are the ER’s three time-related findings. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by magnitude of related benefit: persistence attaches to nerve recovery (the sole Low-tier benefit), then the unestablished human time course, then half-life, which attaches to no benefit. |
| 11.3 | If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | Three distinct time-to-effect aspects exist and all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields carry ER-derived content. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER does provide time-to-effect information, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Items match the ER Expected Benefits headings. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier spans present. |
| 12.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Items reduced to bare headings; the ER’s magnitude figures (27% fibre growth, 40% conduction velocity) correctly omitted. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content carried through. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | benefits_high and benefits_medium carry style=”display: none”; no empty-state phrasing inserted. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Items match the ER Potential Risks & Side Effects headings. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier spans present. |
| 13.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Items reduced to bare headings; the purity, endotoxin and fold-change figures correctly omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content carried through. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | risks_high and risks_medium carry style=”display: none”; no empty-state phrasing inserted. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER Monitoring Protocol table. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six ER biomarkers present with their optimal ranges and rationales. |
| 14.3 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. |
🟢 | Cadence populated with baseline, end of first course (day 10 to 20), 3 months, 6 to 12 months, and functional measures at 3 and 6 months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Items come from the ER’s qualitative marker list in Monitoring Protocol & Defining Success. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers present. |
Issues 31/08/2026 23:41
Pass rate 100.00%. No issues found.
Issues 31/08/2026 23:35
- 2.8 / 4.5 — Protocol and time cells carry ER-length prose: All six
subcells in the two protocol grid rows (lines 455-458, 469-472, 483-486, 503-506, 517-520, 531-534) run two full sentences each in a one-third-width 8.5pt cell, driving each grid row to roughly four rendered lines and pushing the panel well past its share of the one-page budget. - 2.8 / 4.5 — Monitoring cadence runs three sentences: [monitoring_cadence] (lines 751-755) reproduces the ER’s cadence paragraph almost in full rather than condensing it to the compact single-line annotation the template’s cadence row is sized for.
- 4.5 — Key Interactions gate over the per-section budget: [caution_items] (lines 584-612) renders to roughly sixteen lines at 9.5pt in a 92mm gate column, chiefly because the peptide-transporter and over-the-counter entries carry connective wording (“cephalosporin antibiotics”, “no interaction documented with”) that can be trimmed without dropping any named drug.
Fixes 31/08/2026 23:35
- 2.8 / 4.5 — Protocol and time sub cells condensed: All six
subcells were tightened from two full sentences to one compact annotation each (e.g. action_1_sub from “10 to 20 days, repeated two to four times yearly. Vendor and practitioner figures that rest on convention, not published study.” to “10 to 20 days, two to four times yearly. Convention, not published study.”), cutting roughly one rendered line from each protocol grid row. - 2.8 / 4.5 — Monitoring cadence tightened: [monitoring_cadence] was reduced from the ER’s three-sentence paragraph to a compact cadence line, dropping “roughly”, “repeated” and “Functional measures repeat only at” while keeping every interval and both measure types.
- 4.5 — Key Interactions entries trimmed: The peptide-transporter entry dropped the class descriptor (“cephalosporin antibiotics (cefadroxil, cephalexin)” to “cefadroxil, cephalexin”) and the over-the-counter entry dropped connective wording (“no interaction documented with” to “none documented with”); every named drug and the “oral” route qualifier were retained.
Issues 31/08/2026 23:28
- 11.2 — Time-to-effect sets not ordered by benefit: The three time cells run time to effect → persistence of effect → half-life (QRS lines 495–536), a generic pharmacology sequence rather than an ordering by the magnitude of the related benefit; the only benefit-linked cell, “Persistence of effect”, sits behind a null cell with no benefit attached.
Fixes 31/08/2026 23:28
- 11.2 — Time cells reordered by benefit: Swapped the first two time-to-effect cells so “Persistence of effect / Outlasts the course, in rats” — the only cell tied to the ER’s highest-tier benefit — leads, followed by “Time to effect / Not established in humans”; “Half-life” remains last.