Audit: QRS - Indole-3-Lactic Acid for Health & Longevity

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

Summary

Items	Count
Total	94
Passed	86
Failed	0
N/A	8
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.	🟢	Dose (8 × 10⁹ CFU), 17-day onset, all biomarker targets, cadence and qualitative markers trace to ER Therapeutic Protocol, Practical Considerations and 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 figure exists”, “No human clinical outcome has been measured”, “No established target”, “conflicted” mirror the ER’s own hedging.
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”).	🟢	Pregnancy/breastfeeding and CKD 4–5 remain in the Contraindications gate, not the Caution gate; the ER’s “⚠️ Conflicted” flags are retained as “(conflicted)”.
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.	🟢	Gate items come only from ER `Key Interactions & Contraindications`; tier items only from `Expected Benefits` / `Potential Risks & Side Effects`; no Modifying-Factor content is repositioned.
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 IDs or author names anywhere; the only proper names are strain designations (BB536) and species names, all present in the ER Protocol section.
1.6	The QRS does not introduce new attributions.	🟢	Company attributions in the ER (Morinaga Milk Industry, Infinant Health, Evolve BioSystems) are omitted rather than restated or replaced.

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.	🟢	Measured, non-promotional register matching the ER, including its British spellings (“fibre”, “ageing”, “colonisation”, “favourable”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Actionable routes, quantified targets and a monitoring cadence give the reader something to act on while the evidence limits stay explicit.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells describe what trials used (“Dose used in the trials that raised fecal concentrations”) rather than instructing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives and no prescriptive verbs in any populated variable.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should” or “consult” in QRS content.
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	🟢	Retained technical terms (hs-CRP, eGFR, anti-PD-1) are the ER’s own biomarker and drug-class names, where no plain substitute exists.
2.8	Information is presented in a concise and very compact manner	🟢	Tier rows are semicolon-joined fragments; gate items are single clauses; marker rows are short noun phrases.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” in the QRS.
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.	🟢	Sheet is framed around implementation routes, exposure monitoring and hard stops.
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.	🟢	Fibre-led regimen, daily live-organism dosing and specialty metabolomics markers are presented without hedging on effort or cost.
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.	🟢	Research-only supply status and LC-MS/MS-dependent markers are presented as workable constraints, not deterrents.
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢	At-A-Glance states plainly that the effect in healthy adults is unmeasured — the decision-relevant point 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.	🟢	“slowing ageing” and “age-related inflammation”; no “anti-aging”/”anti-ageing” anywhere.
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 route-of-administration colloquialisms; “colony-forming units”, “fecal concentrations”, “filtration” used throughout.

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”	🟢	Line-by-line comparison against the template shows every fixed heading, gate head, tier label and column header byte-identical.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 35 distinct template names present; the repeating `marker_#_*` and `qualitative_item_#` rows are instantiated as marker_1–7 and qualitative_item_1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	`<span website="evidence_review">`, `<span website="audit">` and `<span website="full_review">` are untouched; the CSS block, footer disclaimer and all structural markup 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 source ER section is empty; the absent High tiers are handled under 12.5 / 13.5 by hiding the span rather than by empty-state phrasing.
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 cell labels reproduce the ER bullet labels verbatim: “Infant-type bifidobacteria route”, “Adult fermented-milk route”, “Competing approach — prebiotic first”.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Marker names match the ER biomarker table verbatim; Protocol labels match the ER bullet labels.
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; the ER’s “⚠️ Conflicted” markers are rendered as the plain word “(conflicted)”.
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 discretionary section is compressed to the minimum (mechanisms, magnitudes, parentheticals and attributions all dropped); the only long lists — 7 interactions and 7 markers — are mandated in full by 9.2 and 14.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.	🟢	Single comment spanning lines 2–14, immediately after `<!doctype html>` on line 1.
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 preceding “QRS — Metadata” label sits above 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.	🟢	Enclosed in an HTML comment; none of its values is repeated in head or body markup.
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:03"` is quoted, correctly, because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: indole_3_lactic_acid_2026-0920-1614_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-1732`.
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 only, no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s actual name 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, no unnecessary quoting on any of the nine keys.

#	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 `&`)	🟢	“Indole-3-Lactic Acid for Health & Longevity - Quick Reference Sheet” — ampersand correctly encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	“Indole-3-Lactic Acid for Health & Longevity”, matching the ER `canonical_topic`.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0922-1732 → “09/22/2026”.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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.	🟢	Header holds only the title and the template subline; the ER’s “Also known as” list is 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 “a compound gut bacteria make from a dietary amino acid, studied for calming inflammation and slowing ageing” — kind and purpose before any verdict.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Compresses the Conclusion’s four moves — what it is, that it is not a purchasable product, that observation dominates administration, and that the healthy-adult effect is unmeasured — and adds the practical route.
7.3	[at_a_glance] is no longer than 70 words	🟢	66 words.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct source: Motivation (bacterial synthesis), Expected Benefits (inflammation, ageing), Sourcing and Quality (research-use-only), Therapeutic Protocol (indirect route), Conclusion (mixed direction, unmeasured in healthy adults).
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “a dietary amino acid” replaces tryptophan and “laboratory material” replaces research-grade reagent.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years or sample sizes.
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All five items map to the ER’s “Populations who should avoid Indole-3-Lactic Acid” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations present, in ER order, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five `<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.	🟢	ER rationales dropped (“on the basis of the placental cell-model activity”, “given the first-week association with later attention deficits”, “who cannot safely take live bacterial products”); no dash-trailing clauses remain.
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).	🟢	Staging and threshold preserved: “stage 4 or 5 (filtration below 30 mL/min/1.73 m²) or dialysis”; tumour qualifier preserved as “(particularly esophageal squamous cell carcinoma)”; “outside a supervised trial” retained.
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’s avoid-populations list 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 names five such populations and the section is correctly populated rather than left 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	🟢	All seven items map to ER interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven of the ER’s eight interaction bullets are carried; the checkpoint-inhibitor bullet is correctly omitted because anti-PD-1 therapy is already a Contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven `<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.	🟢	Each item is agent plus consequence only; the ER’s Mitigation sentences and mechanistic explanations (“They deplete the bifidobacteria…”, “Raising gut pH favours…”) are stripped, and no dash-trailing clauses remain.
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 lists preserved in full: the three antibiotics, the three acid-reducing agents, the three statins, the three probiotic species and the four prebiotic fibres.
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’s interaction bullets use 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 names eight interactions and the section is correctly populated rather than left 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	🟢	All three cells trace to 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 dosing routes plus the competing prebiotic-first approach are the only bullets that specify what to actually take; timing, half-life, split dosing and genotype notes are secondary.
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 three or more actionable aspects and all three sets are populated.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	Nine cells populated; values carry the ER’s strain and dose (“8 × 10⁹ colony-forming units daily”, “BB536 in fermented milk”) and the subs carry the ER’s supporting facts.

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	🟢	Onset of the measurable effect, absence of a clinical-benefit timeline, and reversal after stopping — drawn from ER `Practical Considerations` and `Discontinuation & Cycling`.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	The only demonstrated, quantified change (fecal concentrations, day 17) leads; the unquantified clinical endpoint follows; the offset window closes.
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	The ER supplies three distinct aspects and all three sets are populated.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Nine cells populated; “Days to weeks” / “day 17”, “No figure exists”, “Within weeks” / “colonisation is transient” all trace to ER text.
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 an explicit “Time to effect” bullet, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	All eight listed benefits correspond to ER `Expected Benefits` sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and correctly tiered: three Medium, one Low, four Speculative, High hidden.
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-headings alone; the odds ratios (0.85, 0.70), cohort sizes (1,359 / 142) and CCL2/CCL7 mechanism are all absent. The retained “(conflicted)” is the ER’s own evidence-conflict flag, required by 1.3.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s definitional and mechanistic parentheses (“joint degeneration causing pain and stiffness in the fingers”, “proteins recruiting inflammatory white blood cells”, “an itchy, relapsing inflammatory skin disease”) are all stripped.
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` carries `style="display: none"` with an empty `<li>` and an HTML comment citing the ER’s “No benefit reaches High”; no empty-state text rendered.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All seven listed risks correspond to ER `Potential Risks & Side Effects` sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and correctly tiered: three Medium, one Low, three Speculative, High hidden.
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-headings alone; the odds ratios (4.49, 2.14), cohort sizes (122 patients, 4,833 people) and the mediation analysis detail are all absent.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s glosses (“meaning heart attack, stroke or death”, “drugs releasing a brake called programmed cell death protein 1 on immune T cells”, “progressive loss of kidney filtering capacity”) are all 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` carries `style="display: none"` with an empty `<li>` and an HTML comment citing the ER’s “No risk reaches High”; no empty-state text rendered.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Table and cadence both drawn from ER `Monitoring Protocol & Defining Success`.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All seven ER biomarker rows present in ER order, with targets verbatim (Below 0.5 mg/L, Above 90 mL/min/1.73 m², Below 50 µg/g, 45–75 µmol/L).
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.	🟢	“Kidney filtration and inflammation markers at 3 months, then every 6–12 months; the metabolite and stool composition at 3 months and again at 12 months” — matches the ER’s ongoing-monitoring sentence.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Drawn from the ER’s “Qualitative markers worth tracking alongside the laboratory values” list.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All five ER qualitative markers present verbatim and in ER order.

Issues 22/09/2026 17:37

Pass rate 100.00%. No issues found.