Audit: QRS - Fenugreek for Health & Longevity

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

Iterations

Summary

Items Count
Total 94
Passed 86
Failed 0
N/A 8
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. 🟢 All benefit/risk tier labels are the ER’s own section headings; protocol doses, time-to-effect values, gate items, all 12 biomarkers and all 7 qualitative markers are traceable to ER lines 347–378, 400–424, 455, 487–510.
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. 🟢 ER-cautious targets carried verbatim, e.g. marker_10_target “No established target for supplemented adults; track change from own baseline” (ER line 498) and marker_9_target (ER line 497).
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 remains an absolute Contraindication, not a caution; the testosterone claim is framed in at_a_glance as “the weakest part of the record”, matching ER line 534.
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. 🟢 Contraindications come only from the ER “Populations who should avoid Fenugreek” list; Key Interactions only from the ER interaction bullets; modifying factors are not surfaced as gates.
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 The QRS carries no PMIDs, no NCT identifiers and no brand names (Testofen, Libifem, FenuSMART, Furocyst, Fenfuro are all absent); drug names in the gates are the ER’s own generic examples.
1.6 The QRS does not introduce new attributions. 🟢 No author, institution, reviewer or manufacturer is named 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-weighted register matches the ER; British spelling (“standardised”, “haemoglobin”, “oestradiol”, “dysmenorrhoea”) is preserved throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Concrete doses, targets and time horizons are given without hedging or alarm, enabling action.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as noun phrases and observed facts, not as orders to a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No “should”, “must”, or imperative instruction in the QRS’s own voice; the cadence cell describes the monitoring pattern rather than prescribing it.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol and Monitoring cells present the regimens and ranges used in trials rather than recommending them.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronoun appears anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are expanded where the ER expands them: “HbA1c (glycated haemoglobin)”, “ALT and AST (transaminases)”, “Child-Pugh Class B or C liver impairment (moderate to severe cirrhosis)”.
2.8 Information is presented in a concise and very compact manner 🟢 Every gate, benefit and risk item is stripped to its key fact; mechanisms, magnitudes, citations and mitigations from the ER are all removed.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: no “you”, “your”, “we”, “our” or “us” in the document.
2.10 The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. 🟢 Functional-optimal ranges (fasting glucose 75–85 mg/dL, HbA1c 4.8–5.3%, ALT/AST < 20/25 U/L) are pitched at an optimising reader, not at conventional lab cut-offs.
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. 🟢 The sheet presents twice-daily gram-level dosing, a 12-marker baseline panel and several-times-weekly capillary glucose checks without softening for convenience.
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. 🟢 Twelve interaction classes and a twelve-marker panel presuppose a reader prepared to act on detail.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 at_a_glance closes with “Effects are largest when starting values are already disturbed”, which is precisely the caveat that matters for an already-optimised reader (ER line 532).
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. 🟢 “Longevity” appears in the title and header topic; “anti-aging” appears nowhere in the file.
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. Direct quotes from sources are exempt. 🟢 No consumer-grade route-of-administration or adverse-event wording; the sheet uses “with meals”, “in two doses”, “allergic reactions”, “hypoglycaemia”.

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 byte-identical to [qrs_template] (lines 437, 474, 516, 536, 542, 553, 572, 576–578, 603 of the template).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variable names present; the repeating marker_#* set is expanded to marker_1..marker_12 and qualitative_item# to qualitative_item_1..7.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The non-variable spans website=”evidence_review”, website=”audit” and website=”full_review” are unchanged; head, CSS and footer are byte-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 ER section feeding the QRS is empty — all four benefit tiers, all four risk tiers, the contraindication list, the interaction list and the monitoring table are populated in the ER.
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. 🟢 action_1_label “Whole-seed metabolic protocol”, action_2_label “Standardised extract protocol” and action_3_label “Best time of day” match the ER bold labels at lines 402, 404 and 410 verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Benefit and risk items reuse the ER’s own sub-section headings; monitoring marker names reuse the ER table’s Biomarker column verbatim.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Character scan confirms no emoji or symbol characters; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ Conflicted flags 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. 🟢 The one-page A4 print stylesheet is intact and unmodified; no page-break or second-page structure was added, and every section was condensed to key facts within the completeness constraints imposed by items 9.2, 12.2, 13.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; it is the first element 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 and closing “—” on line 13; the preceding title text on line 2 is permitted.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; no metadata value is repeated in the header, footer or body.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 All nine values trimmed; only duration: “00:02” is quoted, which is required because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: fenugreek_2026-0909-0246_Opus_ER.md, matching the ER frontmatter filename at ER line 17.
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.22, 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-1703, correctly formatted.
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: qrs_filename: fenugreek_2026-0909-0246_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: no leading or trailing whitespace on any of the nine lines; quoting used only where YAML requires it.

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: “Fenugreek for Health & Longevity - Quick Reference Sheet”, matching canonical_topic at ER line 8 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., &amp; for &) 🟢 Line 417: “Fenugreek for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/22/2026, correctly derived from qrs_creation_date 2026-0922-1703.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “Opus 5”, matching the frontmatter value.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 The header carries only the title and the template subline; the ER’s “Also known as” line was correctly not carried over.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opens “Fenugreek is a bitter food legume sold as a culinary spice and as standardised seed extracts” — kind and use given before any evidence verdict.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses ER Conclusion lines 532–534 and 538: metabolic effects, women’s symptom relief, the weak testosterone claim, and the baseline-dependence caveat.
7.3 [at_a_glance] is no longer than 70 words 🟢 67 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Legume/spice/extract framing from ER lines 37–39; metabolic list from line 532; women’s symptoms from line 532; testosterone weakness from line 534; baseline dependence from line 532.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; uses “blood sugar”, “blood fats”, “upper blood pressure number”, “a smaller waist” and “period-pain symptoms” in place of clinical classifications.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, author or sample size appears.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric effect estimate, confidence interval or percentage appears.

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 Fenugreek” list at ER lines 373–378.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-list entries are present, none added and none dropped.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six discrete <li> elements inside the stop_items span, lines 574–585.
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 rationale correctly stripped, e.g. “Children under 18, in whom no efficacy data exist and allergic sensitisation is most common” reduced to “Children under 18”; no dash-trailing clauses remain.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 “all trimesters, and the two weeks before an expected delivery date”, “within 14 days”, “(ribociclib, palbociclib)” and “Child-Pugh Class B or C … (moderate to severe cirrhosis)” 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. 🟢 The ER uses no ranking notation in this list; the CDK4/6 parenthetical is already a plain comma-separated list.
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 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 — six contraindications are listed.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All twelve items map one-to-one to the ER interaction bullets at ER lines 347–369.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All twelve ER interaction bullets carried; none duplicates an entry on the avoid-list.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Twelve discrete <li> elements inside the caution_items span, lines 593–612.
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 severity label, mechanism sentence and “Mitigation:” clause was stripped; only the drug-class name and its example list remain.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 All eight ER example-drug parentheticals are preserved intact, e.g. “(berberine, cinnamon extract, gymnema, bitter melon, chromium)” and “(warfarin, apixaban, rivaroxaban)”.
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. 🟢 The ER uses no ranking notation in these bullets; every parenthetical is already a plain comma-separated list.
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 twelve interaction classes, and the section is correspondingly populated rather than 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 — twelve key interactions are listed.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells map to the ER Therapeutic Protocol bullets at ER lines 402, 404 and 410.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The two dosing regimens (whole seed, standardised extract) plus timing are the three implementable decisions; the remaining ER bullets are background, provenance or pharmacokinetics.
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 or more distinct 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. 🟢 “10 g/day” / “5 g of defatted seed powder twice daily with meals” (ER line 402), “500–1,000 mg/day” / “Saponin-standardised seed or husk extract in two doses” (ER line 404), “With meals” / carbohydrate-meal and 30–60 minute pre-training detail (ER line 410).

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 🟢 Post-meal glucose, fasting glucose and lipids, and menopausal symptom scores — drawn from ER line 455, with HbA1c and the hormonal endpoints folded into the sub-lines so all five ER horizons are represented.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered glycaemic control, blood lipids, menopausal relief — the ER’s own High-tier ordering at ER lines 159, 165 and 177.
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 five distinct time-to-effect aspects 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. 🟢 “Immediate”, “4–8 weeks” with the “HbA1c requires 8–12 weeks” sub, and “6 weeks” with the “Hormonal endpoints took 8–12 weeks in trials” sub all match ER line 455.
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 at line 455, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All fifteen items are the ER Expected Benefits sub-section headings from ER lines 159–247.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four populated: 4 high, 2 medium, 6 low, 3 speculative — matching the ER tier counts exactly.
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. 🟢 Every ER “Magnitude:” figure, mechanism sentence and citation is stripped; items are reduced to the heading phrase alone.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content appears 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 contain 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 ten items are the ER Potential Risks & Side Effects sub-section headings from ER lines 269–329.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four populated: 1 high, 2 medium, 5 low, 2 speculative — matching the ER tier counts exactly.
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. 🟢 The ER’s sotolone, IgE, case-report and 66.3% co-sensitisation detail is all stripped; items are reduced to the heading phrase alone.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content appears 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 contain 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 🟢 The table reproduces the ER Monitoring Protocol & Defining Success biomarker table at ER lines 487–500.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All twelve ER biomarkers present with names, optimal ranges and rationales carried verbatim; the ER’s Context/Notes column was correctly dropped for the one-page format.
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 817–820 condense ER lines 483 and 485: baseline panel, several-times-weekly capillary glucose for four weeks, repeat panel at 12 weeks, then every 6–12 months, plus the transaminase addition.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All seven items come from the ER qualitative-marker list at ER lines 504–510.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All seven ER qualitative markers present and carried verbatim, none added or dropped.

Issues 22/09/2026 17:10

Pass rate 100.00%. No issues found.