Audit: QRS - IGF-1 LR3 for Health & Longevity

Audit conducted on 02/10/2026 06:02 using AI4L / Opus 5.5

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.	🟢	All protocol, time-to-effect, tier, gate, monitoring and qualitative entries trace to ER passages (Protocol, Expected Benefits, Potential Risks, Key Interactions, Monitoring, Practical Considerations, Conclusion).
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 caution preserved: “theoretical” on every interaction, “not validated or safe” (action_2_sub), “unknown for IGF-1 LR3 in humans” (time_1_sub), “no human time course exists” (time_3_sub), “by common practice” in 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”).	🟢	No claim strengthened or softened; contraindications kept as avoid-populations; forum regimen kept as unvalidated.
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.	🟢	Contraindications come from “Populations who should avoid”, interactions from the interaction bullets, qualitative items from the Monitoring list; no category relabelling.
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, NCT numbers, expert names or brand names (e.g., INCRELEX) appear.
1.6	The QRS does not introduce new attributions.	🟢	No new 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.	🟢	Cautious, evidence-separating tone of the ER (analogue vs native hormone) is mirrored.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven while staying factual and non-alarmist.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence; no prescriptive instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No language implying medical advice; dosing cells framed as sourced reference / circulating regimen.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Information is presented, not recommended.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct reader address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language used; remaining technical terms are verbatim ER labels with glosses where the ER provides them (e.g., “Closed epiphyses (fused growth plates)”).
2.8	Information is presented in a concise and very compact manner	🟢	Compact single-line items and short cells.
2.9	It DOES NOT address the reader directly	🟢	No “you”/imperative 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.	🟢	Content suits risk-aware, proactive adults (contraindications, monitoring, cadence).
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.	🟢	Monitoring cadence and protocol details assume an engaged audience.
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-population 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.	🟢	At-a-glance flags that mid-range adults face a push away from the lowest-risk middle, matching the audience-specific weighting in the ER Conclusion.
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” wording; framed in longevity terms.
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 route and event terminology (“subcutaneous”, “intramuscular”, “injection-site reactions”); no colloquial terms such as “shot” or “pill”.

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 Marker/Target/Why headers unchanged (lines 440, 477, 519, 539, 552, 572, 591, 595-597, 644).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present: page_title, header_, at_a_glance, action_1-3, time_1-3, benefits_, stop_items, caution_items, risks_*, marker_1-3, monitoring_cadence, qualitative_item_1-5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-variable spans (website=”evidence_review”, “audit”, “full_review”) and static template text 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 ER tiers (High/Medium benefits and risks) are hidden per 12.5/13.5; no ER empty-state phrasing is altered.
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 use ER bold labels verbatim (“Only sourced dosing reference”, “What circulates instead”, “Best time of day”); interaction items use ER bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels are not paraphrased or invented; time labels use ER benefit headings verbatim.
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.	🟢	Content is condensed to single-line tier lists and compact gates consistent with a one-page budget.

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 the first element after “<!doctype html>” (line 2).
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 delimited by “—” lines (lines 3 and 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.	🟢	Metadata sits inside an HTML comment and is not surfaced.
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 trimmed; only duration is quoted, which contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: igf_1_lr3_2026-1002-0024_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.10.1 matches 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)	🟢	qrs_creation_date: 2026-1002-0545 in YYYY-MMDD-HHMM format.
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 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: Opus 5.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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: igf_1_lr3_2026-1002-0024_Opus_QRS.html matches the 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.	🟢	All values trimmed and correctly 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., & for &)	🟢	“IGF-1 LR3 for Health & Longevity - Quick Reference Sheet” (line 22).
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	“IGF-1 LR3 for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	10/02/2026 matches qrs_creation_date 2026-1002.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.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 extra header content.

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 with “a laboratory-made version of a natural growth signal sold as a research chemical for bodybuilding and longevity” before any evidence verdict.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion: no human study, animal/native-hormone evidence, U-shaped mortality, cancer link, push from the middle.
7.3	[at_a_glance] is no longer than 70 words	🟢	70 words.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each fact maps to Motivation or Conclusion passages of the ER.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms beyond the intervention name; plain terms (“low blood sugar”, “swelling”).
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trials cited.
7.7	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	🟢	Derived from ER Key Interactions & Contraindications (Populations who should avoid IGF-1 LR3).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER avoid-populations represented.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is an <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.	🟢	Trailing dash clauses and citations 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).	🟢	“(fused growth plates)” qualifier preserved.
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 ranking notation in the ER bullets.
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 correctly populated; the ER names populations to avoid.
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	🟢	Derived from ER Key Interactions & Contraindications.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight ER interaction bullets represented; none duplicate a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is an <li>.
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.	🟢	No mechanistic rationale, citations or dash 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).	🟢	Example drug lists and severity classes (“monitor/avoid/caution, theoretical”) preserved.
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 in the ER bullets.
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 correctly populated; the ER names 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	🟢	Derived from ER Therapeutic Protocol.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dosing reference, circulating regimen and timing cover the key actionable aspects of the ER protocol.
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 in the ER.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All action labels, values and subs filled from the ER Protocol.

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	🟢	Blood-sugar control (12 weeks), body-fat reduction (6 weeks) and gut mucosal growth (7-14 days) are the ER’s time-anchored benefit findings.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered Low-tier benefits first (blood sugar, body fat) then the Speculative gut finding.
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 in the ER.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All time labels, values and subs filled from 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	🟢	Derived from ER Expected Benefits.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	benefits_high, benefits_medium, benefits_low, benefits_speculative 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 are bare ER headings without qualifiers.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content.
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.	🟢	High and Medium spans set to display: none (lines 521, 524).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Derived from ER Potential Risks & Side Effects.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	risks_high, risks_medium, risks_low, risks_speculative 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 are bare ER headings without qualifiers.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content.
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.	🟢	High and Medium spans set to display: none (lines 574, 577).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from ER Monitoring Protocol & Defining Success.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All three ER table biomarkers listed (Serum IGF-1, Fasting plasma glucose, HbA1c).
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 from the ER Monitoring paragraph (baseline, pre-meal checks, periodic eye exam, 4-6 weeks then 3-6 months).

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from ER Monitoring section.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers listed.

