Audit: QRS - Zoledronate for Health & Longevity

Audit conducted on 15/09/2026 15:57 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
Failed 0
N/A 10
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. 🟢 All protocol, time-to-effect, benefit, risk, gate, marker and qualitative content traces to ER lines 251–461.
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. 🟢 ER uncertainty on mortality/cancer/cardiac signals is carried in the lede (“remain far less certain”) and by the Low/Speculative tiers.
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”). 🟢 Contraindications retain absolute framing; thresholds (35 mL/min, 20 ng/mL, 12 months) unchanged.
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. 🟢 Gates draw only from ER Key Interactions & Contraindications; tiers only from Expected Benefits / Potential Risks & Side Effects.
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, NCT IDs, author names or brand names (Reclast/Aclasta/Zometa) present.
1.6 The QRS does not introduce new attributions. 🟢 No attributions anywhere in the sheet.

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. 🟢 Lede and tier items reuse ER Conclusion and heading wording.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢  
2.4 The QRS avoids language that implies medical or clinical advice 🟢 All protocol and monitoring cells are stated descriptively, not as instructions.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “should”, “must”, “recommended” or “advised” in document voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns present.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are the ER’s own and are necessary to the fact.
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢 Verified: no “you”/”your”.
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. 🟢  
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. 🟢 Infusion logistics, dental clearance and repletion prerequisites are surfaced without softening.
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. 🟢  
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. 🟢 Lede separates the well-established skeletal case from the uncertain longevity signals.
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)”; “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. 🟢 Route of administration is stated as “infusion”/”intravenously” throughout, including the lede.

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 strings byte-identical to the template.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variables present; marker_#/qualitative_item_# rows expanded to 9 and 7 instances.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Head, CSS, website="evidence_review"/"audit"/"full_review" spans and footer disclaimer identical to template.

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 source ER section used by the QRS is empty.
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 labels and interaction labels match the ER bold labels; monitoring rows match the ER table’s biomarker names.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Time-to-effect labels are derived from the ER’s single Time to effect bullet, which carries no per-item bold labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s “⚠️ Conflicted” markers were stripped.
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. 🟢 Every item is condensed to a single short clause; item counts are those mandated by 9.2, 14.2 and 15.2.

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. 🟢 Lines 2–14, immediately after 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. 🟢 Opening --- line 3, closing --- line 13.
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. 🟢 Fully enclosed in an HTML comment.
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. 🟢 Only duration: "00:03" is quoted, correctly so (contains a colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: zoledronate_2026-0915-1303_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]” 🟢 26.9.11, matching QRS.md.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 2026-0915-1535
5.8 The nickname of the AI used to create the document is stated as “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) 🟢  
5.10 The full name of the AI used to create the document is stated as “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) 🟢 No qualifier appended.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 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. 🟢  

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 &) 🟢 “Zoledronate for Health & Longevity - Quick Reference Sheet”
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Zoledronate for Health & Longevity”
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0915 → 09/15/2026
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. 🟢 Subline is exactly the template’s. The ER’s alternate-names line is not carried over.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses ER lines 479–485.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion paragraph.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Paget’s disease rendered as “a disorder of runaway bone rebuilding”; no acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢  

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Maps to ER lines 323–331.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 7 ER “Populations who should avoid” entries present.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Seven <li> elements.
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. 🟢 “since the time to fracture benefit exceeds it” correctly stripped from the life-expectancy item.
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). 🟢 35 mL/min, 20 ng/mL, one year, three months and 12 months all 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. N/A The ER uses no ranking notation in this section.
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 ER does identify such populations and the section is correctly populated.
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 section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Maps to ER lines 303–321.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 9 of the ER’s 10 interaction bullets; “Other antiresorptive drugs” correctly excluded as it is already a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <li> elements.
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. 🟢 All mechanism and mitigation text stripped.
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 ER example drug list retained; only redundant glosses (“fluid-clearing drugs”, “iodinated”) trimmed.
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 in this section.
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 ER identifies interactions and the section is correctly populated.
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 section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Maps to ER Therapeutic Protocol, lines 351–377.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard regimen, extended-interval regimen and the single-dose administration rule.
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 more than three; 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 cells populated from ER lines 353, 355, 363 and 367.

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 🟢 All three aspects of ER line 409 are carried.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Fracture prevention (High-tier benefit) first, then bone density, then turnover markers.
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 The ER supplies three; 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 cells populated.
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.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Maps to ER lines 133–207.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four populated.
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. 🟢 Each item is the ER benefit heading alone; all Magnitude text omitted.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried over.
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. N/A All four tiers have items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Maps to ER lines 223–285.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four populated.
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. 🟢 Each item is the ER risk heading alone; “⚠️ Conflicted” and all frequencies omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried over.
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 All four tiers have items in the ER.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Maps to ER Monitoring Protocol & Defining Success, lines 435–451.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 9 rows of the ER biomarker table present with matching targets 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. 🟢 Condenses ER line 439 in full.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Maps to ER lines 453–461.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 7 ER qualitative bullets present.

