Audit: QRS - Holy Basil for Health & Longevity

Audit conducted on 13/09/2026 02:09 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.	🟢	Spot-checked every filled span against the ER; e.g. time_1_sub mirrors ER line 426, marker_7_why mirrors ER line 466.
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.	🟢	Cautious ER framing retained: “Reproductive and thyroid concerns come from animals only”, “No trial beyond three months” (ER lines 508–510).
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”).	🟢	Contraindications keep the ER’s absolute framing; no “avoid” is downgraded to “caution” and no animal-only signal is upgraded.
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 and interactions come from the ER Key Interactions & Contraindications section only; 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.	🟢	No PMIDs, study names, NCT identifiers or brand names (OciBest, Holixer) appear anywhere in the QRS body.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind appear in the QRS.

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.	🟢	Matches the ER’s measured, evidence-weighted register throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven while remaining accessible; tiers and targets give actionable structure.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence and reference ranges without instructing or prescribing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives directed at a patient; the footer disclaimer is template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is stated declaratively (“Splitting is standard above 600 mg daily”), not as recommendation.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the body; marker_11_target uses “the individual’s own baseline”.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language throughout; the only technical terms are biomarker and drug-class names carried verbatim from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	All sections are condensed to short phrases; benefit and risk tiers are single semicolon-separated lines.
2.9	It DOES NOT address the reader directly	🟢	Verified: no “you”/”your” in the rendered body.
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.	🟢	Framing assumes a reader already tracking glucose, thyroid and platelet values.
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.	🟢	Protocol and monitoring assume willingness to split doses, self-measure glucose and run lab panels.
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.	🟢	Detail level (triterpene standardisation, functional reference ranges) is beyond general-population framing.
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢	Risk/benefit weighting mirrors the ER: narrow but favourable benefit set against animal-only reproductive and thyroid signals.
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; no aging-related framing is used at all.
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.	🟢	Route of administration is stated as powder/extract/rinse, not lay phrasing; “blood sugar” and “gum bleeding” in the lede are the ER Conclusion’s own words (ER lines 506–508).

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢	All fixed headings, gate headings, tier labels and the Marker/Target/Why column headers match the template byte-for-byte.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Diff against [qrs_template] confirms all 34 template spans present; marker_#* and qualitative_item# are expanded to 11 and 7 numbered instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Structural diff against the template shows changes only inside data-qrs-var spans; CSS, markup and the website=”…” spans 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 ER section is empty; every source section carries content, so no empty-state phrasing applies.
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 labels “Standard stress protocol”, “Metabolic protocol” and “Best time of day” are the ER bold labels verbatim (ER lines 369, 371, 379).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring marker names are the ER biomarker-table names verbatim; no label is invented.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters occur anywhere in the QRS; tiers are rendered with bold labels and CSS only.
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 relative to its ER source (12 benefit entries to four tier lines, 13 protocol bullets to three cells, the four-column ER biomarker table to three columns); no content is carried over uncondensed.

