Audit: QRS - Dihydromyricetin for Skin Rejuvenation of the ER frontmatter

Audit conducted on 01/08/2026 02:25 using AI4L / Grok 4

Iterations

Summary

Items Count
Total 91
Passed 84
Failed 0
N/A 7
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. 🟢  
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. 🟢 Preserves “insufficient data”, “theoretical”, “not validated”, “Not defined”/”No established onset” aligned with ER “lack a defined onset”.
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”). 🟢  
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. 🟢  
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. 🟢 None introduced.
1.6 The QRS does not introduce new attributions. 🟢  

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. 🟢  
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢  
2.4 The QRS avoids language that implies medical or clinical advice 🟢  
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢  
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained where they are ER labels/markers (CYP, ALT, etc.).
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢 Uses “skin aging”/”facial aging”, not “anti-aging”.
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. 🟢 “gut symptoms” mirrors ER Conclusion wording.

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” 🟢  
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 Template # markers expanded to numbered marker_1–8 and qualitative_item_1–5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢  

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” 🟢 Empty High benefit/risk tiers use display:none per 12.5/13.5 (ER omits those tiers).
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 match ER bold labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢  
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. 🟢  

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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢 duration quoted for colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: dihydromyricetin_skin_2026-0731-2317_Grok_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]” 🟢 qrs_prompt_version: 26.7.02
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-0801-0120
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Grok
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢  
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Grok 4
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) 🟢  
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 dihydromyricetin_skin_2026-0731-2317_Grok_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. 🟢  

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Dihydromyricetin for Skin Rejuvenation - 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., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 08/01/2026 from 2026-0801-0120
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Grok 4
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢  

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢  
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. 🟢  
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain-language paraphrases (e.g., surface-skin age scores vs epidermal DNA methylation age).
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢  

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From “Populations who should avoid or defer”.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All five populations mapped.
8.3 Individual [stop_items] are formatted as <li></li> 🟢  
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. 🟢  
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). 🟢 (insufficient data), (topical), (oral) 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. N/A ER does not use ranking notation in contraindication items.
8.7 If no [stop_items] are present the section is left empty N/A stop_items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢  
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Six interaction bullets; critical narrow-index CYP avoid remains in stop only as absolute gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢  
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. 🟢 Caution/Monitor trailing ranks stripped.
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). 🟢 Example drugs and (oral) route preserved.
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 ER does not use ranking notation in interaction items.
9.7 If no [caution_items] are present the section is left empty N/A caution_items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 From Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Topical primary, oral adjunct, timing.
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 Three distinct aspects are present and used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢  

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 🟢 8 weeks, ~4 weeks, oral not defined.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Main clinical window first; early changes; oral weakest/undefined.
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 aspects are present and used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢  
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 ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢  
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢  
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. 🟢  
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 (Topical), (Oral, Preclinical), etc. stripped.
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. 🟢 benefits_high style=”display:none”.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢  
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢  
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. 🟢  
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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. 🟢 risks_high style=”display:none”.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 From Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 8 table biomarkers present.
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. 🟢 Matches ER ongoing cadence wording.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢  
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 5 qualitative markers present.

Issues 01/08/2026 02:25

Pass rate 100.00%. No issues found.

Issues 01/08/2026 02:19

  1. 2.7 — Unnecessary specialist jargon: time_2_sub uses “echogenicity” without a plain-language alternative; benefits_low keeps “senomorphic” and “SASP-like” without plain framing where a longevity-reader paraphrase would suffice.

  2. 9.5 — Dropped Z-drug example: Key Interactions sedatives item omits the ER nested example “zolpidem” from “Z-drugs (non-benzodiazepine hypnotics such as zolpidem)”.

Fixes 01/08/2026 02:21

  1. 2.7 — Plain-language jargon cleanup: Replaced time_2_sub “echogenicity” with “dermal-density”; rewrote benefits_low senomorphic/SASP phrasing to “calming support of aged fibroblasts and reduced age-related cell-stress signaling”; expanded risks_speculative DNMT1 wording to “DNA-methylation enzyme inhibition”.

  2. 9.5 — Z-drug example restored: Key Interactions sedatives item now includes “Z-drugs such as zolpidem” to preserve the ER nested example drug.

Issues 01/08/2026 02:13

  1. 1.1 — Unsupported claim wording: At-a-glance uses “metabolic health” where the ER Conclusion says “metabolic liver markers”; time_1_sub says “dermal density shifts” where the ER reports “echogenicity shifts.”
  2. 1.3 — Claim scope broadened: At-a-glance broadens oral evidence from ER “metabolic liver markers” to “metabolic health.”
  3. 4.3 — Marker label abbreviated: marker_3_name drops “(cutometry)” from the ER Monitoring table marker “Skin elasticity / firmness (cutometry) if available.”
  4. 11.2 — Time-to-effect order: Time cells are ordered chronologically (~4 weeks, 8 weeks, oral) rather than by magnitude of the related benefit (main 8-week clinical window should lead).

