Audit: QRS - Monolaurin for Health & Longevity

Audit conducted on 26/08/2026 02:27 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 86
Failed 0
N/A 7
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 populated span traces to ER text: at-a-glance to Conclusion, protocol cells to Therapeutic Protocol, time cells to Practical Considerations plus the nasal magnitude line, gates to Key Interactions & Contraindications, tiers to the ER benefit/risk sub-headings, markers and cadence to the Monitoring Protocol & Defining Success table and prose.
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. 🟢 Cautious ER phrasing carried through verbatim: “no trial has measured any oral time course” (time_2_sub), “untested rather than disproven” (at_a_glance), “No established target value” (marker_7_target).
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 tier or severity shifts. “Pregnancy and breastfeeding” stays an absolute contraindication; oral use stays “untested rather than disproven” rather than “ineffective”.
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. 🟢 Nothing from Benefit-Modifying Factors or Risk-Modifying Factors is surfaced in the gates. Contraindications come only from the ER’s “Populations who should avoid Monolaurin” list; interactions only from the ER’s interaction bullets.
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 identifiers, study names or expert names appear. The only brand name, “Alli”, is present in the ER for the same orlistat fact.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions. “described by practitioners” (time_2_sub) mirrors the ER’s own “practitioners describe”.

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. 🟢 Matches the ER’s sober, evidence-limited register throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective and data-driven; the negative framing of oral use is the ER’s own conclusion, not editorialising.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence and thresholds; no prescriptive clinician voice.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives. monitoring_cadence is phrased as descriptive noun clauses (“Lipid panel and blood count at baseline, repeated at 12 weeks”).
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”, “advise” or “guidance” verbs anywhere in the content spans.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; the only technical terms are biomarker names, which are unavoidable in the Monitoring table.
2.8 Information is presented in a concise and very compact manner 🟢 Every span is condensed to label-level or single-clause form.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by search: no “you”, “your”, “we”, “our” or “us” in the file.
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 assumes a proactive optimiser: dose-escalation schedules, self-monitoring biomarkers, culture-confirmed decolonisation tracking.
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. 🟢 Presents multi-week titration, split dosing with meals, repeat lab panels and pre/post cultures without hedging on effort.
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 audience: apolipoprotein B targets, absolute lymphocyte count thresholds and CD4 cut-offs assume an engaged reader.
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. 🟢 Weighting reflects the audience — the oral form that dominates the market is flagged as untested, and the added saturated-fat load is surfaced as a monitorable risk.
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 only “anti-“ construction is “anti-inflammatory”, which is a mechanism term from the ER.
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. 🟢 Clinical register maintained (“intravaginal”, “mucosal irritation”, “absolute lymphocyte count”). The plainer wording in at_a_glance is ER-verbatim and required by item 7.4.

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 present and unmodified: “Protocol” (445), “Time to effect” (488), “Benefits” (535), “Risk & Side Effects” (612), “Monitoring” (638), “Qualitative Assessment” (767), “Contraindications” (560), “Key Interactions” (580), “Marker”/”Target”/”Why” (642-644), and the tier labels High/Medium/Low/Speculative.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variables present; the repeatable marker_#* and qualitative_item# placeholders are expanded to 7 marker rows and 5 qualitative items with no name gaps.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against the template shows changes confined to variable regions. The non-variable website="evidence_review", website="audit" and website="full_review" spans, the stylesheet, and the footer disclaimer 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 is empty. The ER’s High and Medium benefit tiers and High risk tier carry explanatory prose rather than an empty-state phrase, and item 12.5/13.5 governs their handling in the QRS.
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. 🟢 ER bold labels reused verbatim: “Standard oral protocol”, “Competing topical-only approach”, “Best time of day” for the protocol cells; the ER’s Time to effect bold label is the fixed subhead; monitoring row labels match the ER biomarker table column verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 time_1_label “Topical and mucosal use” and time_2_label “Oral use” are lifted from the ER’s own wording in the Time to effect bullet, not invented.
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 on two speculative items were 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. 🟢 Each section is condensed relative to the ER rather than carried over: benefit and risk tiers collapse the ER sub-headings into semicolon lists with magnitudes stripped, gate items are reduced to label plus parenthetical, and the marker “Why” cells are single clauses.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 The metadata comment opens at line 2, immediately after <!doctype html> on line 1, and precedes the template comment at 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 --- at line 3, closing --- at line 13. The preceding “QRS — Metadata” text 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. 🟢 Wholly inside an HTML comment; none of the values are echoed by any rendered element.
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. 🟢 All values trimmed. Only duration: "00:02" is quoted, which is required because the value contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: monolaurin_2026-0826-0013_Opus_ER.md matches the source ER’s own filename frontmatter value.
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.7.02 matches the version badge at the top of 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-0826-0221 conforms to YYYY-MMDD-HHMM.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: 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, 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]” 🟢 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) 🟢 Nickname plus version number only; no qualifier such as a context-window suffix.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: monolaurin_2026-0826-0013_Opus_QRS.html 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. 🟢 Re-verified: no stray whitespace or unnecessary quoting on any of the 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., &amp; for &) 🟢 <title>Monolaurin &amp; Longevity... — title reads “Monolaurin for Health & Longevity - Quick Reference Sheet”, matching canonical_topic with the ampersand entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 header_topic is “Monolaurin for Health & Longevity”, identical to the ER canonical_topic with &amp; encoding.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 header_subline_date “08/26/2026” is qrs_creation_date 2026-0826-0221 in MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model “Opus 5” equals qrs_creator_ai_fullname.
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 carries only the title and the template subline. No badge, version stamp, alternate-names line, audit date or variant marker.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distils the ER Conclusion to the execution-relevant point: local and topical use has a modest real case, the oral form that dominates the market is untested.
7.2 [at_a_glance] is no longer than 60 words 🟢 56 words, within the 60-word ceiling.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion passage — the membrane description, the “thin and almost entirely local” human-work sentence, the “untested rather than disproven” sentence, and the “recorded harms are mild and mostly local” sentence.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications; “coconut-derived fat”, “membranes”, “pellets” and “vaginal gel” are all plain-language.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No study names, years, sample sizes or p-values.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, risk ratios or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER’s “Populations who should avoid Monolaurin” list inside Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-population bullets are represented, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 All six items are <li> elements inside the stop_items 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. 🟢 Trailing rationale stripped throughout — “— no human safety data exist…”, “, since almost all commercial product is derived from these oils”, “, outside of what they receive in breast milk” and “, given the documented mucosal irritation” are all removed.
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). 🟢 Thresholds preserved: “absolute lymphocyte count below 1.0 × 10⁹/L, CD4 count below 200 cells/µL”, “under 2 years”, and the culture-confirmed infection examples. Only the ER’s glossary aside “(a measure of helper T-cell numbers)” was dropped, which item 8.4 requires.
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 section is populated, which is correct: the ER names six populations that should avoid the intervention.
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 🟢 Drawn from the ER’s nine interaction bullets in Key Interactions & Contraindications.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All nine ER interaction bullets are present and none duplicates a contraindication item.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 All nine items are <li> elements inside the caution_items 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. 🟢 Severity, Consequence and Mitigation clauses stripped from every item; the ER’s organisational prefix “Other interventions —” is removed from the decolonisation-protocol item as the em-dash rule requires.
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 parenthetical is preserved, including the five-agent antimicrobial-supplement list and the three-agent antiseptic list.
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 section is populated, which is correct: the ER names nine 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 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 three selected — the standard oral escalation, the competing topical-only approach, and timing with meals — are the most actionable of the ER’s eleven protocol bullets; the remainder are modifiers 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 more than three actionable implementation 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 populated fields carry ER-derived content: 750 → 1,500 → 3,000 mg with the week-one/week-two/maintenance schedule, the 5% gel twice daily for three days, and dosing with meals with the lipid rationale.

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 🟢 Both time-to-effect aspects the ER supplies are covered; the ER describes no third.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Topical/mucosal is first, matching the Low-tier nasal decolonisation benefit — the strongest human signal in the ER; oral, which no trial has measured, follows.
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. 🟢 The third set is emptied and its .pcell carries style="display: none"; no placeholder or empty-state text was inserted.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 time_1 “8–12 hours” with persistence “two to three days” and time_2 “2–6 weeks” with the no-trial caveat are both ER-sourced.
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, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from the ER Expected Benefits tier sub-headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four tier variables present; high and medium are collapsed, low and speculative 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. 🟢 Items are the ER sub-heading text only — no magnitudes, sample sizes, citations or author affiliations carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content retained; the effect-size parentheses such as “(3 log₁₀)” are absent.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 benefits_high and benefits_medium spans carry style="display: none" with the inner <li> removed, and no empty-state phrasing was substituted.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from the ER Potential Risks & Side Effects tier sub-headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four tier variables present; high is collapsed, medium, low and speculative 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. 🟢 Items are the ER sub-heading text only — no frequencies, risk differences, confidence intervals or p-values carried over.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content retained; the “⚠️ Conflicted” marker on the emulsifier item is stripped.
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. 🟢 risks_high span carries style="display: none" with the inner <li> removed, and no empty-state phrasing was substituted.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol & Defining Success biomarker table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All seven ER biomarkers listed with targets verbatim: apolipoprotein B, LDL cholesterol, absolute lymphocyte count, hs-CRP, alanine aminotransferase, fasting glucose, and nasal or lesion culture for Staphylococcus aureus.
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. 🟢 monitoring_cadence carries the ER’s full cadence — baseline, 12 weeks, then every 6–12 months at 3 g daily or above, cultures 1 week after each topical course, annual testing at 1–2 g daily.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER’s “Qualitative markers worth tracking alongside the labs” list in the same Monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers listed verbatim: bowel pattern and abdominal comfort, upper respiratory infection frequency and duration, recurrent boils/cold sores/vaginal symptoms, topical-site skin condition, and energy and daily function.

Issues 26/08/2026 02:27

Pass rate 100.00%. No issues found.