Audit: QRS - Phellodendron amurense for Health & Longevity

Audit conducted on 20/08/2026 19:39 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	87
Failed	0
N/A	6
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 protocol values, gate items, tier lists, and all 10 monitoring rows trace to ER lines 322–360, 386–398, 445, 473–497.
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’s “⚠️ Conflicted” flag is carried as “(conflicted)”; “No established target” retained in marker_10_target.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	Pregnancy and lactation remain in Contraindications, not in Key Interactions; the conflicted cortisol signal is not 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 come from the ER’s “Populations who should avoid” list; Key Interactions from the ER’s interaction bullets; no Benefit- or Risk-Modifying Factor is surfaced.
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, NCT IDs, author names or brand names (Relora, Nexrutine) appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	Attributions are stripped rather than added; e.g. qualitative item 3 drops “which the mood trials captured”.

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, hedged framing of a thin, commercially funded evidence base matches the ER Conclusion.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Targets and cadence are actionable; limitations are stated without discouragement.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells describe trial regimens rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; monitoring cadence is stated descriptively.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, or “should” in the QRS body.
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 are used only where they carry the decision (Child-Pugh, eGFR, CYP3A4).
2.8	Information is presented in a concise and very compact manner	🟢	Gate items are bare facts; tier lines are semicolon-separated fragments.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for you/your/we/our.
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.	🟢	Optimal functional ranges (hs-CRP below 0.5 mg/L, ALT 10–26 U/L) are aimed at optimizers, 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.	🟢	A 10-marker panel plus drug-trough monitoring assumes a high-effort audience.
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.	🟢	Split three-times-daily dosing and repeat bloods are not 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.	🟢	At-A-Glance leads with the interaction hazard, the item that matters most to a supplement-stacking audience.
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 only in the title; “anti-aging” appears nowhere.
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.	🟢	Body uses “gastrointestinal intolerance”, “haemolytic anaemia”, “adverse events”; the plain-language wording in At-A-Glance is mandated by item 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 headings, gate labels, tier labels and table headers match the template byte for byte.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 fixed template variables present; the repeatable marker_#* and qualitative_item# rows expanded to 10 and 6 instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three <span website="..."> spans and the whole style block are 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 source ER section that feeds a QRS variable 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.	🟢	“Standard bark-only dose”, “Stress and weight-management blend” and “Best time of day” are the ER’s bold labels verbatim (ER lines 386, 390, 398).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit, risk and marker labels are the ER’s own headings and table cells; time-to-effect labels are the ER’s own domain terms from ER line 445.
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” is rendered as plain text.
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 carried item was trimmed to a bare fact; no explanatory prose was extended beyond the template’s cells.

---

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢	Lines 2–14, 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 “—” on line 3, closing “—” on line 13.
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 via the header variables required by section 6.
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, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: phellodendron_amurense_2026-0825-1800_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 QRS.md.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	Line 6: qrs_creation_date: 2026-0820-1932.
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, context-window qualifier correctly omitted.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s own name on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys; no stray whitespace 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: “Phellodendron amurense 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 matches ER frontmatter canonical_topic, with & encoded.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/20/2026” from qrs_creation_date 2026-0820-1932.
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’s own subline; the ER’s “Also known as” 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 ER lines 523–527: identity, low bioavailability, best signal, weaker signals, interaction hazard.
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 maps to a distinct sentence in the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“stress hormone” for cortisol, “blood fats” for lipids, “knee comfort” for osteoarthritis function; no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, author, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Only qualitative comparatives (“best”, “weaker”); no numbers at all.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the “Populations who should avoid Phellodendron amurense” list at ER lines 350–360.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All nine ER avoid-list entries are present, in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 569–577, nine well-formed <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.	🟢	The rationale “because of the bleeding and glucose interactions” and the gloss “(moderate to severe liver scarring)” are stripped; no trailing dash 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).	🟢	“Child-Pugh Class B or C”, “under 1 year”, “below 30 mL/min/1.73 m²”, “below 50 beats per minute”, “below 100 mmHg”, “within 14 days” all preserved.
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; all items read as plain prose.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER names nine such 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.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the fourteen interaction bullets at ER lines 322–348.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Twelve of fourteen carried; calcineurin inhibitors and immunosuppressant/biologic therapy correctly omitted as already covered by the transplant and autoimmune contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 585–596, twelve well-formed <li> elements.
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 “— monitor:”/”— caution:” clause plus its Mitigation sentence is stripped; only the drug class and its examples 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 eleven ER example-drug parentheticals are carried intact, with Coptis chinensis correctly italicised via <em>.
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 parentheticals are already comma-separated drug lists; no ranking symbols carried through.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER names fourteen 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.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells trace to the ER Therapeutic Protocol bullets at lines 386, 390 and 398.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Single-herb dose, the blend dose that matches the best-evidenced endpoint, and dose timing — the three decisions a user must make first.
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 provides fourteen bullets, well above three.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine cells populated; e.g. “250–500 mg twice daily” and “giving 500–1000 mg daily” from ER line 386.

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	🟢	Mood/stress, joint, and weight/lipids/glucose — the three domains named in the ER’s “Time to effect” bullet (line 445).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Mood and stress is the ER’s only Medium-tier benefit and leads; the two Low-tier domains follow.
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 domains.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	“4 weeks” and “4–8 weeks” with subs drawn verbatim from ER line 445.
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 thirteen entries correspond to ER benefit headings at lines 134–206.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 538–559.
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 entry is the bare ER heading; every “Magnitude:” line is dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No ER parenthetical is carried; “(conflicted)” is the non-emoji rendering of the ER’s own “⚠️ Conflicted” evidence flag required by item 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.	🟢	The ER states “No benefit reaches this level” for High; [benefits_high] carries style="display: none" at line 538.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eleven entries correspond to ER risk headings at lines 234–300.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 608–630.
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 entry is the bare ER heading; the cyclosporine figures and grade-3 event rate are dropped.
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 tier.
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 this level” for High; [risks_high] carries style="display: none" at line 608.

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 at lines 477–488.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 10 ER table rows carried in ER order, with name, target and rationale reproduced verbatim (marker_10_target trimmed only by “for this purpose”).
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 796–800 reproduce the cadence from ER line 475.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Sourced from the qualitative-markers list at ER lines 492–497.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER items present in order; item 3 trimmed of its trial attribution.

Issues 20/08/2026 19:39

Pass rate 100.00%. No issues found.