Fixes 01/08/2026 02:14

  1. 1.1 / 1.3 — At-a-glance oral evidence wording: Replaced “metabolic health” with ER Conclusion phrasing “metabolic liver markers.”
  2. 1.1 — Early time-to-effect subtext: Replaced “dermal density shifts” with ER “echogenicity shifts” in time_2_sub (after reorder).
  3. 4.3 — Marker 3 label: Restored “(cutometry)” in marker_3_name to match the ER Monitoring table.
  4. 11.2 — Time-to-effect order: Reordered cells by benefit magnitude: main 8-week clinical window first, then ~4-week early changes, then oral not defined.

Issues 01/08/2026 02:08

  1. 12.3 — Benefits low key fact: benefits_low rewrites ER title “Senomorphic Support of Aged Fibroblasts and Reduced SASP-Like Stress” as mechanistic paraphrase “calming support of aged fibroblasts and reduced harmful aging-cell signaling” instead of the key fact.
  2. 13.3 — Risks speculative DNMT1: risks_speculative rewrites ER title term “DNMT1 Inhibition” as “DNA-methylation enzyme inhibition” rather than the key fact from Potential Risks & Side Effects.

Fixes 01/08/2026 02:10

  1. 12.3 — Benefits low key fact: Restored benefits_low second item to ER key fact “senomorphic support of aged fibroblasts and reduced SASP-like stress” (replaced mechanistic paraphrase).
  2. 13.3 — Risks speculative DNMT1: Restored risks_speculative third item term to “DNMT1 inhibition” per ER title (replaced “DNA-methylation enzyme inhibition”).

Issues 01/08/2026 01:57

  1. 7.4 — At-a-glance specialist wording: At-a-glance uses research-register “skin signal” and clinical-register “metabolic data” instead of plain-language terms a non-specialist would use unprompted (e.g., strongest evidence / metabolic health findings).

Fixes 01/08/2026 02:00

  1. 7.4 — At-a-glance plain language: Replaced research-register “skin signal” with “skin evidence” and “clearer metabolic data than proven facial effects” with “clearer support for metabolic health than for facial aging” (59 words, still under 60).

Issues 01/08/2026 01:50

  1. 1.2 — Monitoring cautious qualifiers dropped: ALT target omits ER “targeted” and “sex-specific”; glucose/HbA1c target omits ER “(individualized)”.
  2. 1.3 — GABA subtype and target hardening: risks_speculative says “GABA pathways” instead of ER “GABA_A Pathways”; dropped monitoring qualifiers also present absolute ranges more strongly than the ER.

Fixes 01/08/2026 01:51

  1. 1.2 — Monitoring cautious qualifiers restored: Restored ALT target to “Often targeted ~<25–30 U/L (sex-specific lab ranges vary)” and glucose/HbA1c target to include “(individualized)”.
  2. 1.3 — GABA_A pathway wording: Changed risks_speculative “GABA pathways” to “GABA_A pathways” to match the ER subtype claim.

Issues 01/08/2026 01:37

  1. 2.7 — Unexplained specialist jargon: Protocol uses unexpanded “DHM”; benefits/risks keep specialist terms (SASP, senomorphic, DNMT1) without plain-language support.
  2. 4.2 — Protocol labels not verbatim: action_1_label is “Primary route” instead of ER bold label “Primary skin-oriented approach (topical)”; action_2_label omits ER “(evidence weaker for skin)”.
  3. 4.3 — Labels paraphrased or abbreviated: “Primary route” is invented/paraphrased; “Oral adjunct” drops the ER parenthetical qualifier that belongs in the bold label.
  4. 12.3 — Study detail in benefits: benefits_low retains “in stressed models” (study-setting detail) on the wound-closure benefit.

Fixes 01/08/2026 01:45

  1. 2.7 — Plain-language jargon cleanup: Replaced unexpanded “DHM” with “dihydromyricetin” in protocol and monitoring; rewrote SASP/senomorphic/DNMT1 phrasing into plain terms (calming support, harmful aging-cell signaling, DNA-methylation enzyme).
  2. 4.2 / 4.3 — Protocol labels restored: Set action_1_label to ER bold label “Primary skin-oriented approach (topical)” and action_2_label to “Oral adjunct (evidence weaker for skin)”.
  3. 12.3 — Study detail stripped: Removed “in stressed models” from the low-tier wound-closure benefit line.

Issues 01/08/2026 01:34

  1. 1.3 — Strengthened dosing preference: action_3_sub reads “Oral with meals; split dosing preferred”, which strengthens the ER Protocol’s descriptive wording (“often with meals”; split dosing “is more common”) into a preference claim.

  2. 2.5 — Preference framed as guidance: The same action_3_sub “preferred” phrasing presents guidance rather than information-only condensation of the ER.

Fixes 01/08/2026 01:36

  1. 1.3 / 2.5 — Dosing preference wording: Changed action_3_sub from “Oral with meals; split dosing preferred” to “Oral often with meals; split dosing more common” to match ER Protocol descriptive phrasing.

Issues 01/08/2026 01:27

  1. 7.4 — Technical jargon in at-a-glance: The at_a_glance text uses “flavonoid” (“vine-tea flavonoid”), a technical chemical classification that a non-specialist would not use unprompted with exact meaning; plain-language wording is required.

Fixes 01/08/2026 01:28

  1. 7.4 — At-a-glance plain language: Replaced “vine-tea flavonoid” with “vine-tea plant compound” in at_a_glance to remove the specialist chemical classification.