Audit: QRS - Lactoferrin for Health & Longevity

Audit conducted on 28/08/2026 03:11 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	82
Failed	0
N/A	11
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.	🟢	Protocol cells trace to ER Therapeutic Protocol (lines 373, 383, 387); time-to-effect cells to ER line 429; benefits/risks to the ER tier headings; gates to ER lines 323–353; markers and cadence to the ER Monitoring Protocol & Defining Success table and prose.
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.	🟢	The ER’s hedged iron reading (“gentler digestion rather than better numbers”) and its animal-only ageing caveat are both carried into [at_a_glance]; hepcidin’s “No established target range” is preserved in marker_7_target.
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”).	🟢	Contraindications remain absolute; interaction categories keep the ER’s own strength words (“monitor”, “caution”, “additive and intended”).
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.	🟢	[stop_items] draw only from the ER “Populations who should avoid Lactoferrin” list; [caution_items] only from the ER interaction bullets; no Benefit- or Risk-Modifying Factor is promoted into a gate.
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 carries no PMIDs, NCT identifiers, author names, or brand names at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

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 and deflationary where the ER is (iron comparison, ageing claims), affirmative only where the ER grades High.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Tiered benefits, concrete thresholds, and actionable dosing cells give the reader material to act on without overselling.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Interaction items state separations and categories descriptively rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative directed at a reader; gate items are stated as conditions and separations, not prescriptions.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “advised”, or “should” constructions in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Every abbreviation in the Monitoring table is introduced with its full term (TSAT, MCV, hs-CRP, TIBC); the At-A-Glance text is fully non-technical.
2.8	Information is presented in a concise and very compact manner	🟢	Benefits and risks are reduced to bare tier headings; interaction items are stripped to drug class, examples, and the separation rule.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by scan: no “you”/”your” in the document.
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.	🟢	Functional marker ranges, hepcidin as an optional research assay, and formulation detail (enteric-coated) all assume a proactive, self-monitoring reader.
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.	🟢	Fasted dosing 30–60 minutes before breakfast, split morning/evening dosing, and a repeated laboratory panel are all presented without softening.
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.	🟢	Seven-marker monitoring panel and multi-drug separation windows are beyond general-population framing.
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] closes on the longevity question specifically (“Ageing claims rest on animal work”), and the Speculative benefit tier retains the senescence/longevity item.
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 “Ageing claims” and “longevity pathways”; the string “anti-aging” does not appear.
2.15	The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“Visceral fat”, “gingival”, “transferrin saturation”, “adjunctive antitumor activity” throughout; the plain wording in [at_a_glance] is mandated by item 7.4 and taken from the ER Conclusion.

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 headings, gate headings, and column headers match the template byte-for-byte; visible tier labels are unchanged.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Structural diff against [qrs_template] shows every template span present; the repeating marker_#_* and qualitative_item_# spans are expanded to marker_1–7 and qualitative_item_1–6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three <span website="..."> elements (evidence_review, audit, full_review), the whole <style> block, the override stylesheet link, and the footer disclaimer 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 section of the ER is empty; the only absent tier (Risks / High) is governed by item 13.5, which explicitly forbids 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 labels (“Standard dose range”, “Best time of day”, “Single versus split dosing”) and all twelve interaction labels reproduce the ER bold labels verbatim, including the parenthetical drug lists.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels (“Visceral fat”, “Gingival and acne endpoints”, “Iron markers”) use the ER’s own wording from Practical Considerations; marker names match the ER biomarker table.
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 ⚠️ markers were all dropped.
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 over-full section is condensed rather than spilled: Protocol reduces thirteen ER bullets to three cells, Benefits and Risks collapse to bare tier headings, interactions are stripped of all mechanism, and [at_a_glance] is held to the 60-word ceiling.

