Audit: QRS - Carnivore Diet for Health & Longevity

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

Iterations

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
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 (standard approach, protein/fat ratio, adaptation period); time cells to ER Practical Considerations “Time to effect”; benefit and risk lines to the ER H4 headings; gates to Key Interactions & Contraindications; all 17 markers and 8 qualitative items to Monitoring Protocol & Defining Success.
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 retains “though the evidence is surveys of people who chose the diet” and “No long-term comparison trials exist”, mirroring the ER Conclusion.
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 keep the ER’s absolute framing; the SGLT2 entry keeps “that cannot be discontinued”.
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.	🟢	Gates draw only on the ER Key Interactions & Contraindications section; no modifying-factor content is promoted into a gate or a 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 PMIDs, NCT IDs or expert names carried over; every named drug (empagliflozin, dapagliflozin, canagliflozin, glipizide, glimepiride, gliclazide, furosemide, hydrochlorothiazide, lisinopril, atorvastatin, rosuvastatin, ezetimibe, omeprazole, pantoprazole, ibuprofen, naproxen, semaglutide, tirzepatide) appears in the ER for the same interaction.
1.6	The QRS does not introduce new attributions.	🟢	No attributions present; the ER’s named practitioners are not carried over.

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.	🟢	Neutral, evidence-weighted register matching the ER throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Targets and tiers are stated without alarm or promotion.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements are descriptive (“Lipid changes stabilise here”), not prescriptive.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No directives to the reader; monitoring cadence describes the ER’s protocol rather than instructing.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should” or “must” in the document body.
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	🟢	Technical terms are confined to biomarker names and condition names where no plain equivalent exists.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, benefit/risk lines and marker rationales are single clauses with no mechanistic padding.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; 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.	🟢	Functional-range targets and a 17-marker panel assume a proactive, testing-oriented 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.	🟢	Coronary imaging, DEXA and red-cell magnesium testing are retained without hedging on cost or effort.
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 toward 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 flags that the cholesterol rise is largest in the leanest, the ER’s audience-specific signal.
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 appear; the title uses “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.	🟢	Formal terms used throughout (“glycaemic control”, “apolipoprotein B”, “nephrolithiasis”); the lede’s “blood sugar control” is the ER Conclusion’s own wording and is not route-of-administration phrasing.

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 heads, tier labels and column headers match the template byte-for-byte (lines 440, 477, 519, 539, 555, 576, 595, 599–601, 802).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Set comparison against the template returns no missing variable; the repeatable marker_#_* and qualitative_item_# spans are expanded to 17 and 8 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Normalised diff against the template shows the head, CSS block, footer disclaimer and all non-variable markup are byte-identical.

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 ER Expected Benefits High tier carries explanatory prose rather than an empty-state phrase, and is handled under 12.5.
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.	🟢	“Standard approach”, “Protein and fat ratio”, “Adaptation period”, “Warfarin”, “Lithium”, “Over-the-counter medications”, “Supplement interactions”, “Supplements with additive effects”, “Other interventions” all reproduce the ER bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Where the ER supplies a label it is reused verbatim; the three time-to-effect labels derive from the ER’s single “Time to effect” bullet, which supplies no per-item label (see 11.4).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Zero emoji characters in the file; the ER’s “⚠️ Conflicted” markers were stripped.
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 available condensation lever was applied: the ER monitoring table’s “Context/Notes” column is dropped entirely, magnitudes and citations are removed from all tiers, and gate items are reduced to the key fact. Remaining volume is mandated by 8.2, 9.2, 14.2 and 15.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.	🟢	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 --- at line 3, closing --- at 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 echoed into the header or footer.
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 values trimmed; only duration: "00:02" is quoted, which is required 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: carnivore_diet_2026-0922-0642_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-0922-0933, 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” = nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename carnivore_diet_2026-0922-0642_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 or unnecessary quoting.

