Audit: QRS - Hoodia for Health & Longevity

Audit conducted on 16/08/2026 19:10 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
Pass Rate	100.00%

• Total = Passed + Failed + N/A
• Pass Rate = Passed / (Passed + Failed) × 100
• N/A items are excluded from the pass rate calculation

---

1. General Rules

#	Description	Result	Comments
1.1	Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER.	🟢	Every protocol cell, gate item, benefit, risk, marker row and qualitative item traces to a named ER passage (ER lines 300–309, 282–298, 333–341, 386, 416–437, 463–469).
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/limited framing is carried by the tier placement (Low, Speculative) and by ER-verbatim subs such as “Produced adverse effects without measurable appetite or weight benefit”.
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”).	🟢	Absolute contraindications from the ER (MAOIs, stimulants/sympathomimetics) appear in the STOP gate, not the caution gate; caution-level interactions stay in the caution gate.
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.	🟢	No content from ER Benefit-Modifying Factors (lines 185–195) or Risk-Modifying Factors (lines 269–277) appears in the gates or risk card.
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 contains no PMIDs, citations, expert names, NCT identifiers or brand names; all named drugs are ER generic names.
1.6	The QRS does not introduce new attributions.	🟢	No attributions beyond the fixed template subline.

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.	🟢	Sober, evidence-weighting tone matching the ER’s own framing of a conflicted, industry-funded evidence base.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric thresholds and named agents throughout; the sheet equips a decision rather than issuing a verdict.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Impersonal, declarative phrasing throughout; no imperative instructions to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Monitoring cadence and stop thresholds are presented as the ER’s described protocol, not as an instruction to the reader.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “advised” or “should” constructions in the QRS voice.
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 retained are the biomarker and drug-class names the sheet cannot function without; the At-A-Glance text is entirely plain language.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, benefits and risks are reduced to key facts; marker “Why” cells are single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; no direct address.
2.10	The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review.	🟢	Content assumes home blood-pressure monitoring, electrocardiography, liver panels and body-composition measurement.
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.	🟢	Every-second-day home monitoring, day-15 laboratory repeats and post-cessation retesting 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.	🟢	Tight functional ranges (e.g., alanine aminotransferase 10–26/10–30 U/L) rather than conventional laboratory flags.
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.	🟢	Fat-free mass is carried as a monitored marker and lean-mass loss as a risk — the longevity-relevant reading rather than the general weight-loss reading.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	“anti-aging” does not appear; “longevity-relevant harm” is used in marker 10.
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.	🟢	“alanine aminotransferase”, “corrected QT interval”, “sympathomimetic”, “aerial parts” used in the body; the At-A-Glance plain-language register is mandated by 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 labels present verbatim (lines 446, 492, 540, 564, 594, 624, 652, 656–658, 815) including all four tier labels in both Benefits and Risks.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	71 uniquely named data-qrs-var spans present, covering every variable referenced by the checklist (header, at_a_glance, action_1–3, time_1–3, benefits_, stop/caution_items, risks_, marker_1–10 name/target/why, monitoring_cadence, qualitative_item_1–7).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The non-variable template spans website="evidence_review", website="audit" and website="full_review" (lines 423, 426, 440) 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 is empty; the empty High/Medium benefit tiers are governed by the more specific rule 12.5.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	“Trial-derived regimen”, “European regulatory ceiling” and “Best time of day” are the ER’s bold labels verbatim (ER lines 333, 339, 341); interaction items reuse the ER’s bold labels including their parenthetical drug lists.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol, benefit, risk and marker labels are ER headings/labels; the three Time-to-Effect labels name the ER’s own three time-to-effect clauses (ER line 386).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	The ER’s 🟩/🟥/🟨/⚠️ markers are stripped; tiering is carried by the bold “High:”/”Medium:”/”Low:”/”Speculative:” labels and the card 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.	🟢	Condensation is applied throughout — benefits and risks are reduced to bare ER headings, gate items stripped to key facts, marker rationales to single clauses — while retaining the items that 8.2, 14.2 and 15.2 make mandatory.

---

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 on line 2 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 --- line 3, closing --- line 13; the descriptive text on line 2 precedes the opening delimiter.
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢	Enclosed in an HTML comment; no metadata value is echoed except the template-mandated creation date and model name in the subline.
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: hoodia_2026-0825-1658_Opus_ER.md, matching the ER 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 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-0816-1902.
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” — single word, no version.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	Line 8: qrs_creator_ai_fullname: Opus 5.
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	“Opus 5” — nickname plus version only.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: hoodia_2026-0825-1658_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 eleven keys; no stray whitespace or unnecessary quoting.

