Audit: QRS - Molybdenum for Health & Longevity

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

Iterations

Summary

Items Count
Total 94
Passed 90
Failed 0
N/A 4
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. 🟢 Compared every populated region with the named ER: conclusion, protocol, benefits, risks, interactions, and monitoring support the content.
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. 🟢 Unproven longevity benefit, theoretical interactions, absent validated targets, and proposed cadence retain the ER uncertainty.
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”). 🟢 Nutritional requirements are distinguished from longevity doses; laboratory effects are distinguished from clinical benefits.
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. 🟢 Benefits, adverse outcomes, contraindications, interactions, and protocol remain in their corresponding ER categories.
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 study identifiers, expert attributions, or brands are introduced; interaction drug examples are present in the ER.
1.6 The QRS does not introduce new attributions. 🟢 No new source or expert attribution appears.

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. 🟢 The evidence-focused tone matches the source ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Clear discussion of adequacy, uncertainty, and measurable outcomes is objective and usable.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 The sheet describes evidence, amounts, and limitations without prescribing a longevity regimen.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Protocol amounts are explicitly nutritional; the source template disclaimer remains.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Descriptive entries present the ER information.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Populated content does not address a reader directly.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain outcome names, expanded kidney marker name, and micrograms avoid unnecessary abbreviations.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cells, tier lists, and a six-row monitoring table condense the ER.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address in generated content.
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. 🟢 Longevity optimization and experimental-use monitoring are explicit.
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. 🟢 Laboratory monitoring and individualized assessment remain visible.
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. 🟢 The sheet addresses deliberate longevity experimentation, not general-population reluctance.
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. 🟢 Adequacy versus added benefit, uncertainty, and relevant safety factors reflect proactive use.
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. 🟢 Longevity terminology is used throughout.
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. 🟢 Formal terms such as oral, intravenous nutrition, and formulation are retained.

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 listed fixed headings, tier labels, and monitoring headers are unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Every template data-qrs-var anchor is retained, including hidden third time set and expandable marker/qualitative anchors.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Only checklist-addressed content spans are populated; website placeholders 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” 🟢 No contradictory empty-state wording is introduced; empty High tiers are hidden as specifically required.
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 and qualitative labels preserve ER bold labels; interaction decision suffixes are stripped under item 9.4.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels match corresponding ER labels, outcome headings, or biomarker row names.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators occur in the sheet.
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. 🟢 A4 print rules explicitly compact margins, fonts, spacing, gates, and protocol columns; source is designed for one page.

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. 🟢 The 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. 🟢 The metadata comment contains opening and closing YAML delimiters.
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 inside the comment; the designated date and creator fields appear only where required in the header.
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; the quoted duration contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename matches the source ER basename.
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 matches 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 uses YYYY-MMDD-HHMM.
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 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 a single model nickname.
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 is present.
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) 🟢 GPT 6 comprises nickname and version without qualifiers.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the audited basename.
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. 🟢 No padded values or unnecessary quotes occur.

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 uses the canonical topic plus the required suffix and encodes the ampersand.
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 matches the canonical topic with HTML encoding.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 corresponds to qrs_creation_date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model matches 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. 🟢 No additional populated header badges or variant markers appear.

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 🟢 Opening identifies an essential dietary mineral used in supplements for normal body processes.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Summarizes adequacy, uncertain additional benefit, food-study signal, absent effective dose, and safety factors from the conclusion.
7.3 [at_a_glance] is no longer than 70 words 🟢 The at-a-glance paragraph is within the 70-word limit.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each factual component maps to the ER conclusion and introductory mineral description.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications appear in the lede.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes, or p-values appear.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numerical effect estimates or statistical results appear.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 The four contraindications come from the ER populations-to-avoid list.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Formulation allergy, copper deficiency, kidney impairment/dialysis, and reproductive settings are included.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each contraindication 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. 🟢 Only the condition and scope qualifiers 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). 🟢 Specific product, discretionary intake, advanced impairment, unsupervised intake, and experimental high-dose qualifiers are retained.
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 unexplained severity-ranking notation is carried over.
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. 🟢 The section is populated because the ER names avoidance scenarios.
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 The contraindications section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six interaction entries originate in the ER interactions section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All six interaction classes are retained; contraindication scenarios remain separately scoped.
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. 🟢 Entries contain class labels and concise qualifying context without trailing 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). 🟢 Insulin, glipizide, gliclazide, copper-binding drugs, supplement types, and kidney/liver context are retained.
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 unexplained severity-ranking notation appears.
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. 🟢 The section is populated because interactions and additive exposures are described.
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 The interactions section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All action cells derive from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Nutritional amounts, administration timing, and individually prescribed deficiency replacement cover the central actionable distinctions.
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 The ER supplies at least three distinct implementation aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine populated action spans contain meaningful 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 🟢 Two timed glucose/bone laboratory aspects are supplied; the ER provides no quantified onset for clinical deficiency recovery or longevity.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 The Medium glucose outcome precedes the speculative bone outcome.
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. 🟢 The third time set is empty and its parent cell is hidden.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 The 12-day values and clinical-benefit caveats are supported by the ER.
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 time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Benefit entries and tiers match Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four named benefits spans are retained.
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. 🟢 Entries consist of condensed ER outcome headings without added explanations or numeric detail.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parenthetical study details and magnitude text are absent.
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. 🟢 The empty High tier is hidden with display: none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Risk entries and tiers match Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four named risks spans are retained.
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. 🟢 Entries consist of outcome headings without added mechanisms or numerical detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical study details or severity/frequency descriptions remain.
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. 🟢 The empty High tier is hidden with display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 All monitoring rows and the cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six ER biomarkers are listed with baseline/target limitations.
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 retains no validated schedule, proposed 2–4 weeks and 3–6 months, earlier symptom review, and routine-screening limitation.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Both qualitative entries derive from the ER monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Energy, intestinal symptoms, sleep, function, concurrent changes, joint pain, swelling, abdominal pain, neurological symptoms, and reproductive concerns are present.

Issues 27/09/2026 17:18

Pass rate 100.00%. No issues found.

Issues 27/09/2026 17:15

  1. 11.3 — Unused timing cell populated: The Time to effect panel fills time_3_value with “No measured onset” for healthy-life extension. The ER supplies no onset for this outcome, so this timing set should be empty and hidden.

Fixes 27/09/2026 17:15

  1. 11.3 — Unused timing cell hidden: Cleared the healthy-life-extension label, value, and supporting text, and hid the third timing cell while retaining all three template spans.