Audit: QRS - Syringic Acid for Health & Longevity

Audit conducted on 13/08/2026 05:49 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 85
Failed 0
N/A 8
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 populated span against the ER: protocol cells vs ER Therapeutic Protocol, time cells vs Practical Considerations time-to-effect bullet, all 14 marker rows vs the ER biomarker table, gates vs Key Interactions & Contraindications. All literally supported.
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 phrasing carried through, e.g. “No established human protocol” (action_1_sub) and “no study has compared schedules” (action_2_sub).
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”). 🟢 No claim strengthened or softened; “lowers blood pressure, blood sugar, and stored fat in rodents” keeps the ER’s species 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. 🟢 Contraindications come from the ER’s “Populations who should avoid Syringic Acid” list; interactions from the ER interaction bullets. No modifying factor is surfaced as a gate.
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 citations, expert names or NCT identifiers appear. Named drugs/supplements are exactly those the ER names for the same interactions.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind 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 restrained, evidence-gap-forward register.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective and data-driven throughout; tiering and monitoring targets give the reader actionable structure.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence and observed practice; no prescriptive instruction to a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No clinical advice; monitoring cadence is stated descriptively (“that first interval shortens to two weeks”).
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Statements are declarative descriptions of what the evidence and existing practice show, not recommendations.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address anywhere in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language; technical terms are only those the ER itself uses in table rows (HOMA-IR, hs-CRP, eGFR).
2.8 Information is presented in a concise and very compact manner 🟢 Highly compact: benefit and risk tiers collapsed to single semicolon-separated lines; gate items reduced to key facts.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no direct reader 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 a self-quantifying adult: 14-marker panel, functional ranges, home blood-pressure averaging.
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, pair with fat, and run repeat 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. 🟢 Not pitched at the general population; assumes lab access and adherence to a multi-month assessment window.
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. 🟢 Framing foregrounds the human-evidence gap alongside the preclinical breadth, which is the weighting this audience needs.
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. 🟢 The term “anti-aging” does not appear.
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. 🟢 Formal terminology throughout (“hepatic impairment”, “adverse”, “antihypertensives”); no consumer-grade substitutes.

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 present verbatim: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”; tier labels and “Marker/Target/Why” headers unmodified.
3.2 All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. 🟢 All template variable spans are present: page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1-3 (label/value/sub), time_1-3 (label/value/sub), benefits_* , stop_items, caution_items, risks_, marker_ (name/target/why), monitoring_cadence, qualitative_item_1-6.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Unaddressed spans (website=”evidence_review”, website=”full_review”, website=”audit”) and the footer disclaimer are left intact.

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 maps to a QRS field is empty. The empty High tiers are governed by items 12.5 / 13.5 (display:none), not by empty-state phrasing.
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 reuse the ER bold labels verbatim: “Dose range in use”, “Single versus split dosing”, “Dosing with dietary fat”.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label paraphrased or abbreviated; time-to-effect labels are drawn directly from the ER’s time-to-effect bullet wording.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators anywhere; tiering is conveyed by bold labels and CSS colour.
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. 🟢 Content is condensed to fit: tiers collapsed into single list items, gate items trimmed to key facts, qualitative markers stripped of their ER rationale clauses. The 14-row monitoring table is mandated by item 14.2.

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. 🟢 Metadata comment opens at line 2, immediately after <!doctype html> on line 1, before any other 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. 🟢 YAML delimited by --- at line 3 and --- at 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; not surfaced anywhere 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. 🟢 All values trimmed; 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]” 🟢 er_filename: syringic_acid_2026-0813-0228_Opus_ER.md (line 4).
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 (line 5), matching this QRS.md version.
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-0813-0544 (line 6), correct YYYY-MMDD-HHMM format.
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 (line 7).
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 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]” 🟢 qrs_creator_ai_fullname: Opus 5 (line 8).
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 only, no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: syringic_acid_2026-0813-0228_Opus_QRS.html (line 9), matching the actual filename.
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. 🟢 Confirmed — no stray whitespace or unnecessary quoting in any value.

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 &) 🟢 <title>Syringic Acid for Health &amp; Longevity - Quick Reference Sheet</title> (line 22), entity-encoded correctly.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 header_topic = “Syringic Acid for Health & Longevity” (line 417), matching the ER canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 header_subline_date = 08/13/2026 (line 421), the MM/DD/YYYY form of 2026-0813.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model = “Opus 5” (line 425).
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, source-review link and model; no badge, version stamp, AKA line, or audit date.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distils the ER Conclusion: dietary sources and purified availability, the preclinical effect profile, and the human-evidence and safety gap.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words — within the 60-word budget.
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 (dietary sources; laboratory/animal effect list; “Almost nothing has been measured in people who swallow it”; “Formal safety testing has covered two weeks in rodents”).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications; “protective enzymes” and “sold purified” replace technical equivalents.
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, relative risks, or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER’s “Populations who should avoid Syringic Acid” list inside Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoidance populations are represented, one-to-one (lines 571-576).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each item is a discrete <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. 🟢 Rationale clauses stripped, e.g. ER’s “on the basis that no reproductive toxicity study exists” reduced to “Pregnancy and lactation”; 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). 🟢 Qualifiers preserved and compacted into parentheses: “(Child-Pugh Class B or C)”, “(below 30 mL/min/1.73 m²)”, “and for 30 days afterwards”, “until ferritin is restored”, “under 18”.
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 inside parentheses in this section.
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; the ER does identify populations that should avoid the intervention, so leaving it empty would have been wrong.
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. <!– empty: ER names no population that should avoid the intervention –> 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 🟢 Drawn from the ER Key Interactions & Contraindications bullet list.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All ten interaction bullets are carried through; the eleventh (chemotherapy and radiotherapy) is correctly excluded because it sits in Contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each item is a discrete <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. 🟢 Caution/Monitor labels, mechanisms, consequences and mitigations all stripped; only the agent 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 parenthetical retained verbatim, e.g. “(lisinopril, amlodipine, losartan, hydrochlorothiazide)” and “(berberine, chromium picolinate, alpha-lipoic acid, cinnamon extract)”.
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 inside parentheses in this section.
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; the ER identifies eleven interactions, so leaving it empty would have been wrong.
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. <!– empty: ER names no interaction that changes how the intervention is used –> N/A The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from the ER Therapeutic Protocol section.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose range, single-versus-split dosing, and dosing with dietary fat are the three actionable bullets in the ER protocol; the remainder are modifiers, competing approaches, or population caveats.
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 at least three distinct actionable 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 action fields carry ER-derived content (lines 450-488).

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 🟢 Covers the three facts in the ER’s Practical Considerations time-to-effect bullet: topical skin studies at twelve weeks, rodent metabolic change over 6-16 weeks, and the four-month assessment window.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered correctly by benefit magnitude: skin lesions (the ER’s only Medium-tier benefit) first, metabolic markers (Low tier) second, general assessment window 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 exist in the ER, 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 time fields carry ER-derived content (lines 498-532).
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 section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from the ER Expected Benefits section.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit spans present (lines 541-561).
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 benefit reduced to its ER heading, with magnitudes, mechanisms and study details dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives in any benefit item.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 [benefits_high] is empty with style="display: none" (line 541), matching the ER’s empty High tier; no empty-state text used.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from the ER Potential Risks & Side Effects section.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk spans present (lines 611-626).
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 reduced to its ER heading; magnitudes, concentrations and conflict markers dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives in any risk item.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 [risks_high] is empty with style="display: none" (line 611), matching the ER’s empty High tier; no empty-state text used.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol & Defining Success section.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 14 ER biomarkers are present, with targets and rationale matching the ER table verbatim: fasting glucose, HbA1c, fasting insulin, HOMA-IR, triglycerides, HDL-C, LDL-C with particle number, hs-CRP, ALT, AST, eGFR, ferritin, home systolic blood pressure, adiponectin.
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. 🟢 [monitoring_cadence] (lines 823-827) carries the ER’s four-week / three-month / six-month cadence plus the shortened two-week interval for medicated users.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER’s qualitative marker list at the end of Monitoring Protocol & Defining Success.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers listed, with their trailing ER rationale clauses correctly trimmed.

Issues 13/08/2026 05:49

Pass rate 100.00%. No issues found.