Audit: QRS - Ivermectin to Treat Cancer

Audit conducted on 27/09/2026 19:00 using AI4L + evidence-mcp / GPT 6

Iterations

Summary

Items Count
Total 94
Passed 89
Failed 0
N/A 5
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. 🟢 Claims map to the named ER’s Conclusion, Therapeutic Protocol, benefits, risks, interactions, and monitoring sections.
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. 🟢 Preserves unestablished cancer efficacy, safety uncertainty, theoretical supplement interactions, and unvalidated monitoring cadence.
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”). 🟢 Research doses remain expressly unestablished regimens; trial eligibility remains distinguished from universal safety limits.
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. 🟢 Benefit and risk tiers, contraindications, and interaction categories follow their respective ER sections.
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. 🟢 ICONIC and the breast-cancer trial refer to the same protocol facts as the ER; no new study identifiers, experts, or brands.
1.6 The QRS does not introduce new attributions. 🟢 No additional source attribution 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. 🟢 Retains the ER’s cautious assessment of investigational cancer use.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Compact factual explanation supports informed understanding without overstating efficacy.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents research status and monitoring context without an individualized treatment prescription.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Dose examples are explicitly research schedules, not established cancer regimens.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Describes evidence, protocol administration, and uncertainty.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Variable content does not address the reader directly; fixed template disclaimer is preserved.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Uses plain descriptions; technical enzyme, laboratory, and condition names retain necessary identification for decision gates.
2.8 Information is presented in a concise and very compact manner 🟢 Short protocol cells, tier lists, compact gates, and monitoring rows.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address in populated variables.
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. 🟢 Emphasizes implementation evidence, medication interactions, and risk awareness for proactive adults.
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. 🟢 Includes research schedules, laboratory monitoring, and structured symptom tracking.
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. 🟢 Retains detailed protocol eligibility and monitoring relevant to the specified audience.
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. 🟢 Separates exploratory cancer use from established parasite treatment and identifies attribution limits.
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. 🟢 No anti-aging framing.
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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. 🟢 Uses oral administration, dose, regimen, and clinical adverse-effect terminology.

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 specified headings, tiers, and monitoring column headings are unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Every template data-qrs-var anchor is present, including hidden unused spans.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Website integration spans and other unassigned template content remain unchanged.

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” 🟢 Empty benefit tiers use the specific hiding requirement in 12.5; no substitute empty-state prose is introduced.
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. 🟢 Protocol, time-to-effect, gate, and qualitative bold labels preserve the ER labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Displayed labels derive from the ER or fixed template.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators in the QRS.
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. 🟢 Source defines A4 print size, compact print typography, narrow margins, and block break avoidance; content is condensed into a single-sheet design.

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 immediately follows the doctype.
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. 🟢 One opening and one closing YAML delimiter within the metadata comment.
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. 🟢 Metadata remains in an HTML comment; permitted date and creator fields appear in their prescribed header locations.
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. 🟢 Values are trimmed; duration quoting is justified by its colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Names ivermectin_cancer_2026-0927-1732_GPT_ER.md, resolved to the exact staging source supplied by the workflow.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Matches QRS.md version 26.9.27.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 Creation timestamp 2026-0927-1857 follows the required format.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Creator nickname field is present.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT is one word without a 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]” 🟢 Creator fullname is GPT 6.
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) 🟢 Fullname consists of nickname plus model version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Metadata filename matches the audited creation-directory file.
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. 🟢 Trimmed fields; only colon-containing duration is quoted.

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., &amp; for &) 🟢 Title equals canonical topic plus the prescribed suffix.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Header topic equals Ivermectin to Treat Cancer.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 matches the creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model equals GPT 6.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only prescribed template header content appears.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opens by identifying a medicine for parasitic infections being researched for cancer.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the Conclusion’s efficacy, sustained-use safety, treatment-displacement, and validation limitations.
7.3 [at_a_glance] is no longer than 70 words 🟢 64 words by whitespace count.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each factual clause maps to a distinct statement in the ER Conclusion or intervention description.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No specialist acronyms or classifications in the summary.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, dates, sample sizes, or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistical results.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six gates derive from Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Preserves every listed avoidance population and trial eligibility scenario.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each gate is an li element.
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. 🟢 Compact key facts; protocol context and the safety-cutoff distinction are necessary qualifiers to the numerical gates.
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). 🟢 Preserves pregnancy/breastfeeding, high parasite burden, kidney/liver thresholds, liver-metastasis condition, Gilbert exception, and weight limit.
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. 🟢 No severity-ranking shorthand occurs; greater-than signs express laboratory thresholds.
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 because the ER specifies avoidance populations.
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 interactions derive from Key Interactions & Contraindications.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Includes the eight ER interaction categories without duplicating contraindication entries.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each interaction is an li element.
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. 🟢 Compact interaction labels and identifying examples; retained em-dashes are within verbatim ER labels, not appended explanatory clauses.
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). 🟢 Preserves named inhibitors, inducers, sedatives, supplements, recent-use exclusion intervals, and theoretical status.
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. 🟢 No ranking notation requiring normalization.
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 because the ER identifies 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 action content derives from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers regimen validation, quantified research dosing and schedule, and administration/food.
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 At least three distinct implementation aspects exist and all three slots 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 used action spans contain meaningful ER-derived material.

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 🟢 Captures the ER’s single time-to-effect assessment and distinguishes subjective/cohort observation from a reliable timetable.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 The sole populated set prioritizes tumor and survival outcomes.
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. 🟢 Two unused sets remain empty and their parent cells are hidden by CSS.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 The populated label, value, and subtext derive from Practical Considerations: Time to effect.
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 provides a time-to-effect assessment, so the section remains.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Includes the ER High parasite-control benefit and all three Low cancer-related benefit headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four specified benefit spans remain 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. 🟢 Only concise benefit descriptors; no study details or numerical magnitudes.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical explanatory content retained.
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. 🟢 Medium and Speculative tiers are hidden without empty-state text.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Risk descriptors and evidence tiers match Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk spans remain 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. 🟢 Only risk descriptors; no study details, frequencies, or explanatory clauses.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical detail retained.
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. N/A Every risk tier has ER items; none requires hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 Includes all eight table biomarkers plus blood pressure from the monitoring narrative; blood-count components remain identified.
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. 🟢 Includes baseline, 1–2 weeks, cycle-based reassessment, new symptoms, imaging, pregnancy retesting, and anticoagulation-service checks, with pragmatic status retained.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All qualitative material derives from the ER Monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Includes function/alertness, each symptom and quality-of-life domain, and dated attribution records.

Issues 27/09/2026 19:00

Pass rate 100.00%. No issues found.