Audit: QRS - Abaloparatide for Health & Longevity

Audit conducted on 13/08/2026 13:11 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.	🟢	Protocol, time-to-effect, benefit/risk tiers, contraindications, interactions, all 11 markers, cadence and all 6 qualitative items trace verbatim or near-verbatim to ER lines 167–203, 241–303, 329–356, 382–394, 440, 470–493.
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.	🟢	No cautious ER phrasing is restated more firmly; speculative items are carried in the Speculative tier as the ER classifies them.
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”).	🟢	Pregnancy/breastfeeding, 24-month cumulative cap and eGFR<30 remain in the Contraindications gate at ER strength.
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.	🟢	All 10 caution items come from the ER Key Interactions & Contraindications bullets; no Benefit- or Risk-Modifying Factor is promoted into a gate.
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, expert names or brand names appear anywhere in the QRS; only generic drug names that the ER itself uses.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

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.	🟢	At-a-glance mirrors the ER Conclusion’s measured, caveat-carrying register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Concrete, decision-enabling content presented without hedging or alarm.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as evidence and parameters, not instructions to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive constructions; protocol and monitoring cells are descriptive.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrences of “should”, “recommend”, “advise” or equivalents in the rendered text.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms that remain are biomarker names, drug names and named conditions carried verbatim from the ER; the at-a-glance is fully plain-language.
2.8	Information is presented in a concise and very compact manner	🟢	Every gate, tier and marker entry is a stripped fact; explanations and mechanisms from the ER are removed.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address in any span.
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 reader evaluating a full 18–24 month course and its mandatory follow-on.
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.	🟢	Daily injection, site rotation and sequential therapy are presented without softening the burden.
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.	🟢	Density of biomarker targets and sequencing detail is pitched above general-population material.
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.	🟢	At-a-glance surfaces both the durability condition and the sponsor-funding caveat rather than a headline benefit alone.
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” string appears; the title uses “Health & Longevity”.
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.	🟢	“injection”, “administration site reactions”, “orthostatic hypotension”, “antiresorptive” used throughout; no consumer-grade substitutes.

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 match the template byte-for-byte (lines 440, 477, 519, 539, 552, 574, 593, 597–599, 734).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template spans present; marker_#* expanded to marker_1..11 and qualitative_item# to qualitative_item_1..6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website="…" spans and the entire style block are byte-identical to the 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 mapped 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.	🟢	“Standard dose”, “Sequencing approach”, “Time of day” reproduce the ER Protocol bold labels verbatim (ER lines 382, 384, 390).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit and risk items reproduce the ER #### headings; time-to-effect labels use the ER’s own noun phrases from line 440.
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” marker on the palpitations heading is correctly dropped.
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.	🟢	Condensation applied throughout — glosses, mechanisms and trailing clauses stripped from gates, tiers reduced to bare headings; no section carries ER prose.

---

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 <!doctype html> on line 1.
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.	🟢	Enclosed in an HTML comment; no metadata value is repeated in the header or footer.
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 because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: abaloparatide_2026-0813-1058_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]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md badge.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	Line 6: qrs_creation_date: 2026-0813-1302.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: 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)	🟢	“Opus” — 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]”	🟢	Line 8: 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)	🟢	“Opus 5” — nickname plus version only.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the on-disk filename exactly.
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 across all nine keys.

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 &)	🟢	Line 22: “Abaloparatide 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., & for &)	🟢	Line 417: “Abaloparatide for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/13/2026”, matching qrs_creation_date 2026-0813-1302.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “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.	🟢	Header block (lines 415–428) is structurally identical to the template.

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 519 and 523: mechanism, fracture and density outcomes, the durability condition, and the sponsorship caveat.
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 sentence in the ER Conclusion (lines 519, 523).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“bone-preserving drug” replaces “antiresorptive”; no acronyms or drug-class names appear.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year or sample size is mentioned.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Uses “sharply”, “substantially”, “at every site measured” instead of numbers.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items map to the “Populations who should avoid abaloparatide” list at ER lines 351–356.
8.2	[stop_items] represent the Contraindications from the ER	🟢	6 ER bullets → 6 QRS items, none added, none dropped.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 542–547, each item its own <li>.
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.	🟢	ER trailing clauses “where calcium and peptide handling are unpredictable and unstudied”, “in whom the drug has not been studied” and “— the sole absolute contraindication in the label” are all stripped.
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).	🟢	“(within the past 12 months)”, “(below 30 mL/min/1.73 m²)”, “(counting teriparatide)” and the osteosarcoma-risk condition list 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 names six 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	🟢	All ten items map to ER lines 329–347.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	10 ER interaction bullets → 10 QRS items, with no overlap against the Contraindications gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 555–564.
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 mechanistic rationale (“Rising serum calcium potentiates digitalis effect…”) and monitoring instructions are 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).	🟢	Named example drugs retained for thiazides, antihypertensives/nitrates and antiresorptives; the ~1,000 mg calcium threshold 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.	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 names ten 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	🟢	All three cells derive from the ER Therapeutic Protocol bullets at lines 382, 384 and 390.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, sequencing and dosing time — the three parameters that determine execution; baseline biomarkers are already carried by the Monitoring card.
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 provides more than three actionable aspects; 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 spans populated with ER-derived content (lines 444–473).

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	🟢	Fracture protection, bone density and bone formation markers — the three horizons named in ER line 440.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Fracture protection and BMD gain are High-tier benefits; rapid anabolic onset is Low-tier and placed last.
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 names three distinct time-to-effect aspects; 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 spans populated from ER lines 201, 203 and 440.
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 (line 440).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All eight items reproduce the ER #### benefit headings at lines 165–213.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated (lines 521–532).
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.	🟢	Every Magnitude paragraph, PubMed link and mechanistic sentence from the ER is dropped; only the headings remain.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit item.
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 contain items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All ten items reproduce the ER #### risk headings at lines 241–303.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated (lines 576–587).
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.	🟢	Frequencies (70.5%, 10.0% vs 6.1%, 7.9 bpm) and mechanisms are all stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risk item.
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 contain items in the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Marker, Target and Why columns reproduce the ER biomarker table at lines 472–484.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER table rows present as marker_1 through marker_11, with targets and rationales verbatim.
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.	🟢	Line 728 reproduces the cadence sentence from ER line 470.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from the “Qualitative markers worth tracking alongside the labs” list at ER lines 488–493.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present as qualitative_item_1 through qualitative_item_6.

Issues 13/08/2026 13:11

Pass rate 100.00%. No issues found.