Audit: QRS - Red Clover Extract for Health & Longevity

Audit conducted on 17/08/2026 00:47 using AI4L / Opus 5

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, gate item, benefit, risk, marker row and qualitative item traces to a named ER passage (Protocol, Practical Considerations, Key Interactions & Contraindications, 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.	🟢	The ER’s “⚠️ Conflicted” markers are carried through as “, conflicted” on hot flash frequency, lumbar spine bone loss and estrogenic stimulation; “Speculative” tiers are preserved.
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 and lactation remain an absolute contraindication; endocrine cancer therapy remains “outside oncology supervision”; the CYP450 item keeps the ER’s “low concern”.
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 come only from `Key Interactions & Contraindications`, benefits only from `Expected Benefits`, risks only from `Potential Risks & Side Effects`; no 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.	🟢	No PMIDs, citations or NCT identifiers appear; the only brand names, Promensil and Menoflavon, are the ER `Protocol` extract-selection brands.
1.6	The QRS does not introduce new attributions.	🟢	No author, institution or trial attribution appears anywhere in the sheet.

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, evidence-first register matching the ER; conflicted findings are flagged rather than smoothed.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and dose ranges are paired with plain-language rationale in the At-A-Glance and `sub` cells.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what trials used and what was measured, not as instructions to the reader.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Gate items are stated as decision conditions carried verbatim from the ER, not as directives from the sheet’s own voice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Protocol cells describe the schedule “used in the trials”; no recommending verbs in the sheet’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun occurs anywhere in the populated spans.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker names carried from the ER monitoring table; the At-A-Glance is jargon-free.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, benefits and risks are reduced to key facts; monitoring “why” cells are single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct address in any populated span.
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.	🟢	The sheet assumes willingness to track a 12-marker panel, run a two-week symptom baseline and audit total isoflavone load.
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.	🟢	Split twice-daily dosing, serial lipid and liver panels and annual endometrial surveillance are presented without hedging on 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.	🟢	Functional ranges (ALT < 25 U/L women, TSH 0.5–2.5 mIU/L) are tighter than conventional cut-offs, addressing an optimizing audience.
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢	The At-A-Glance names both the conditional nature of the vasomotor effect and product variability, the two facts that determine whether this audience gets any effect at all.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	“anti-aging” does not occur; the 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“adverse events”, “transaminases”, “neuraxial procedure” are used; “heat surges” and “dummy treatment” in the At-A-Glance are the ER’s own `Conclusion` wording required by the plain-language rule 7.4.

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 present verbatim at lines 446, 492, 542, 635, 663, 855, 571, 601, 667–669 and in the tier `<strong>` labels.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	76 `data-qrs-var` spans present, covering every named variable in this checklist: page_title, header_, at_a_glance, action_1–3, time_1–3, benefits_, stop_items, caution_items, risks_, marker_1–12_, monitoring_cadence, qualitative_item_1–6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The template’s `website="evidence_review"`, `website="full_review"` and `website="audit"` spans, the footer disclaimer and the full stylesheet are untouched.

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 relied on by 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.	🟢	Protocol cells use “Standard dose”, “Single versus split dosing” and “Extract selection” verbatim from ER lines 349, 361 and 351; monitoring row labels match the ER biomarker table column verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels (“Vasomotor improvement”, “Lipid changes”, “Bone effects”) use the ER’s own nouns from the `Time to effect` bullet, which supplies no per-item bold labels of its own.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji occurs in the file; tiers are conveyed by `<strong>` labels plus the `.benefits` / `.risks` CSS palettes.
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.	🟢	Gate items, benefits and risks are stripped to key facts and the At-A-Glance is held to 59 words; the 12 marker rows and 6 qualitative items are mandated in full by 14.2 and 15.2 and are carried as single-clause cells.

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 metadata comment immediately follows `<!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 “QRS — Metadata” caption 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.	🟢	It sits in an HTML comment; no metadata value is repeated in the header, footer or any span.
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; all other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: red_clover_extract_2026-0825-2359_Opus_ER.md`, matching the source ER’s own `filename` field.
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 at the top of QRS.md.
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-0817-0036`, in the required 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 context-window or tier qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: `qrs_filename: red_clover_extract_2026-0825-2359_Opus_QRS.html`, matching the file on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys: no stray whitespace and no unnecessary quoting.

#	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: “Red Clover Extract for Health & Longevity - Quick Reference Sheet”, matching ER `canonical_topic` with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	Line 417: “Red Clover Extract for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/17/2026”, the correct reformatting of `2026-0817-0036`.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter `qrs_creator_ai_fullname`.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header holds only the title and the template subline; the ER’s nine alternate names are 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 all three `Conclusion` paragraphs: receptor selectivity, the conditional vasomotor effect, the weaker secondary endpoints, placebo-equivalent tolerability and product variability.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words, verified by word count.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Maps to ER lines 480 (receptor selectivity, conditional heat-surge effect, inconsistent lipid/vascular/bone gains), 482 (side effects match dummy treatment) and 484 (products vary in strength).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “heat surges”, “blood fats”, “artery elasticity”, “dummy treatment” replace vasomotor symptoms, lipids, arterial compliance and placebo.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind; the ER’s −1.73 flushes/day and confidence intervals are omitted.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All nine items come from that section: eight from “Populations who should avoid Red Clover Extract” and one from the endocrine cancer therapy bullet flagged there as an absolute contraindication.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Complete: pregnancy/lactation, ER-positive breast and endometrial cancer, endocrine cancer therapy, undiagnosed bleeding, bleeding disorders/unstable INR, surgery within 14 days, active liver disease, under-18s, and PSA-monitored men.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 574–596: nine discrete `<li>` elements inside the `stop_items` span.
8.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	The ER’s rationale clauses are stripped, e.g. “since isoflavones cross into amniotic fluid and no safety data exist” (ER line 318) is dropped; no dash-trailing clause 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).	🟢	“within 14 days”, “above three times the upper limit of normal”, “under 18 years”, “unless supervised by the treating oncologist”, “until the cause has been established” and the endocrine-therapy drug list 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’s contraindication bullets use no ranking notation inside parentheses.
8.7	The section is left empty ONLY IF the ER’s `Key Interactions & Contraindications` section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER names eight such populations, and the section is correctly populated rather than empty.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All eight items map to the ER’s interaction bullets at lines 298–314.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Eight of the ER’s nine interaction bullets appear here; endocrine cancer therapy is correctly excluded because it is carried in the Contraindications gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 604–625: eight discrete `<li>` elements inside the `caution_items` 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.	🟢	Mechanistic and management text is stripped throughout, e.g. the coumarin rationale and the 14-day washout advice (ER line 298) and the P-glycoprotein/OATP1B1 gloss (ER line 310); the only retention is the ER’s own “low concern” severity class.
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 named drug list is preserved; the transporter list is trimmed to “(digoxin, rosuvastatin)” and the CYP450 item keeps its “low concern” class.
9.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER’s interaction bullets use no ranking notation inside parentheses.
9.7	The section is left empty ONLY IF the ER’s `Key Interactions & Contraindications` section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER names nine interactions, and the section is correctly 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 come from the ER `Therapeutic Protocol` bullets at lines 349, 351, 357 and 361.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, dosing schedule and extract selection are the three decisions that determine exposure; the ER’s competing-approach and demographic bullets are commentary rather than implementation steps.
10.3	If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	The ER `Therapeutic Protocol` section supplies twelve bullets, well above three.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	All nine cells populated: “40–80 mg isoflavones daily”, “40 mg twice daily” and “Promensil or Menoflavon”, each with an ER-sourced `sub` line.

11. Time to Effect

#	Description	Result	Comments
11.1	The three sets of [time] items cover the three most important time-to-effect aspects from the ER	🟢	Vasomotor improvement, lipid changes and bone effects — the only three onset windows the ER quantifies (line 408).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order follows the ER benefit tiers: hot flash reduction (High), blood lipid profile (first Medium), lumbar spine bone loss (third Medium).
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 no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	“4–12 weeks”, “3 months” and “12 months” with subs traceable to ER lines 408, 434 and 176.
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 explicit time-to-effect information in `Practical Considerations`.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	All eight benefit headings from ER lines 154–202 are represented in the matching tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 544–564.
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 item is the ER heading alone; the ER’s magnitude lines (−1.73 flushes/day, −12.34 mg/dL, 23% compliance rise) are all dropped. The retained “, conflicted” carries the ER’s own ⚠️ Conflicted marker, required by 1.2/1.3 and unavailable as an emoji under 4.4.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any benefit item.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four ER benefit tiers contain items, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All eight risk headings from ER lines 230–278 are represented in the matching tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 637–657.
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 item is the ER heading alone; the PSA fall from 10.16 to 7.15 ng/mL, the two bleeding case reports and the Ki-67 data are all 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 risk item.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four ER risk tiers contain items, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Every row is drawn from the ER `Monitoring Protocol & Defining Success` biomarker table (lines 436–449).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All twelve are present in ER order, with the ER’s optimal functional ranges and “why measure it” text carried 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 845–849 condense ER line 434: baseline, 12-week transaminases and symptom count, lipids at three and six months, annual thyroid/bone/endometrial review.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	All items come from the qualitative marker list at ER lines 453–458.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All six carried verbatim: hot flash count and severity, night awakenings and sleep quality, vaginal comfort and urinary urgency, mood stability, energy and cognitive clarity, and bleeding or bruising.

Issues 17/08/2026 00:47

Pass rate 100.00%. No issues found.

Issues 17/08/2026 00:41

11.4 — Tautological time-to-effect subs: time_2_sub (line 517) and time_3_sub (line 528) restate their own values (“Lipid changes appear by three months.” for “3 months”; “Bone effects require twelve months.” for “12 months”) instead of adding ER-sourced context the way time_1_sub does.

Fixes 17/08/2026 00:41

11.4 — Tautological time-to-effect subs: Replaced time_2_sub “Lipid changes appear by three months.” with “Total and LDL cholesterol reductions are measurable by the first three-month lipid recheck.” and time_3_sub “Bone effects require twelve months.” with “The trials showing attenuated lumbar spine loss tracked bone density over twelve months.”, so each sub adds ER-sourced context instead of restating its value.