Issues 02/10/2026 06:02

Pass rate 100.00%. No issues found.

Issues 02/10/2026 05:58

1. 1.2 / 1.3 — Mid-range push overstated: At a Glance (line 433) states “use pushes mid-range adults away from the lowest-risk middle” as fact and drops the ER Conclusion’s caveat “with no human measurement of where it lands”, strengthening the ER claim.

Fixes 02/10/2026 05:58

1. 1.2 / 1.3 — Mid-range push caveat restored: Replaced “use pushes mid-range adults away from the lowest-risk middle” with “for mid-range adults, evidence describes an unmeasured push away from the lowest-risk middle”, restoring the ER’s “no human measurement” caveat; tightened wording elsewhere to keep At a Glance at 70 words.

Issues 02/10/2026 05:55

1. 7.2 — Lede lacks execution takeaway: The at-a-glance (line 433) summarises the evidence but omits the ER Conclusion’s decision-relevant point (ER line 462) that for adults already mid-range, use pushes them away from the lowest-risk middle.

Fixes 02/10/2026 05:55

1. 7.2 — Lede lacks execution takeaway: Rewrote the at-a-glance to add the ER Conclusion’s takeaway (“use pushes mid-range adults away from the lowest-risk middle”) and compressed earlier phrasing (e.g., “has never been given to people in a study” to “has never been studied in people”) to stay within 70 words.

Issues 02/10/2026 05:51

1. 4.2 / 4.3 — Interaction label paraphrased: Key Interactions item at QRS line 560 reads “Supplements with additive glucose lowering”, but the ER bold label (ER line 311) is “Supplement interactions with additive glucose lowering”.

Fixes 02/10/2026 05:51

1. 4.2 / 4.3 — Interaction label restored verbatim: Changed the Key Interactions item label from “Supplements with additive glucose lowering” to the ER’s bold label “Supplement interactions with additive glucose lowering”.

Issues 02/10/2026 05:47

1. 1.2 — Cadence drops common-practice qualifier: The monitoring cadence (line 638) gives “IGF-1 and glycated haemoglobin at roughly 4–6 weeks, then every 3–6 months” without the ER’s qualifier “by common practice”, presenting an uncited parameter at the same weight as the label-derived checks.
2. 2.7 — Unexplained jargon in cadence: The monitoring cadence (line 638) uses “funduscopic examination” twice, although the ER glosses it as a “back-of-the-eye” examination that a plain-language field can use instead.

Fixes 02/10/2026 05:47

1. 1.2 — Restored common-practice qualifier: Rewrote the monitoring cadence so the IGF-1 and glycated haemoglobin recheck interval reads “by common practice, IGF-1 and glycated haemoglobin at roughly 4–6 weeks, then every 3–6 months”, matching the ER.
2. 2.7 — Replaced funduscopic jargon: Changed “dilated funduscopic examination” and “periodic funduscopic examination” in the cadence to “dilated back-of-the-eye examination” and “periodic back-of-the-eye examination”, the ER’s own gloss.