Audit: QRS - Branched-Chain Amino Acids for Health & Longevity

Audit conducted on 07/09/2026 05:49 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. 🟢 Protocol cells trace to ER lines 352–356; time-to-effect to ER line 401; benefits/risks to the ER H3 headings; gates to ER lines 307–330; monitoring table and qualitative list to ER lines 429–448.
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. 🟢 “Higher blood levels travel with later metabolic and heart disease” preserves the ER Conclusion’s associational hedge; “no strength or muscle-size effect is established” mirrors ER line 472.
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 qualifiers (“any dose”, “outside physician supervision”, “unless doses separated by at least two hours”) retained at ER strength.
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 from ER Key Interactions & Contraindications; benefits from Expected Benefits; risks from Potential Risks & Side Effects. No modifying-factor content is surfaced as 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. 🟢 No PMIDs, NCT identifiers, author names or brand names in the QRS; drug names (metformin, glipizide, glyburide, prednisone, dexamethasone, levothyroxine) all appear in ER lines 309–313.
1.6 The QRS does not introduce new attributions. 🟢 The ER’s “Wolfe and Kresser argue for” attribution (line 356) is stripped rather than replaced; no attribution added anywhere.

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, population-split framing of the ER Conclusion carried through.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and thresholds paired with plain-language explanation.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 No prescriptive second-person instruction anywhere on the sheet.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Monitoring cadence and protocol cells are stated descriptively, not as directions to a patient.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommended”, “advised”, or “should” constructions in the document’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No occurrence of “you” or “your”.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are only those the ER itself uses as marker or condition names.
2.8 Information is presented in a concise and very compact manner 🟢 Benefits and risks reduced to semicolon-separated headings; gate items reduced to key fact plus qualifier.
2.9 It DOES NOT address the reader directly 🟢 Confirmed; no direct address or imperative verbs aimed at the reader.
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 biomarker targets and a specialist amino acid panel assume a proactive, self-directed 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. 🟢 Fasting amino acid panel, plasma ammonia and DXA-based lean mass index retained despite cost and inconvenience.
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 simplified general-population framing; functional rather than conventional laboratory ranges used.
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 makes the population split explicit — benefit concentrated in liver disease, minimal in healthy well-fed training adults.
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. 🟢 No occurrence of “anti-aging”; header 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 Risks card uses “Gastrointestinal upset”; the At-A-Glance plain-language rendering is required by item 7.4 and matches the ER Conclusion wording at line 474.

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 fixed strings match [qrs_template] byte-for-byte (QRS lines 446, 492, 534, 564, 580, 602, 632, 636–638, 756).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Set comparison against the template shows every named span present; only the repeatable marker_#_* and qualitative_item_# placeholders are expanded to numbered instances, as intended.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Whitespace-normalised diff against the template shows differences confined to variable regions and the metadata block; CSS, structure, website= spans and footer disclaimer are 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” N/A No source ER section mapped into the QRS is empty.
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 sports-nutrition protocol”, “Clinical liver protocol” and “Complete amino acid alternative” reproduce the ER bold labels at lines 352, 354, 356 verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Time-to-effect labels are the literal subject phrases of ER line 401 (“Soreness reduction”, “Nutritional benefits in liver disease”, “muscle size”); marker names match the ER table verbatim.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s ⚠️ Conflicted markers are stripped and tiering is carried by the CSS palette and bold tier 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. 🟢 Benefits and risks collapsed to headings only, gate items stripped of rationale and glosses, protocol reduced to three cells; no section carries ER prose beyond its 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. 🟢 Single comment spanning lines 2–14, immediately after the doctype at 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 opener.
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 echoed by a visible 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 values trimmed; only duration: "00:03" 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: branched_chain_amino_acids_2026-0907-0219_Opus_ER.md, matching the ER frontmatter filename.
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 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-0907-0537, 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 file’s actual name on disk.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Re-verified across all nine keys, including the appended git_user and git_issue.

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., &amp; for &) 🟢 Line 22: “Branched-Chain Amino Acids 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 (e.g., &amp; for &) 🟢 Line 417 matches the ER canonical_topic with the ampersand encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/07/2026, correctly derived from 2026-0907-0537.
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 contains only the title and the template 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 🟢 Compresses ER lines 472–474: what it is, where it works, where it does not, the observational counterweight, and the main adverse event.
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. 🟢 Each of the five clauses maps to a distinct sentence in ER lines 472–474.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 “Confusion from liver failure” replaces hepatic encephalopathy; “stomach upset” replaces gastrointestinal upset; no acronyms used.
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 effect estimates of any kind.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items map to the ER “Populations who should avoid” list at lines 325–330.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-list populations are present; none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> elements inside the stop_items span (lines 567–575).
8.4 Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. 🟢 ER glosses (“the most severe grade of liver failure”, “a progressive motor neuron disease”) and rationales (“on the basis that supplemental doses are entirely unstudied”, “on precautionary grounds”) are stripped; no dash-trailing 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 (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 “any dose”, “at least two hours”, “Child-Pugh Class C”, “stage 4 or worse”, “below 30 mL/min/1.73 m²” and “outside physician supervision” 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 identifies six such populations and the section is correspondingly populated.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All seven items map to the ER interaction bullets at lines 309–321.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All seven non-contraindication interactions present; the levodopa bullet (ER line 307) is correctly excluded because it appears among the contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Seven <li> elements inside the caution_items span (lines 583–592).
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 ER bullet body (mechanism, monitoring rationale) is dropped; the ER’s inline gloss “insulin-releasing oral drugs such as” is removed while the drug names are kept.
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). 🟢 Named examples (metformin, glipizide, glyburide, insulin, prednisone, dexamethasone, levothyroxine) and severity tags (“caution, monitor”, “caution, separate doses”, “additive, redundant”, “caution, minimal”) retained.
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 identifies eight interactions and the section is correspondingly populated.
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 map to ER Therapeutic Protocol lines 352, 354 and 356.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The two competing dosing regimens plus the complete-amino-acid alternative are the ER’s three dose-bearing bullets; the remaining bullets are modifiers rather than regimens.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER supplies three distinct actionable aspects, 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. 🟢 Doses (“5–10 g total, 2:1:1 ratio”, “~12 g daily as granules”, “10–15 g essential amino acids”) and timing detail all match the ER numerically.

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 🟢 Reproduces the three statements in the ER “Time to effect” bullet at line 401.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Soreness reduction (High tier, pooled effect size 0.73) precedes the cirrhosis nutritional benefit (High tier, SMD 0.52), with the no-effect muscle-size entry 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 time-to-effect aspects, 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. 🟢 “24–72 hours”, “4–12 weeks” and “No effect expected” match ER line 401 exactly.
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 🟢 All eight entries are the ER’s H3 benefit headings from lines 157–207.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 536–557).
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. 🟢 Headings only; all Magnitude figures, net readings and mechanistic paragraphs omitted.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefits entry.
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 The ER populates all four tiers (3 high, 2 medium, 2 low, 1 speculative).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All ten entries are the ER’s H3 risk headings from lines 231–289.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 604–626).
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; frequencies (12% vs 3%), risk ratios and mechanism paragraphs 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 risks entry.
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 The ER populates all four tiers (1 high, 4 medium, 2 low, 3 speculative).

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 All rows map to the ER biomarker table at lines 429–440.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All ten ER biomarkers present — fasting insulin, HOMA-IR, HbA1c, fasting plasma branched-chain amino acids, plasma ammonia, alanine aminotransferase, blood urea nitrogen, estimated glomerular filtration rate, creatine kinase, appendicular lean mass index — with targets and rationales matching the ER verbatim.
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 746–750 reproduce the cadence stated in ER line 427 (12 weeks, then 6–12 months, annual body composition, ammonia at 12 weeks at higher clinical doses).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All five items map to the ER qualitative marker list at lines 444–448.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers present and reproduced verbatim; none omitted or added.

Issues 07/09/2026 05:49

Pass rate 100.00%. No issues found.

Issues 07/09/2026 05:42

  1. 1.3 — At-A-Glance overstates null finding: [at_a_glance] (line 437) asserts “strength and muscle size are unchanged”, strengthening the ER Conclusion’s “no effect on strength or muscle size has been established” (ER line 472) and contradicting the ER’s Low-tier benefit “Preserved Muscle Mass and Strength” (ER line 191).

Fixes 07/09/2026 05:42

  1. 1.3 — At-A-Glance overstates null finding: Replaced “strength and muscle size are unchanged” with “no strength or muscle-size effect is established” in [at_a_glance], restoring the ER Conclusion’s not-established framing; the section remains within the 60-word budget.