Issues 15/09/2026 15:57

Pass rate 100.00%. No issues found.

Issues 15/09/2026 15:51

  1. 4.3 — Biomarker label abbreviated: [marker_9_name] at line 729 reads “Bone mineral density T-score, total hip and spine”, abbreviating the ER’s row label “Bone mineral density T-score, total hip and lumbar spine” (ER line 451).

Fixes 15/09/2026 15:51

  1. 4.3 — Biomarker label abbreviated: Restored the ER’s full row label in [marker_9_name], changing “Bone mineral density T-score, total hip and spine” to “Bone mineral density T-score, total hip and lumbar spine”.

Issues 15/09/2026 15:43

  1. 4.5 — Sheet overflows one A4 page: At the file’s own print rule (A4 with 12mm padding, ≈1032px usable height) the populated sheet renders to roughly 2050px, about two pages; Monitoring (lines 634–755), the gates block (lines 565–601) and Qualitative Assessment (lines 758–802) account for most of the excess.
  2. 2.8 — Cells carry unabridged ER prose: Qualitative items 1, 2, 3, 6 and 7 (lines 762–799) and several Monitoring “Why” cells (lines 664–719) reproduce full ER sentences with trailing rationale clauses, wrapping to two lines where one would carry the fact.

Fixes 15/09/2026 15:43

  1. 2.8 — Qualitative items trimmed to the observable: Stripped the trailing rationale clauses from qualitative items 1, 2, 3, 6 and 7 (e.g. “…of any duration, which is treated as an atypical femoral fracture prodrome until imaging excludes it” became “…of any duration”), leaving the marker itself.
  2. 2.8 — Monitoring “Why” cells shortened: Condensed the rationale cells for markers 2 through 7 (e.g. “The single strongest predictor of avoidable hypocalcaemia” to “Strongest predictor of avoidable hypocalcaemia”; “parathyroid hormone” to “PTH”) so each fits a single rendered line.
  3. 4.5 — Monitoring row width reduced: Shortened marker 9’s name from “Bone mineral density T-score, total hip and lumbar spine” to “…total hip and spine” and its target from “Improvement or stability from the individual’s own baseline” to “Improvement or stability from own baseline”.
  4. 4.5 — Cadence sentence compressed: Rewrote the monitoring cadence to “…10 to 14 days after the first infusion, then before each subsequent one… a bone turnover marker at 3 months and again when the next interval is decided; bone density scan every 2 to 3 years”, dropping a rendered line while keeping every interval.
  5. 4.5 — Decision-gate items tightened: Trimmed redundant wording in the Contraindications and Key Interactions lists (“acute kidney injury of any cause” to “acute kidney injury”; “iodinated contrast media” to “contrast media”; “within the next three months” to “within three months”), preserving every threshold, time window and named drug.
  6. 4.5 — Protocol and time-to-effect subtexts condensed: Shortened action 2 and action 3 subtexts and replaced time 1’s subtext with “One non-vertebral fracture avoided per 100 treated women”, since the “~12 months” figure already sits in the value cell above it.