Audit: QRS - Tributyrin for Health & Longevity

Audit conducted on 19/06/2026 10:58 using AI4L / Opus 4.8

Iterations

Summary

Items	Count
Total	91
Passed	91
Failed	0
N/A	0
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.	🟢	All content traces to the ER (Protocol, Benefits, Risks, Monitoring, Conclusion, Key Interactions & Contraindications).
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.	🟢	At-a-glance and tier labels preserve the ER’s cautious framing (“rest mostly on cell and animal studies”, “looks reassuring”).
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 strengthening/softening detected; contraindications and cautions retain ER force.
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.	🟢	Contraindications/interactions drawn from the ER’s Key Interactions & Contraindications section; no cross-category relabeling.
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.	🟢	The QRS contains no PMIDs, citations, NCT IDs, or brand names.
1.6	The QRS does not introduce new attributions.	🟢	No new 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, evidence-graded tone.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert yet accessible; objective framing throughout.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence without prescribing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Protocol presented descriptively; footer disclaims medical advice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Information-presenting voice throughout.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language with brief glosses where needed.
2.8	Information is presented in a concise and very compact manner	🟢	Dense card/table layout, terse phrasing.
2.9	It DOES NOT address the reader directly	🟢	No direct address.
2.10	The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review.	🟢	Framing targets proactive longevity-oriented users.
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.	🟢	Protocol/monitoring assume a willing, effort-tolerant reader.
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢	Not written for the general population.
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 proactive audience.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim.	🟢	Title and body use “longevity”; no “anti-aging” usage.
2.15	The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language. Direct quotes from sources are exempt.	🟢	Uses “gastrointestinal”, “supplement doses”, etc.; no consumer-grade slang.

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card/section headings (“Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”); Gate headings (“Contraindications”, “Key Interactions”); Tier labels (“High”, “Medium”, “Low”, “Speculative”); Monitoring column headers (“Marker”, “Target”, “Why”).	🟢	All fixed headings and labels present and unmodified.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template var spans present, including hidden benefits_high/risks_high.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-targeted spans unchanged.

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”	🟢	Empty High tiers handled via display:none (per 12.5/13.5), not empty-state text; no empty ER section was misquoted.
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 labels (Standard Dose, Timing, Split Dosing) and markers align with ER labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels faithful to ER content.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators in the rendered 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.	🟢	Content condensed to one-page budget.

---

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 is first element after 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.	🟢	YAML delimited by “—” lines (lines 3 and 12).
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.	🟢	Inside an HTML comment; not rendered.
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 trimmed and unquoted as appropriate.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: tributyrin_2026-0619-1010_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.5.18 matches QRS.md.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]”	🟢	qrs_creation_date: 2026-0619-1010.
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.	🟢	“Opus” — single word.
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 4.8.
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier	🟢	“Opus 4.8” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: tributyrin_2026-0619-1010_Opus_QRS.html.
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.	🟢	Values clean and consistent.

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”. The [canonical_topic] is HTML-entity-encoded as needed.	🟢	“Tributyrin for Health & Longevity - Quick Reference Sheet”.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed.	🟢	“Tributyrin for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	06/19/2026 from 2026-0619.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 4.8”.
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 date and model; no extra content.

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 Conclusion (releases butyrate, only target engagement confirmed, benefits mostly preclinical, safe at supplement doses).
7.2	[at_a_glance] is no longer than 60 words	🟢	52 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to the Conclusion/Mechanism passages.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Plain-language only (“natural fat”, “compound gut bacteria make from fiber”).
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial citations.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No 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 this intervention” bullet.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five avoid-populations represented.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is its own <li>.
8.4	Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em/en/hyphen-dash. Just the key fact.	🟢	Items terse; only parenthetical qualifiers retained, 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.	🟢	“(no safety data)”, “(medical supervision only)”, “(decompensated liver disease, advanced chronic kidney disease)” preserved.
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 bare ranking symbols carried through.
8.7	If no [stop_items] are present the section is left empty	🟢	Contraindications exist and are populated; condition not met for empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from the ER interactions bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Orlistat, other butyrate sources, fermentable fibers/prebiotics, high-fiber diet; HDAC-inhibitor excluded (already a contraindication).
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is its own <li>.
9.4	Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em/en/hyphen-dash. Just the key fact.	🟢	Terse; mechanistic rationale stripped.
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.	🟢	“(lipase-blocking weight-loss drug)”, “(sodium/calcium-magnesium butyrate)”, “(resistant starch, inulin)” preserved.
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 bare ranking symbols.
9.7	If no [caution_items] are present the section is left empty	🟢	Interactions exist and are populated; condition not met for empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	Drawn from the Therapeutic Protocol and Risk Mitigation sections.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard dose, timing (with food), split dosing — the three core actionable levers.
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.	🟢	Three aspects exist; all three sets used appropriately.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All three sets filled with 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	🟢	Raised butyrate (hours), gut/systemic outcomes (weeks), study intervention periods (~4 weeks+).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order matches descending benefit magnitude: Raised Butyrate (Medium tier, the most-demonstrated benefit) → Gut/Systemic Outcomes (Low-tier benefits) → Study Intervention Periods (no specific benefit).
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.	🟢	Three aspects exist; all three used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All filled from the ER’s Practical Considerations “Time to effect” bullet.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel	🟢	The ER provides time-to-effect data; section retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Tiers map to ER Expected Benefits grades.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier variables present.
12.3	Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations, etc. Just the key fact.	🟢	Tier items reduced to bare benefit names.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Target Engagement)” stripped from the Medium 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 empty-state phrasing.	🟢	benefits_high (no High benefits in ER) set to display:none.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Tiers map to ER risk grades.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier variables present.
13.3	Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations, etc. Just the key fact.	🟢	Risk items reduced to bare names.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical detail retained.
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 empty-state phrasing.	🟢	risks_high (no High risks in ER) set to display:none.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Drawn from the Monitoring Protocol table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven (hs-CRP, fasting glucose, fasting insulin, HbA1c, ALT, CBC, eGFR/creatinine) listed with matching targets.
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.	🟢	Baseline → ~3 months → every 6–12 months cadence reproduced.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER’s qualitative markers list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All four qualitative markers listed.

Issues 19/06/2026 10:58

Pass rate 100.00%. No issues found.

Issues 19/06/2026 10:54

1. 9.2 — HDAC inhibitor duplicated in gates: “Pharmaceutical HDAC inhibitors (vorinostat, romidepsin)” appears in Key Interactions (line 553) while “Pharmaceutical HDAC-inhibitor therapy” is already a Contraindication (line 544); per 9.2 it must be excluded from Key Interactions.
2. 12.3 / 12.4 — Benefit qualifier not stripped: benefits_medium “Increased systemic butyrate availability (target engagement)” (line 524) retains the “(target engagement)” parenthetical, which must be stripped.

Fixes 19/06/2026 10:54

1. 9.2 — HDAC inhibitor duplicated in gates: Removed the “Pharmaceutical HDAC inhibitors (vorinostat, romidepsin)” item from Key Interactions, since “Pharmaceutical HDAC-inhibitor therapy” is already listed as a Contraindication.
2. 12.3 / 12.4 — Benefit qualifier not stripped: Stripped the “(target engagement)” parenthetical from benefits_medium, leaving “Increased systemic butyrate availability”.