6. Page Title & Header

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &)	🟢	Line 22: “Hoodia 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: “Hoodia for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/16/2026” from qrs_creation_date: 2026-0816-1902.
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 contains only the title and the fixed template subline; the ER’s alternate_names 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 all four Conclusion paragraphs (ER lines 463–469): origin, conflicted and conflicted-funded efficacy, the harm set, and the adulteration problem.
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.	🟢	“chewed to blunt hunger” (ER line 38); “genuinely conflicted” and “All were paid for by companies” (ER line 465); the harm list (ER line 467); “another plant, no Hoodia, or an undeclared drug” (ER line 467).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“raised blood pressure and pulse”, “odd skin sensations”, “shifted liver markers”, “muscle loss in animals” — no acronyms, no clinical-register vocabulary.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, sample size or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind; the ER’s −1.6 kg and 56.4% figures are deliberately omitted.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All ten items map to ER lines 288, 290 and 300–309.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight “Populations who should avoid Hoodia” bullets are present (the combined MAOI / narrow-margin-substrate bullet split into two items), plus the ER’s absolute-contraindication stimulant/sympathomimetic combination.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Ten discrete <li> elements at lines 567–589.
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.	🟢	No dashes and no trailing clauses; the ER’s rationale for the pregnancy bullet (“animal data show delayed fetal bone formation…”) is stripped.
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).	🟢	“≥ 140/90 mmHg on treatment”, “above 440 milliseconds”, “below 50 or above 100 beats per minute”, “above twice the upper limit of normal”, “below 20 kg/m²”, “over 70” and the MAOI 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 uses no ranking notation in this section; “≥ 140/90 mmHg” is a threshold value, carried through unchanged.
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 section is populated, correctly, because the ER names eight such populations plus two absolute drug-class contraindications.
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 ER lines 282–298.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All seven ER caution-level bullets are present; the two absolute-contraindication bullets (stimulants/sympathomimetics, MAOIs) are correctly excluded and appear only in the STOP gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven discrete <li> elements at lines 597–614.
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.	🟢	The ER’s mechanism and mitigation sentences (“P57 weakly inhibits CYP3A4…”, “Home monitoring twice weekly…”) are all stripped; no dashes present.
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Every ER example-drug list is retained in full: simvastatin/midazolam/tacrolimus/apixaban; digoxin/dabigatran/rivaroxaban/colchicine; amlodipine/lisinopril/bisoprolol; the OTC list; bitter orange/green tea extract/guarana/Acacia rigidula/forskolin; green tea extract/kava/Garcinia cambogia/high-dose niacin; semaglutide.
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 in this section; all parentheses are plain comma-separated drug lists.
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 section is populated, correctly, because the ER names nine interaction bullets.
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 333, 339 and 341.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose regimen, the competing regulatory dose ceiling, and timing — the only three bullets in the ER section that specify an executable action.
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 contains twelve bullets; 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 spans populated; labels are the ER’s bold labels verbatim and the subs paraphrase the matching ER sentences without adding facts.

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	🟢	The ER’s Practical Considerations “Time to effect” bullet (line 386) names exactly three; all three are carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Body measurements (−1.6 kg, −2.1 cm) first, subjective appetite second, the null purified-extract result 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	Three distinct time-to-effect aspects are present in the ER; 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.	🟢	“40 days”, “Within 10 days” and “Nothing at 15 days” with subs quoting ER line 386; species attribution for the whole-plant trial is supported by ER lines 160 and 337.
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 row is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Sourced from ER lines 148–180.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 542, 545, 548, 551.
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.	🟢	Bare ER sub-headings only; the “Magnitude:” paragraphs, the −1.6 kg figure and every citation are dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in either benefits 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.	🟢	The ER states no benefit reaches High or Medium (lines 150, 154); both spans carry style="display: none" with no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Sourced from ER lines 204–264.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 626, 629, 635, 641.
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.	🟢	Bare ER sub-headings only; the 56.4%, 63.3% and 15.5% figures and all citations are dropped.
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 risk tiers carry items in the ER, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Sourced from the ER Monitoring Protocol & Defining Success table and cadence paragraph (lines 414–427).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER table rows present in ER order, with targets and rationales matching the ER’s “Optimal Functional Range” and “Why Measure It?” columns.
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 804–809 reproduce the ER’s ongoing-monitoring paragraph (line 414) including the day-15 repeats, the monthly panel beyond 30 days and the four-week post-cessation check.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Sourced from the ER’s “Qualitative markers worth tracking” list (lines 431–437).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All seven ER bullets present in ER order: hunger/craving score, nausea/vomiting/early fullness, skin sensations, palpitations/restlessness, sleep onset and quality, training quality, and the jaundice/dark-urine stop signals.

Issues 16/08/2026 19:10

Pass rate 100.00%. No issues found.