Audit: QRS - Inositol for Health & Longevity

Audit conducted on 22/09/2026 17:41 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	94
Passed	84
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.	🟢	Every span traces to ER text: protocol cells to Therapeutic Protocol, time-to-effect to Practical Considerations, benefit/risk tiers to the ER sub-headings, gates to Key Interactions & Contraindications, monitoring rows and qualitative items to Monitoring Protocol & Defining Success.
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.	🟢	The eGFR row preserves the ER’s hedge verbatim (“No established inositol-specific target exists; track change from the individual’s own baseline instead”); time_3_sub keeps “Where present.”
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 avoid-level force; interactions retain caution-level force; lithium stays a gate rather than an interaction, matching the ER’s “relative contraindication”.
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.	🟢	No item from Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or the risks card; every gate item comes from Key Interactions & Contraindications.
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, citations, NCT identifiers, author names, or brand names anywhere in the sheet; the ER’s trial attribution in the “Best time of day” bullet was correctly stripped.
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.	🟢	Register, British spelling (“glycaemic”, “oestradiol”, “hypoglycaemia”), and framing match the ER throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric targets, defined protocols, and explicit gates give an actionable, objective register.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated descriptively (“the regimen used in…”, “the typical interval reported”), not issued as instruction.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive constructions; the cadence paragraph is phrased passively, as in the ER.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, “advised”, or equivalent in the document’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the sheet.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are confined to where they are load-bearing (drug names, biomarker names); the lede is jargon-free.
2.8	Information is presented in a concise and very compact manner	🟢	Gate, benefit, and risk items are bare facts; protocol subs are one to two sentences.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address.
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.	🟢	Optimal functional ranges (rather than conventional lab cut-offs) and a full self-monitoring cadence address exactly this audience.
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.	🟢	Twice-daily dosing, a 14-marker panel, and weekly home blood-pressure checks assume a high-effort reader.
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.	🟢	No simplification toward casual use; the sheet assumes baseline testing and ongoing tracking.
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.	🟢	The lede’s “clearest gains in people who begin with disturbed readings” carries the ER’s responder-selection point, which is the decisive framing for this audience.
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; the title uses “Health & Longevity” and the speculative tier uses “ageing”.
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.	🟢	No colloquial route-of-administration or adverse-event phrasing; “insulin secretagogues”, “antihypertensive drugs”, and “gastrointestinal intolerance” are used in place of lay equivalents.

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 446, 493, 535, 569, 581, 604, 630, 634–636, 795).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variables are present; the repeatable marker_#_* and qualitative_item_# spans are instantiated as marker_1..14_* and qualitative_item_1..6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A normalised structural diff against the template shows no deviation outside variable content; the website="evidence_review", website="audit", and website="full_review" spans, the footer disclaimer, and the entire <style> block are 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 ER section feeding the QRS is empty — all benefit and risk tiers, both gate lists, the protocol, the biomarker table, and the qualitative list are populated in the ER.
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 metabolic protocol”, “Standard reproductive protocol”, and “Best time of day” are the ER’s bold labels verbatim; the interaction items reuse the ER’s bold labels (e.g. “Insulin and insulin secretagogues (glipizide, glyburide, gliclazide, repaglinide)”, “Levothyroxine”, “Selenium”).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The three time-to-effect labels are lifted from the ER’s own wording (“hormonal and glycaemic markers”, “menstrual regularity”, “Sleep and anxiety effects”); the biomarker names match the ER table cells exactly.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji anywhere; the ER’s “⚠️ Conflicted” marker on the anxiety/mood benefit was 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.	🟢	Every condensation lever the checklist permits has been applied: gate items carry no trailing rationale (8.4/9.4), benefit and risk items are bare tier facts with all parentheticals stripped (12.3/12.4, 13.3/13.4), and protocol subs are one to two sentences. The remaining volume is content the checklist mandates in full (14 biomarkers per 14.2, all 11 non-contraindicated interactions per 9.2, all four benefit and risk tiers per 12.2/13.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: the metadata comment immediately follows <!doctype html> on line 1 and precedes the template comment on line 16.
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 --- on line 3, closing --- on line 13; the “QRS — Metadata” caption on line 2 sits before the opening delimiter.
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; no metadata value is echoed into the body except qrs_creation_date and qrs_creator_ai_fullname, which are required by 6.3 and 6.4.
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:02" is quoted, and it contains a colon. All other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: inositol_2026-0825-0010_Opus_ER.md, matching the ER’s own filename field.
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.9.22, matching the QRS.md version 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-0922-1733, correct format.
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 or qualifier.
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, no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: inositol_2026-0825-0010_Opus_QRS.html, matching 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.	🟢	Re-verified across all ten keys; no stray whitespace or unnecessary 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., & for &)	🟢	Line 22: “Inositol for Health & Longevity - Quick Reference Sheet”; the ER’s canonical_topic is “Inositol for Health & Longevity” and the ampersand is encoded.
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: “Inositol for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/22/2026”, correctly derived from qrs_creation_date: 2026-0922-1733.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter value.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header holds only the title and the template subline; the ER’s “Also known as” line was not carried over.

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 “Inositol is a sugar-like compound the body makes and food supplies, sold as a supplement at gram doses for blood sugar, hormone, and mood concerns” — kind and purpose both stated before any evidence verdict.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Compresses all three strands of the ER Conclusion: the metabolic core, the ovulatory/hormonal result, and the thinner mood/anxiety/sleep evidence.
7.3	[at_a_glance] is no longer than 70 words	🟢	67 words.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct ER passage in Motivation, Mechanism of Action, or Conclusion.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “blood sugar handling”, “blood fats”, and “disturbed readings” replace the clinical register used elsewhere on the sheet.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial named or dated.
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric effect estimates; the only number-like term is “gram doses”, which is a dose scale, not an effect size.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items come from the ER’s “Populations who should avoid Inositol” list inside that section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 572–576: five discrete <li> elements inside the span.
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.	🟢	The ER’s trailing clauses “where clearance is untested” and “where supplement-level exposure has not been studied” are both stripped; no dashes carry trailing content.
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).	🟢	“stage 4 or worse (eGFR below 30 mL/min/1.73 m²)”, “above 600 mg daily”, and “including post-bariatric reactive hypoglycaemia” are all retained; the parenthetical is shortened to “eGFR” rather than dropped.
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 inside parentheses 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 five such populations and the section is populated accordingly.
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 eleven items map to bullets in that ER section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Eleven of the ER’s twelve interaction bullets appear; lithium is correctly omitted because it is carried as a contraindication gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 584–594: eleven discrete <li> elements inside the span.
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.	🟢	Every ER mitigation clause (“Mitigation: staggered introduction with fasting-glucose monitoring”, etc.) is stripped; items are bare agent names.
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).	🟢	All four ER example-drug lists are preserved intact, and the selenium threshold “(at or below 200 mcg daily)” is 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 inside parentheses 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 twelve such entries and the section is populated accordingly.
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.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two named regimens (metabolic, reproductive) plus timing are the ER’s three operative implementation decisions; the remaining bullets are comparative positioning, provenance, and cost commentary rather than actions.
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 well over three actionable aspects, so no set is unused.
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 carry substantive ER-derived content; the ER’s trial reference in the timing bullet was stripped, as 1.5 requires.

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	🟢	The ER’s “Time to effect” bullet names exactly three horizons — glycaemic/hormonal markers, menstrual regularity, sleep and anxiety — and all three are carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Glycaemic/hormonal markers and menstrual regularity map to High-tier benefits and lead; sleep and anxiety map to Medium- and Low-tier benefits and come 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	Three distinct aspects exist, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans are populated; “Where present.” carries the ER’s own conditional hedge on the sleep and anxiety horizon.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All thirteen items are the ER’s Expected Benefits sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 537, 544, 550, 557, with 5 / 2 / 4 / 2 items matching the ER’s tier counts exactly.
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.	🟢	No Magnitude lines, certainty grades, or trial descriptions carried over; only essential population scope is retained (“in PCOS”, “in smokers with precancerous lesions”), which 1.3 requires.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain 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 ER benefit tiers contain items, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight items are the ER’s Potential Risks & Side Effects sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 606, 609, 615, 622, with 1 / 2 / 4 / 1 items matching the ER’s tier counts exactly.
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.	🟢	No Magnitude figures, trial sizes, or mechanisms carried over; only the isomer and dose scope essential to the claim is retained.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain 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 ER risk tiers contain items, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	The table reproduces the ER Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 14 ER rows are present in ER order, with Target and Why values matching the ER cells 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.	🟢	Lines 784–789 reproduce the ER’s cadence paragraph, including the blood-pressure, panel, thyroid, and glucose intervals.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present and verbatim, in ER order.

Issues 22/09/2026 17:41

Pass rate 100.00%. No issues found.