Audit: QRS - Lactobacillus casei for Health & Longevity

Audit conducted on 05/09/2026 02:46 using AI4L / Opus 5

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
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 value traces to the ER: dose (ER Therapeutic Protocol), gate items (ER Key Interactions & Contraindications), tiers (ER Expected Benefits / Potential Risks), markers and cadence (ER Monitoring Protocol).
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 altered; the empty High-risk tier is handled per item 13.5 rather than reworded.
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”).	🟢	Absolute contraindications stay absolute; interactions stay interactions.
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.	🟢	Benefit- and Risk-Modifying Factors are not surfaced in the gates; gates draw only on the ER’s interaction and avoid-population lists.
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, expert names, NCT identifiers, or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No 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.	🟢	Matches the ER’s measured, funding-aware register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢
2.4	The QRS avoids language that implies medical or clinical advice	🟢
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “should”, “must”, “recommend”, or “advise” 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 file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are used only where the ER uses them; At-A-Glance is plain language.
2.8	Information is presented in a concise and very compact manner	🟢
2.9	It DOES NOT address the reader directly	🟢	No second-person pronouns anywhere 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.	🟢
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.	🟢
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢	Funding bias and strain-versus-species caveats are carried into At-A-Glance, which is the signal this audience needs.
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 occurrence of “anti-aging” or “antiaging”.
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.	🟢	Formal terminology throughout; the plain-language wording in At-A-Glance is 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, gate headings, tier labels, and Monitoring column headers are unmodified.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template span names are present; marker_#* and qualitative_item#_* are expanded to 5 and 7 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A full diff against the template shows changes only inside data-qrs-var spans and the metadata block.

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 is empty, so no empty-state phrasing applies; the absent High-risk tier is governed by item 13.5.
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 “Standard dose”, “Best time of day”, and “Antibiotic-associated diarrhoea protocol” are reused verbatim as Protocol labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Marker names are verbatim from the ER Monitoring table.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters in the file.
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 section is condensed to key facts with no elaboration; the long gate, marker, and qualitative lists are mandated in full by items 8.2, 14.2, and 15.2.

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢	Lines 2-14: the metadata comment is the first element after <!doctype html>.
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.	🟢	”—” opens at line 3 and closes at 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.	🟢	Wrapped in an HTML comment; not repeated in 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” is quoted, which its colon requires.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: lactobacillus_casei_2026-0905-0002_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.7.02 matches 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)	🟢	qrs_creation_date: 2026-0905-0239.
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.
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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename 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.	🟢	As for 5.4.

#	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 `&`)	🟢	“Lactobacillus casei for Health & Longevity - Quick Reference Sheet”; 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., `&` for `&`)	🟢	“Lactobacillus casei for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/05/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0905.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	Header carries only the template’s date, source and model line.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Condenses the ER Conclusion: strain-versus-species, best-supported effects, safety split, and funding bias.
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 of the five claims maps to a distinct sentence in the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Plain-language throughout: “a long-term tube into a vein”, “weakened immune defences”, “live culture”; no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial 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 confidence intervals.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 10 ER contraindications are present: the two absolute drug-class contraindications plus the eight avoid-populations.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Ten <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.	🟢	Explanatory glosses such as “(drugs that deliberately damp the immune system: …)” are trimmed to bare drug names; no trailing dash clauses.
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: neutrophils below 0.5 x 10^9/L, APACHE II >= 8, Imrie >= 3, CRP above 150 mg/L, CD4 below 200 cells/uL.
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.
8.7	The section is left empty ONLY IF the ER’s `Key Interactions & Contraindications` section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER does identify avoid-populations, so the section is correctly not empty.
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	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven interactions carried over; the two absolute contraindications (immunosuppressants/biologics, cytotoxic chemotherapy) are correctly excluded.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven <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.	🟢	Mechanistic rationale and mitigation clauses from the ER bullets are stripped; no trailing 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 preserved for antibiotics, acid-suppressing drugs, prebiotic fibres, and antifungals/antiprotozoals.
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.
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 does identify interactions, so the section is correctly not empty.
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	🟢	Drawn from the ER Therapeutic Protocol section.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Standard dose, best time of day, and the antibiotic-associated diarrhoea schedule are the three decision-bearing items.
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 and 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 action fields carry ER-derived content.

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	🟢	Stool consistency, sleep quality, and joint symptoms are the only three time-to-effect aspects the ER states.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High (stool consistency) then Medium (sleep, joint), matching the ER benefit tiers.
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 and 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 time fields carry ER-derived content.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the `Protocol Panel`	N/A	The ER does provide time-to-effect information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier spans present and populated.
12.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢	Each tier is a semicolon-separated list of bare benefit headings.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses 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.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier spans 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.	🟢	Each tier is a semicolon-separated list of bare risk headings.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses 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.	🟢	risks_high carries style=”display: none” with an HTML comment citing the ER’s “No risk reaches High”.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Drawn from the ER Monitoring Protocol & Defining Success section.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All five ER biomarker table rows are present with their optimal ranges and rationale.
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 mirrors the ER: four weeks, three months, then six to twelve months.

15. Qualitative Assessment

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

Issues 05/09/2026 02:46

Pass rate 100.00%. No issues found.