Audit: QRS - Broccoli Seed for Health & Longevity

Audit conducted on 16/08/2026 11:06 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.	🟢	All 16 benefit items, 9 risk items, 5 contraindications, 7 interactions, 10 biomarkers, 5 qualitative markers, 3 protocol cells and 3 time-to-effect cells trace to explicit ER text.
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.	🟢	E.g. time_2_sub “Change is plausible mainly where the marker started abnormal” mirrors ER “a measurable change is plausible”; marker_5_why keeps “the one theoretical risk”.
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; chemotherapy/radiotherapy stays absolute with the “absent oncology approval” qualifier.
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 on ER `Key Interactions & Contraindications`; Benefits/Risks cards draw only on the corresponding ER sections.
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, author names, NCT identifiers 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.	🟢	Measured, evidence-first register matching the ER, including the ER’s emphasis that preparation determines conversion.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and thresholds alongside plain-language framing.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as observed evidence, not as orders.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs; footer disclaimer states the educational framing.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No instance of “recommend”, “advise”, “should” or “must” in document voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the rendered content.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Biomarker names are spelled out in full (“Alanine aminotransferase”, “Thyroid-stimulating hormone”); the few retained technical terms (CYP1A2, NF-κB) are carried verbatim from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Benefits/risks reduced to bare tier lists; interactions and contraindications reduced to label-level facts.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for second-person forms.
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 rather than conventional reference ranges; product-delivery caveats surfaced.
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.	🟢	Retains urinary sulforaphane metabolite testing and drug-level testing, both effortful.
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.	🟢	Assumes access to laboratory panels and willingness to titrate.
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 explicitly notes benefits are confined to people whose values started abnormal.
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.	🟢	No colloquialisms; “blood sugar” appears only as part of the ER’s verbatim benefit heading and in the plain-language At-A-Glance required 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 present verbatim at lines 446, 491, 540, 620, 649, 806, 571, 592, 543/546/554/563, 653–655.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	69 data-qrs-var spans present, covering every variable named in this checklist (page_title through qualitative_item_5), with no gaps in the marker_1–marker_10 series.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The non-variable template spans (website=”evidence_review”, website=”full_review”, website=”audit”) 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.	🟢	action_1/2/3_label reproduce the ER bold labels “Standard supplemental dose”, “Best time of day”, “Single versus split dosing” exactly.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit/risk items and all 10 marker names reproduce the ER headings and ER table rows verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-text scan returns no emoji; the ER’s “⚠️ Conflicted” markers are 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 padded: 16 benefits and 9 risks collapsed to bare tier lines, 12 ER protocol bullets reduced to 3 cells, interaction bullets reduced to label level, and print CSS pins the sheet to A4.

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, immediately after the doctype at line 1.
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢	Opening “—” at line 3, closing “—” at line 13; the descriptive text sits on line 2 before the opener.
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢	Enclosed in an HTML comment; no element repeats the values.
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 so because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: broccoli_seed_2026-0825-0647_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 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-1056`.
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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual file `broccoli_seed_2026-0825-0647_Opus_QRS.html`.
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 ten keys; no stray whitespace or 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: “Broccoli Seed 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: “Broccoli Seed for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/16/2026”, matching qrs_creation_date 2026-0816-1056.
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.	🟢	Header holds only the title and the template subline; the ER’s “Also known as” list 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	🟢	Maps to the four Conclusion paragraphs: conversion dependence, strongest evidence, smaller conditional effects, and harms.
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 traces to a distinct Conclusion sentence (ER lines 564–568).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“sulforaphane”/”glucoraphanin”/”Nrf2” are replaced by “a compound the body converts into its active form”; no acronyms appear.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, or sample sizes.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numerals or statistics appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All five items derive from the ER “Populations who should avoid Broccoli Seed” sub-list (ER lines 404–410).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoidance populations are represented, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 574–587: five discrete `<li>` elements inside the 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.	🟢	ER’s trailing rationale (“no safety data above food quantities; supplemental doses over 30 mg/day … untested outside a 12-woman pregnancy-hypertension study”) is stripped; no dashes 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).	🟢	Retains urinary iodine <100 µg/L, TSH >4.5 mIU/L, the two-week chemotherapy window, theophylline >15 µg/mL, ANC <1.0 × 10⁹/L, and age over 65.
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 parentheses; its “>” and “<” symbols are numeric threshold operators.
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 five such populations and the section is correctly populated.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All seven items map to ER interaction bullets at lines 388–402.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven of the ER’s eight interaction bullets appear; the cytotoxic chemotherapy/radiotherapy bullet is correctly omitted because it is carried in [stop_items].
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 595–610: seven discrete `<li>` elements inside the 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.	🟢	Each item is the ER bold label only; all mechanism and mitigation prose is stripped and no dashes 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).	🟢	Drug lists preserved for CYP1A2 substrates, Nrf2-activating supplements, glucose-lowering agents, proton pump inhibitors and antibiotics; only the redundant plain-language gloss “stomach acid-blocking medicines” is trimmed.
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 parentheses contain plain comma-separated drug lists only, with no ranking notation.
9.7	The section is left empty ONLY IF the ER’s `Key Interactions & Contraindications` section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER identifies eight interactions and the section is 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 map to bullets in ER `Therapeutic Protocol` (lines 434, 442, 446).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, timing, and single-versus-split administration are the three decision-bearing bullets; the remaining ER bullets are formulation commentary or modifier discussion.
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 more than three actionable implementation aspects, so all three sets are used.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	All nine fields carry ER-derived content; e.g. action_1 “20–60 mg/day” with “trial doses span 7 mg to 92 mg” from ER line 434.

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	🟢	Detoxification markers, liver enzymes and glucose, and cognitive measures are exactly the three aspects named in ER line 491.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Detoxification (High tier) first, glucose/liver enzymes (Medium/Low) second, cognition (Low) third.
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 names three distinct time-to-effect aspects, so all three sets are used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine fields populated; the 30-month dementia-pilot note traces to ER line 491.
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 16 items correspond one-to-one to the 16 ER `Expected Benefits` sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 542, 545, 553, 562 with 1, 5, 8 and 2 items respectively, matching the ER tier counts.
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 bare ER heading; magnitudes, sources and the “⚠️ Conflicted” markers are all 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 needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All 9 items correspond one-to-one to the 9 ER `Potential Risks & Side Effects` sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 622, 625, 632, 638 with 1, 3, 3 and 2 items respectively, matching the ER tier counts.
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 bare ER heading; the 94% adverse-event figure, outbreak counts and enzyme percentages are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any 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 needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Table rows reproduce the ER `Monitoring Protocol & Defining Success` biomarker table (ER lines 521–532).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All 10 ER biomarkers present in ER order, with the ER’s optimal functional ranges and “Why Measure It?” text carried across.
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 795–800 condense ER line 519: baseline, 12 weeks, 6 months, annually, thyroid at 6 months, CYP1A2 drug level at 4 weeks.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	All five items come from the ER “Qualitative markers worth tracking” list (ER lines 536–540).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All 5 ER qualitative markers present in ER order: digestive tolerance, recovery quality, sleep onset and irritability, subjective processing speed, caffeine tolerance.

Issues 16/08/2026 11:06

Pass rate 100.00%. No issues found.