Audit: QRS - Larazotide for Health & Longevity

Audit conducted on 12/09/2026 05:41 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	83
Failed	0
N/A	10
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 ER Conclusion (lines 460-466), protocol cells to ER Therapeutic Protocol (lines 334-338), time cells to ER lines 388/166/414, benefits/risks tiers to ER headings, gates to ER lines 290-310, markers to the ER biomarker table (lines 418-428).
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.	🟢	“Unknown safety beyond six months” and “No established target; track change from the individual’s own baseline” carry the ER’s hedges verbatim; “Proposed proxy for barrier leakiness” keeps “Proposed”.
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”).	🟢	Contraindication thresholds (≥3× ULN, ≤50 mL/min/1.73 m²) and the pregnancy/breastfeeding avoidance are carried at full strength; “No evidence it protects the intestinal lining” matches ER line 462.
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 come only from the ER’s “Populations who should avoid Larazotide” list; Key Interactions only from the ER’s interaction bullets; no Benefit- or Risk-Modifying Factor is promoted into a gate or risk tier.
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 PMID, NCT identifier, “et al.” citation, sponsor name, or expert name appears anywhere in the QRS; the ER’s citations on qualitative items 2 and 3 were stripped.
1.6	The QRS does not introduce new attributions.	🟢	No attribution of any kind is present in the QRS.

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.	🟢	Sober, evidence-weighted register matching the ER, including the ER’s own framing of the inverted dose-response and the unproven mucosal protection.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Thresholds, ranges and cadences are given without alarm or hype; the negative signal is reported neutrally, as in the ER.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Descriptive constructions throughout (“Capsules are administered”, “The only dose that met a primary endpoint”); no imperatives directed at a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No instruction to start, stop, or adjust anything; Protocol and Monitoring state what the trials used.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “advised”, or “should” in the document’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun occurs anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker names, which are unavoidable; the lede uses “seals between intestinal lining cells” rather than “tight junctions”.
2.8	Information is presented in a concise and very compact manner	🟢	Every gate, benefit, and risk item is a bare noun phrase; tiers are collapsed into single semicolon-separated lines.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by scan: no “you”, “your”, or “yours” 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 is pitched at self-directed application: exact dose, meal timing, formulation, and an 11-marker laboratory panel.
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.	🟢	Three-times-daily pre-meal dosing, an obligatory gluten-free diet, and weekly symptom scoring are presented without hedging about burden.
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.	🟢	No simplification to a general-population takeaway; the biomarker panel and functional ranges 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.	🟢	The self-sourcing hazard specific to this audience is surfaced (“product quality failure from unregulated suppliers”) alongside the unproven-mucosal-cover 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 occur; the header carries the ER’s canonical “Health & Longevity”.
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.	🟢	The lede uses “administered orally”; the risks card uses “gastrointestinal adverse events”; no “pill”, “by mouth”, “shot”, or “bad reaction” occurs.

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”	🟢	Byte-for-byte identical to [qrs_template]: “Protocol” (446), “Time to effect” (490), “Benefits” (539), “Risk & Side Effects” (612), “Monitoring” (637), “Qualitative Assessment” (804), “Contraindications” (567), “Key Interactions” (584), tier labels and the Marker/Target/Why headers (641-643).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 fixed template variables present; the repeatable marker_#name/target/why pattern is instantiated 11 times and qualitative_item# 5 times, with no variable missing.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three non-variable spans (website=”evidence_review”, website=”audit”, website=”full_review”) and all surrounding markup, CSS, and template comments — including the template’s “BENEFTIS” comment typo — are unchanged from [qrs_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 mapped to the QRS is empty: all four benefit tiers, all four risk tiers, the contraindication list, the interaction list, Protocol and Monitoring carry content.
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 relative to meals”, “Formulation” and all four interaction labels (“Drugs absorbed between gut cells”, “Non-steroidal anti-inflammatory drugs”, “Oral proteolytic enzyme supplements”, “Barrier-supporting supplements”) are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No ER-sourced label is altered; the Time-to-Effect labels have no bold counterpart in the ER prose and are the minimal descriptors required by the template cells.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Scan for emoji code points returns nothing; the ER’s tier emoji and “⚠️ Conflicted” markers were dropped, tiers conveyed by the CSS palette and bold “High:/Medium:/Low:/Speculative:” labels.
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 compressed to the minimum the completeness items allow: tiers collapsed to one line each, gate items to bare facts, marker “Why” cells to single clauses, and the ER’s 11 mandated biomarkers (14.2) kept as short rows rather than dropped.

