Audit: QRS - Licorice Root for Health & Longevity

Audit conducted on 27/08/2026 13:15 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 protocol cell, time-to-effect cell, benefit, risk, gate item, biomarker row, cadence sentence and qualitative marker traces to a named ER passage.
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.	🟢	No ER empty-state or hedged phrasing is carried into the QRS in altered form; hedges such as “Rarely beyond 4–6 continuous weeks” mirror the ER.
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”).	🟢	Pregnancy stays a contraindication; digoxin, described in the ER as “Absolute contraindication in practice”, is placed in Contraindications rather than downgraded to a caution.
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 the ER Key Interactions & Contraindications section; benefits and risks draw only from their own ER tiers. No modifying factors appear.
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 appear anywhere in the QRS.
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.	🟢	Wording is lifted or lightly compressed from the ER throughout, preserving its measured, mechanism-first register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Ranges, thresholds and targets are given without alarm or promotion.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements describe practice and evidence rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; monitoring and cadence are stated descriptively.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No recommending or advising verbs appear.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker names and drug classes, where precision is required.
2.8	Information is presented in a concise and very compact manner	🟢	Gate, benefit and risk items are reduced to ER headings or key facts with rationale stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for “you”/”your”.
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 biomarker targets, home blood-pressure averaging and red-cell magnesium assume a proactive, self-tracking 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.	🟢	Cadence assumes repeat laboratory panels, renin/aldosterone draws and daily weighing.
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.	🟢	The monitoring and cycling burden is well 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 leads with the whole-root/processed-form split, the decision that matters for this audience, and closes by deflating the ageing claim.
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.	🟢	“Ageing claims” is used; the string “anti-aging” does not occur.
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.	🟢	Register matches the ER; the few plain words (“puffiness”, “worms”) are the ER’s own wording, retained under item 1.1.

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 headings, gate headings, tier labels and column headers match the template byte for byte.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables are present; marker_#_* and qualitative_item_# are expanded to 10 and 6 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans and the page_title wrapper are unchanged; the entire style block and all structural markup 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 source ER section mapped by this template 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.	🟢	“Whole licorice root, conventional herbal dose”, “Deglycyrrhizinated licorice for digestive use” and “Best time of day” are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Biomarker names and protocol labels match the ER wording exactly.
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 were correctly 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 section is condensed rather than extended: benefits and risks are reduced to ER headings, gate items to bare facts, and the ER’s two-paragraph monitoring narrative to a single cadence sentence.

---

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 the doctype 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 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 entirely in an HTML comment; no metadata value is repeated in 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.	🟢	Only duration: "00:03" 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: licorice_root_2026-0827-0927_Opus_ER.md.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md badge version.
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-0827-1308.
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 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.	🟢	All nine keys carry trimmed, correctly quoted or unquoted values.

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: “Licorice Root 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., & for &)	🟢	Line 417: “Licorice Root for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/27/2026”, correctly derived from 2026-0827-1308.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”.
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 carries only the title and the template subline; the ER’s “Also known as” line 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	🟢	Compresses the Conclusion’s four paragraphs into the operative distinction, the harm list, and the status of the ageing claim.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to the ER Conclusion (lines 554–556) and, for the harm list, to the ER High-risk tier.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“Glycyrrhizin”, “11β-HSD2” and “mineralocorticoid” are all replaced by plain descriptions (“the sweet compound”, “the enzyme switching off the body’s main stress hormone”).
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial, author, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric result of any kind appears.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All ten items come from that section (ER lines 359–391).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All nine entries of the ER’s “Populations who should avoid Licorice Root” list, plus digoxin, which the ER calls an “Absolute contraindication in practice”.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Ten <li> elements inside the stop_items span (lines 577–592).
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 clauses (“— glycyrrhizin crosses the placenta and enters breast milk”, “, pending human safety data”) are stripped; no dash-trailing content remains.
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).	🟢	The 140/90 mmHg threshold, NYHA Class II, CKD stage 3 with the 60 mL/min/1.73 m² cut-off, Child-Pugh B/C and the 3.5 mmol/L potassium floor are all retained; only the ER’s glossing phrase “a measure of kidney filtering capacity” was trimmed.
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 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 nine items come from the ER’s interaction bullets (lines 361–379).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten ER interaction bullets are present except digoxin, correctly excluded because it is carried in Contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine <li> elements inside the caution_items span (lines 600–619).
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 rationale sentence (“Licorice directly opposes them…”, “Licorice may accelerate warfarin clearance…”) is stripped; only the drug or class name remains.
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 example drugs are preserved throughout (hydrochlorothiazide/indapamide/furosemide; prednisone/hydrocortisone; senna/bisacodyl; ibuprofen/naproxen; caffeine/yohimbine/bitter orange/dandelion/juniper; DHEA/adrenal glandulars).
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 numerous 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 derive from the ER Therapeutic Protocol bullets (lines 415, 417, 427).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two preparation-and-dose decisions that carry the whole risk/benefit split, plus timing — the three levers a user must actually set.
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 and 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 fields carry ER-derived content; the 1–5 g, 380–760 mg and morning-dosing values are ER verbatim.

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	🟢	Postoperative sore throat, digestive symptom relief and mouth-ulcer healing are the only three ER benefits with an explicit onset window.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Sore throat leads on the only quantified magnitude in the group (risk ratio 0.44, standardised mean difference −0.69); dyspepsia and ulcer healing follow, neither carrying a reported effect size.
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	Three distinct time-to-effect aspects exist and 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.	🟢	The 7–14 day and 4–8 day windows and the 24-hour post-surgical assessment are all 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 provides 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 seventeen entries are ER Expected Benefits sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated, each matching its ER tier exactly (5 / 7 / 3 / 2 items).
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.	🟢	Reduced to the ER sub-heading text alone; every Magnitude paragraph, mechanism sentence and sponsorship caveat is 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 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 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 nine entries are ER Potential Risks & Side Effects sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated, each matching its ER tier exactly (3 / 1 / 4 / 1 items).
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.	🟢	Reduced to the ER sub-heading text alone; the 11β-HSD2 mechanism, case-report detail and pooled figures are all dropped.
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 tiers carry items in the ER, so no span needed hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from the ER Monitoring Protocol & Defining Success biomarker table (lines 508–519).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER rows are present, in ER order, with the Optimal Functional Range and Why Measure It columns carried over unchanged.
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 810–815 condense the ER’s cadence paragraph, retaining baseline/2-week/4-week/3-month intervals, the week-1 escalation and the deglycyrrhizinated exemption.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from the ER’s “the qualitative markers tracked are” list (lines 523–528).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, in ER order and ER wording.

Issues 27/08/2026 13:15

Pass rate 100.00%. No issues found.