6. Page Title & Header

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &)	🟢	Line 22: “Carnivore Diet for Health & Longevity - Quick Reference Sheet”; ampersand correctly entity-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: “Carnivore Diet 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: “09/22/2026”, the correct reformatting of 2026-0922-0933.
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.	🟢	Header holds only the title and the template’s standard subline; the ER’s “Also known as” line is 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 condenses the four ER Conclusion paragraphs into the three mechanisms, the thin benefit evidence, and the lipid cost.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Mechanism triad from ER line 501; benefits and survey caveat from line 503; cholesterol rise in the leanest from line 505; absence of long-term trials from line 507.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; uses “fat-derived fuel”, “blood sugar control”, “blood cholesterol” rather than ketosis, glycaemic control or LDL.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years or sample sizes.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric results; “rises sharply” is qualitative.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All nine items trace to the ER “Populations who should avoid Carnivore Diet” list (ER lines 334–342).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-list bullets are represented; the two compound bullets are split into separate items (urea-cycle/fatty-acid-oxidation disorder, SGLT2 inhibitors), so nothing is lost.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 542–550, nine discrete <li> elements.
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.	🟢	Each item is a single noun phrase; no dashes introduce trailing clauses; the ER’s “(kidney stone disease)” gloss is dropped as redundant.
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).	🟢	“≥190 mg/dL”, “stage 3b or worse (eGFR below 45 mL/min/1.73 m²)”, “Child-Pugh Class B or C”, “without specialist supervision” and “that cannot be discontinued” 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.	🟢	The ER names seven avoid categories, 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 nine items trace to the ER bullets at lines 316–332.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Nine of the ER’s ten interaction bullets are carried; the SGLT2 inhibitor bullet is correctly excluded because it appears in Contraindications. Order matches the ER.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 558–566, nine discrete <li> elements.
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 reduces to label plus consequence (“severe hypoglycaemia”, “altered anticoagulation”, “symptomatic hypotension”); the ER’s mechanism and mitigation sentences are stripped and no dash 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).	🟢	Every ER example-drug list is preserved, as is the “above 1,000 mg daily” vitamin C threshold.
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.	🟢	The ER names ten 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 derive from the ER Therapeutic Protocol bullets at lines 364, 372 and 386.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard approach, protein-and-fat ratio and adaptation period are the three executable parameters; the remaining ER bullets are variants or population modifiers rather than implementation actions.
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 more than three actionable aspects, so no set is unused.
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 populated (lines 444–472); values and subs paraphrase the ER bullets without adding 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	🟢	Weight/glycaemic, gastrointestinal/skin and lipid are exactly the three windows the ER’s “Time to effect” bullet supplies (ER line 418).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Weight and glycaemic control are both Medium-tier benefits and lead; gastrointestinal/skin follows (Medium and Low tiers); lipid change, which carries the High-tier risk rather than a benefit, is placed last.
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, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated (lines 483–511); the 1–2, 2–6 and 8–12 week windows match the ER verbatim.
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every line reproduces an ER Expected Benefits H4 heading.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present 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.	🟢	Semicolon-separated headings only; the ER’s Magnitude lines, mechanisms and caveats are all dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit line.
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.	🟢	The ER states no benefit reaches High; line 521 sets style="display: none" on [benefits_high] with no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Every line reproduces an ER Potential Risks & Side Effects H4 heading.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 578–589.
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.	🟢	Headings only; the ER’s hazard ratios, Net reading paragraphs and “⚠️ Conflicted” markers are stripped.
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 line.
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 risk tiers carry items in the ER, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table rows map one-to-one onto the ER Monitoring Protocol & Defining Success biomarker table (ER lines 452–468).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 17 ER rows present in ER order, including the two imaging measures (coronary artery calcium score, DEXA bone mineral density); targets reproduce the ER “Optimal Functional Range” values exactly.
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 796 carries baseline, 4-week, 12-week, 6-monthly and 2–3-year imaging intervals, matching ER lines 446–448.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All eight items come from the ER’s qualitative-marker list at lines 472–479.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All eight ER qualitative markers present verbatim and in ER order (lines 805–827).

Issues 22/09/2026 09:35

Pass rate 100.00%. No issues found.