---

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 opens at line 2, immediately after “<!doctype html>” on line 1, and closes at line 14 before any other markup.
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 outside the block.
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 are duplicated into a 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 nine values are trimmed; only duration: "00:04" is quoted, which its colon requires.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: larazotide_2026-0912-0234_Opus_ER.md, matching the ER’s own filename frontmatter.
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.11, 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-0912-0534, correct format.
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” is nickname plus version with no context-window or other qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: larazotide_2026-0912-0234_Opus_QRS.html, identical to 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., & for &)	🟢	Line 22: “Larazotide for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic 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., & for &)	🟢	Line 417: “Larazotide for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/12/2026” from qrs_creation_date: 2026-0912-0534.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter 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 holds only the title and the template’s fixed subline; the ER’s “Also known as” list was not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Six clauses drawn in order from ER Conclusion lines 460-464: what it is, what it does, the failed trial, no lining protection, benign safety, inverted dose-response.
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 clause maps to a separate ER Conclusion sentence (lines 460, 462, 462, 462, 464, 464).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronym appears; “tight junctions” is rendered as “the seals between intestinal lining cells” and “peptide” as “protein fragment”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers only to “the largest trial in people already avoiding gluten” with no name, year, size, or p-value.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind in the lede.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from the “Populations who should avoid Larazotide” list at ER lines 304-310.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Seven ER bullets map one-to-one onto seven <li> items with none added or dropped.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 570-579: seven discrete <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.	🟢	The ER’s trailing em-dash clauses (“— excluded from every trial, no reproductive safety data”, “— youngest published exposure was age 3 under an emergency authorization”) are stripped and no dash clause remains; the “People with” prefixes are dropped.
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).	🟢	“(Type I or Type II)” is preserved on the refractory-celiac item, and the ≥3× ULN, ≥2× ULN, ≤50 mL/min/1.73 m² and “under 7 years” thresholds are all carried.
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 contraindication bullets contain 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 seven such populations, and the section is correspondingly populated rather than 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 six items come from the interaction bullets at ER lines 290-300.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All six ER interaction bullets are present; none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 587-602: six discrete <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.	🟢	Mechanism, severity, and mitigation sentences from each ER bullet are stripped, as is the “— injectable antibiotics” gloss on gentamicin; no dash clause survives.
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 named agents are preserved: atenolol, metformin, gentamicin; ibuprofen, naproxen, aspirin; bromelain, papain, serrapeptase; zinc carnosine, L-glutamine, colostrum, quercetin.
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 contain 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 six such interactions, and the section is correspondingly populated rather than 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 come from the ER Therapeutic Protocol bullets at lines 334, 336 and 338.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, meal timing, and formulation are the three executable levers; the remaining ER bullets (competing approaches, half-life, sex, age, baseline markers, pre-existing conditions) are contextual rather than actionable.
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 Therapeutic Protocol section provides eleven bullets, so 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 spans are populated: “0.5 mg three times daily”, “15 minutes before each main meal”, “Delayed-release enteric beads”, each with an ER-derived sub-line.

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	🟢	1-2 weeks for symptom differences (ER line 388), 6 weeks for the antibody readout (ER line 166), 12 weeks as the decisive endpoint (ER lines 388 and 414).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High → Medium → Low: symptom flares (High tier), antibody response (Medium tier), persistent symptoms (Low tier).
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 at least three distinct time-to-effect windows, so 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 spans are populated with ER-derived labels, values and explanatory sub-lines.
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 time-to-effect information at lines 388, 166 and 414, so the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All nine benefit items trace to the ER Expected Benefits headings at lines 154-202.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 541-560.
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 ER benefit headings; the ER’s Magnitude paragraphs, confidence intervals, p-values, sample sizes and sponsor caveats are all omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear 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, so no span needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All seven risk items trace to the ER headings at lines 228-270.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 614-631.
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 lists only ER risk headings; the 5.8% incidence, 17-of-86 headache count, risk ratios and sponsor commentary are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear 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.	N/A	All four ER risk tiers contain items, so no span needed hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Marker names, targets and “Why” cells are taken from the ER Monitoring Protocol & Defining Success table at lines 418-428, with the ER’s “Why Measure It?” wording carried verbatim.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER biomarkers present in ER order: tTG-IgA, DGP, total IgA, fecal GIP, ferritin, 25-hydroxyvitamin D, vitamin B12, ALT, eGFR, hs-CRP, serum zonulin.
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.	🟢	Lines 794-798 reproduce the ER cadence at line 414: baseline, weekly symptom scoring for four weeks, full repeat at 12 weeks, then every 6 months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items come from the ER’s qualitative marker list at lines 432-436.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five listed: symptom frequency/severity, symptom-free days, tiredness and headache, confidence eating outside the home, cognitive clarity and mood — with the ER’s trailing commentary and citation stripped.

Issues 12/09/2026 05:41

Pass rate 100.00%. No issues found.