---

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.	🟢	The metadata comment opens on line 2, immediately after <!doctype html>.
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.	🟢	YAML is delimited by “—” on lines 3 and 13 inside the comment.
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 inside an HTML comment and is not echoed by any visible element.
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 values trimmed; only duration: “00:02” is quoted, which YAML requires because of the colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: holy_basil_2026-0913-0028_Opus_ER.md matches the source ER.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	qrs_prompt_version: 26.9.11 matches the version badge 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)	🟢	qrs_creation_date: 2026-0913-0202 is in YYYY-MMDD-HHMM form.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	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)	🟢	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]”	🟢	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)	🟢	Nickname plus version number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename matches 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 frontmatter keys.

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 &)	🟢	“Holy Basil for Health & Longevity - Quick Reference Sheet”; the ampersand is entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	“Holy Basil for Health & Longevity” matches the ER canonical_topic.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/13/2026 is the MM/DD/YYYY form of qrs_creation_date 2026-0913-0202.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	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 carries only title, creation date, review link, AI4L link and model; no AKA line or badge.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion (ER lines 506–510) into form, strongest evidence, animal-only concerns and duration limit.
7.2	[at_a_glance] is no longer than 60 words	🟢	55 words, within the 60-word limit.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion passage: form and route (line 506), the three strongest findings (line 506), animal-only concerns (line 508), three-month ceiling (line 508).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “type 2 diabetes” is the only clinical term and is in general use.
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 effect sizes or statistics; “Strongest human evidence” is qualitative.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items come from the ER “Populations who should avoid Holy Basil” list (ER lines 331–347).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight ER avoid-populations are represented, in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is a single <li></li> 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.	🟢	Trailing rationales stripped, e.g. “— the rat antifertility data have no human counterpart” and “, who appear in no oral supplementation trial”.
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).	🟢	Thresholds and windows preserved: TSH above 4.5 mIU/L, platelets below 100 × 10⁹/L, within 14 days of surgery, enzymes above twice the upper limit, the Lamiaceae example list.
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 Contraindications 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 does name avoid-populations, and the section is correspondingly populated.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty; eight contraindications are listed.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All nine items come from the ER Key Interactions & Contraindications bullet list (ER lines 311–329).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Nine of the ten ER interaction bullets are carried; “Anaesthesia and elective surgery” is correctly omitted as it is already a contraindication (“Within 14 days of elective surgery or an invasive dental procedure”).
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is a single <li></li> 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.	🟢	Severity words, mechanisms and “Mitigation is …” clauses are all stripped; only the agent or class remains.
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Every ER example-drug list is preserved; only the plain-language gloss “newer blood thinners” is trimmed from the anticoagulant item, with apixaban and rivaroxaban retained.
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 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 does name interactions, and the section is correspondingly populated.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty; nine interactions are listed.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells derive from the ER Therapeutic Protocol section (ER lines 369–393).
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 and timing are the three actionable aspects; the competing approaches, half-life and modifier bullets are descriptive rather than actionable.
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 supplies three or more distinct actionable aspects; 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.	🟢	Values and subs carry dose, standardisation, split and duration from ER lines 369, 371, 379 and 383.

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	🟢	Fasting glucose, stress/sleep and plaque/gum bleeding are drawn from ER lines 426 and 171.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order follows the ER High-tier benefit order: glucose, stress, dental.
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 or more distinct time-to-effect aspects; 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.	🟢	Each label, value and sub is populated from the ER; time_1_sub and time_2_sub are near-verbatim from ER line 426.
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 data (Practical Considerations, ER line 426), so the row is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All four tier lines come from the ER Expected Benefits headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four variables are present and populated.
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 tier is a semicolon-separated list of ER benefit headings, with no magnitudes or mechanisms.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; the “⚠️ Conflicted” markers on the anxiety and blood-pressure entries are dropped as required by 4.4.
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 benefit tiers carry items in the ER, so no tier span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All tiers come from the ER Potential Risks & Side Effects headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four variables are present; risks_high is retained as an empty hidden span.
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 risk is reduced to its ER heading with no frequencies or mechanisms.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried over; the 5% withdrawal figure and drug-class glosses are stripped.
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.	🟢	The ER states “No risk reaches High” (ER line 253), and risks_high is set to style=”display: none” with no empty-state text.

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 (ER lines 458–470).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eleven ER biomarkers are listed with their optimal functional ranges and reasons, unchanged.
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty.	🟢	Cadence states baseline, four weeks, eight weeks, then six-monthly, plus the thrice-weekly self-measurement caveat, from ER lines 454 and 456.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	The seven items come from the qualitative-marker list in the ER Monitoring section (ER lines 474–486).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All seven ER qualitative markers are listed verbatim.

Issues 13/09/2026 02:09

Pass rate 100.00%. No issues found.