Audit: QRS - Lactobacillus salivarius for Health & Longevity

Audit conducted on 27/09/2026 20:24 using AI4L + evidence-mcp / GPT 6

Iterations

Summary

Items Count
Total 94
Passed 88
Failed 0
N/A 6
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. 🟢 Opening, study regimens, benefit/risk labels, exclusions and monitoring all trace to the named ER.
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. 🟢 Retains generally favorable short-term tolerance, absent longevity evidence and unestablished monitoring ranges.
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”). 🟢 Research regimens remain strain-specific; no species-wide longevity or treatment-replacement claim is introduced.
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. 🟢 Benefits, risks, contraindications and interactions remain in their source decision categories.
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. 🟢 All strain identifiers and named interaction medicines occur in the ER for these facts; no new citation or brand appears.
1.6 The QRS does not introduce new attributions. 🟢 No new expert, study or organizational attribution is 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. 🟢 Condition-specific, cautious framing follows the ER conclusion.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Provides concrete study doses and measurable outcomes with balanced uncertainty.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Describes research regimens and assessment intervals rather than issuing an individualized prescription.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Variable content presents evidence and research doses; the template educational disclaimer remains.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Uses descriptive trial schedules, outcome labels and monitoring information.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Authored variable content does not address a reader directly; fixed template disclaimer is retained.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Uses plain descriptions such as viable bacteria and breast inflammation; strain names and decision-gate terms remain precise.
2.8 Information is presented in a concise and very compact manner 🟢 Compact dose cells, tier summaries and short monitoring entries fit the single-sheet purpose.
2.9 It DOES NOT address the reader directly 🟢 No direct-reader language is added in any variable region.
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. 🟢 Opening and selected adult outcomes explicitly address health and longevity with risk awareness.
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. 🟢 Includes repeated daily dosing, condition-specific courses and longitudinal monitoring.
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. 🟢 Preserves exact strain matching and demanding schedules appropriate to proactive adults.
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. 🟢 Prioritizes adult-relevant condition-specific findings and distinguishes them from unproven lifespan extension.
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. 🟢 Uses longevity and slower human aging; no anti-aging framing appears.
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. 🟢 Uses oral capsule, oral-contact tablets, gestational timing and scientific strain terminology.

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 card, gate, tier and Monitoring column headings match the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Source comparison finds every template data-qrs-var anchor present, including marker_# and qualitative_item_#.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Variable changes correspond to explicit metadata, header, summary, protocol, outcome, gate or monitoring requirements.

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” 🟢 There is no empty source section requiring visible empty-state text; empty risk tiers follow the specific hiding rule.
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 and qualitative labels preserve the ER bold labels; interaction gate suffixes are stripped as explicitly required.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Outcome labels and biomarker names retain ER wording; no invented outcome label appears.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators appear 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. 🟢 Source specifies A4, compact typography, reduced gaps, 210 mm print width and section break avoidance; no browser was used.

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 immediately follows the doctype.
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. 🟢 Single metadata comment contains opening and closing YAML delimiters.
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 remains commented; required creation date and model are populated in their designated header fields.
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 are trimmed; the duration value contains a colon and is quoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename matches the named source in staging.
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 is 26.9.27, matching 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 is 2026-0927-2022 in the required 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 is GPT.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT is a single model nickname without a 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 is GPT 6.
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) 🟢 GPT 6 combines the nickname and version without qualifiers.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the actual audited creation filename.
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. 🟢 No frontmatter value has extraneous 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., &amp; for &) 🟢 Title matches canonical_topic plus the required suffix, with the ampersand 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 matches canonical_topic and encodes the ampersand.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 matches the creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model is GPT 6, matching metadata.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only template-required header content is present; audit anchor remains empty.

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 by identifying a bacterium used in probiotic supplements and its health uses.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses strongest condition-specific evidence, oral inconsistency, tolerance and absent longevity benefit from Conclusion.
7.3 [at_a_glance] is no longer than 70 words 🟢 Programmatic whitespace word count: 67.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Identity/use is supported by Motivation; efficacy, safety and longevity statements each appear in Conclusion.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No specialist acronym or classification appears; breast inflammation replaces mastitis in the opening.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No named trial, year, sample size or p-value appears in the opening.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect size, relative risk or statistical result appears in the opening.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All four exclusions derive from Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Includes ingredient allergy, predicted severe acute pancreatitis, susceptible severely ill hosts and premature infants.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Every stop entry is enclosed in li tags.
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. 🟢 Entries contain the exclusion and applicability qualifiers without mechanisms or study explanations.
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). 🟢 Preserves predicted severity, central venous catheter, barrier disruption and specialist/neonatal supervision conditions.
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 source ranking notation needs normalization; combined host vulnerabilities use comma-separated terms.
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. 🟢 Gate is populated because the ER names populations who should avoid supplementation.
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 Gate is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All seven gate entries derive from Key Interactions & Contraindications.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Includes exposure-changing antibiotic, immune, oncology, antiseptic, fiber, stacking and treatment-substitution interactions; OTC medicines have no established specific interaction in the ER.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Every interaction entry is enclosed in li tags.
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. 🟢 Entries retain key exposures and essential treatment-substitution facts without mechanisms, studies or trailing dash explanations.
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). 🟢 Preserves antibiotic, immunosuppressant, cytotoxic, immunotherapy, antiseptic and fermentable-fiber examples.
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 interpretively dependent ranking notation occurs.
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. 🟢 Gate is populated with the source interaction categories.
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 Gate is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three dose regimens derive from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers intestinal capsule use, replicated mastitis-prevention research and distinct oral-contact administration.
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 ER provides more than three actionable implementation aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Each populated label, dose and subline supplies a source regimen, strain, schedule or administration detail.

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 🟢 Includes eczema, gout and fertility, the strongest selected outcomes with explicit assessment times.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Places replicated eczema evidence first, followed by the larger absolute gout-event signal and the fertility signal; the source provides no common effect-size scale across these outcomes.
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 ER provides at least three distinct effect-assessment intervals.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Eczema 8–16 weeks, gout six months and fertility several months are explicitly supported; cells identify assessment contexts.
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 ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Each displayed benefit is an Expected Benefits outcome under the same evidence tier.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefits anchors are 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. 🟢 Displays compact outcome labels without supporting explanations or study details.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical statistical or study content remains.
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 Each source benefit tier contains items.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All displayed risk labels come from Potential Risks & Side Effects at their original tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk anchors are retained.
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. 🟢 Displays source risk labels without frequency, mechanism or study detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical supporting content remains.
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. 🟢 Empty High and Medium risk spans use style=”display: none” and contain no empty-state prose.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 All marker rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 Includes all five source quantifiable markers: oral, eczema, urate, clinically indicated blood tests and species abundance.
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 preserves baseline, 1–2-week tolerance, 4–8-week oral/intestinal and 8–16-week eczema assessment.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative content derives from the three Monitoring bullets.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Includes Symptoms, Function and Adverse effects with the source examples.

Issues 27/09/2026 20:24

Pass rate 100.00%. No issues found.