---

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢	Lines 2–14; the comment opens 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 descriptive text on line 2 precedes 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; no metadata value is repeated in the header, footer, or body.
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:04" is quoted, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: lactoferrin_2026-0828-0001_Opus_ER.md, matching the audited ER.
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.7.02, matching the version badge of [qrs_prompt].
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-0828-0303, 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” is a single word with 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 trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual file name lactoferrin_2026-0828-0001_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.	🟢	Re-verified across all nine keys; no stray whitespace and no 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., & for &)	🟢	Line 22: Lactoferrin for Health & Longevity - Quick Reference Sheet, with the 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 &)	🟢	Line 417: Lactoferrin for Health & Longevity, matching the ER canonical_topic.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 08/28/2026, the correct reformatting of 2026-0828-0303.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: 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.	🟢	The header holds only the title and the template 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	🟢	Line 433 tracks the ER Conclusion (lines 496–498) in order: mechanism, strongest indication, weaker signals, the iron comparison, the ageing caveat.
7.2	[at_a_glance] is no longer than 60 words	🟢	Exactly 60 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Iron binding and denial to surface bacteria (ER 496), H. pylori as strongest evidence (ER 498), the four Medium-tier signals (ER 498), the iron-tablet comparison (ER 498), animal-only ageing data (ER 498).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “the stomach bacterium behind ulcers” replaces Helicobacter pylori, “stomach and bowel upset” replaces gastrointestinal illness, “abdominal fat” replaces visceral fat.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, sample size, or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Comparative claims are qualitative only (“gentler digestion, not better numbers”).

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the “Populations who should avoid Lactoferrin” list at ER lines 347–353.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 542–546: five 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 leading “People with” is dropped throughout and the recombinant-form aside (“a yeast-derived recombinant human form avoids the milk proteins”, ER 349) is correctly stripped; 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).	🟢	“(bovine-derived products)”, “HFE C282Y homozygotes”, the 45% / 300 ng/mL / 200 ng/mL thresholds, and “(hemoglobin below 10 g/dL)” are all 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 uses no ranking notation inside parentheses in this section.
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.	N/A	The section is populated; the ER names five avoid-populations.
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	🟢	Sourced from the twelve interaction bullets at ER lines 323–345.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All twelve ER interaction bullets are present in ER order, with no overlap with the five contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 554–565: twelve 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.	🟢	Every mechanistic sentence is stripped (e.g. ER 323’s “Iron mobilised or carried alongside lactoferrin can bind thyroid hormone” reduces to “separated by at least four hours”); 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 five ER drug-example lists survive intact, as do the four-hour and two-hour windows and the “two-hour separation”.
9.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER uses no ranking notation inside parentheses in this section.
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.	N/A	The section is populated; the ER names twelve interactions.
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 the ER Therapeutic Protocol bullets at lines 373, 383, and 387.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose range, timing relative to food, and single-versus-split dosing are the three execution decisions a reader must make; the ER’s named protocol variants and its genotype/sex/age notes 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 supplies well over three actionable aspects; 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 carry ER-derived content, including the 1.5–3 g oncology range and the pepsin/calcium rationale for fasted dosing.

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	🟢	Visceral fat (8 weeks), gingival and acne endpoints (10–12 weeks), and iron markers (4–12 weeks) are taken from ER line 429; the fourth, the 12-month colorectal signal, sits in the lowest benefit tier.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Visceral fat and the gingival/acne endpoints are Medium-tier benefits, iron-deficiency anemia is Low-tier and ER-flagged as conflicted, so the ordering runs correctly from higher to lower.
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 names four distinct time-to-effect windows; 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; the enteric-coating condition on the visceral-fat result reflects ER lines 165 and 259.
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	🟢	Every item maps to an ER Expected Benefits sub-heading, tier for tier.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans are present and populated at lines 521–532.
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 entry is the bare ER sub-heading; the odds ratios, participant counts, and manufacturer-conflict notes from the ER body are all absent.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any of the four tiers.
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 benefit tiers carry items in the ER, 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 items map to ER sub-headings at lines 271–305.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present at lines 577–588.
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 entry is the bare ER sub-heading; the 555-patient trial detail and the −1.2 g/dL magnitude are correctly omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any tier.
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.	🟢	Line 577: risks_high carries style="display: none" and an HTML comment recording the ER basis (“No risk reaches High”, ER line 267); no empty-state text is rendered.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows and cadence both trace to the ER Monitoring Protocol & Defining Success section (lines 455–467).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven rows of the ER biomarker table are carried over in order: ferritin, TSAT, hemoglobin, MCV, hs-CRP, TIBC, serum hepcidin, each with the ER’s own range and rationale.
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty.	🟢	Line 685 reproduces the ER’s schedule: baseline, 8–12 weeks, six months, then every 6–12 months, with inflammation markers at 12 weeks.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the qualitative-marker list at ER lines 471–476.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, verbatim and in ER order.

Issues 28/08/2026 03:11

Pass rate 100.00%. No issues found.