Audit: QRS - Cissus quadrangularis for Health & Longevity

Audit conducted on 27/09/2026 22:09 using AI4L + evidence-mcp / GPT 6

Iterations

Summary

Items Count
Total 94
Passed 86
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. 🟢 Compared all populated regions with the named ER; doses, durations, categories, and monitoring statements are 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. 🟢 Preserves uncontrolled evidence, conflicting metabolic findings, untested combinations, theoretical concerns, and unvalidated monitoring.
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”). 🟢 Study regimens remain research regimens; no established efficacy, optimal dosing, or preventive benefit is claimed.
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. 🟢 Benefit and harm tiers retain their ER categories; transplant medication is consolidated within the corresponding avoidance 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. 🟢 CQR-300 appears for the same metabolic regimen as in the ER; named medicines match the interaction section.
1.6 The QRS does not introduce new attributions. 🟢 No new source, expert, or institutional attribution is introduced.

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. 🟢 Cautious, formulation-dependent ER framing is retained.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Compact evidence statements combine accessible explanations and concrete study details.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Protocol cells describe studied regimens rather than prescribing treatment.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Content describes evidence and research schedules; the fixed educational disclaimer remains.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Reports findings, limitations, and illustrative monitoring.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Variable content does not address the reader; the fixed template disclaimer is unchanged.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Low platelets and kidney filtration estimate explain or replace specialist terminology.
2.8 Information is presented in a concise and very compact manner 🟢 Uses short cells, tier descriptors, gate lists, and compact monitoring rows.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address in the populated content.
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. 🟢 Includes function, training-related evidence, preventive uncertainty, and longevity framing.
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. 🟢 Includes tracking and context-dependent laboratory assessment.
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. 🟢 Supports an engaged, monitoring-oriented audience.
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. 🟢 Preserves uncertain preventive relevance and strength, activity, and nutrition outcomes.
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 terminology is used; no anti-aging framing.
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. 🟢 Oral route and clinical scientific terminology are retained without colloquial administration terms.

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 specified fixed headings, tiers, and monitoring column names are unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Compared the template variable names with the QRS: none are missing.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Populated variable regions correspond to the checklist; website-managed spans remain 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” N/A N/A: no empty source section requires a visible empty-state statement; absent tiers are hidden under 12.5 and 13.5.
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 and qualitative labels match the ER. Gate labels omit trailing caution text in accordance with 9.4.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Outcome, risk, marker, protocol, and qualitative labels preserve the source labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators appear in the QRS.
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. 🟢 Source includes A4 page rules and compact print-specific typography, spacing, and grids; checked as HTML source only.

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 immediately follows the doctype.
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 and closing YAML delimiters are present within 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. 🟢 Metadata is contained in the HTML comment; visible date and model are the separately required header fields.
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. 🟢 Values are trimmed; duration is quoted because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename matches the named 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 matches 26.9.27.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 Creation timestamp uses the required 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]” 🟢 Creator nickname is present.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT is a single-word model nickname.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Creator full name is present.
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) 🟢 GPT 6 consists of nickname and version without additional qualifiers.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the target basename.
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. 🟢 No leading or trailing value whitespace or unnecessary quotation marks.

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 &) 🟢 Canonical topic and required suffix match; 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., &amp; for &) 🟢 Header topic matches the ER canonical topic with HTML encoding.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 matches the creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model matches GPT 6.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only fixed template header content and required fields appear.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opens by identifying a traditional medicinal plant and its supplement uses.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the ER conclusion into uses, signals, conflicting outcomes, safety uncertainty, and evidence boundaries.
7.3 [at_a_glance] is no longer than 70 words 🟢 58 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each statement maps to the ER conclusion: identity, positive signals, conflicts, preparation dependence, safety, and unestablished preventive outcomes.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No specialist acronyms or technical classifications.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes, or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numerical effect sizes or statistical results.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER interaction and avoidance section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four avoidance populations are represented.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each avoidance item is enclosed in li tags.
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. 🟢 Items contain the key avoidance fact and concise decision qualifiers.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 Retains unexplained low platelets, prior suspected reaction, active bleeding, and lack of a safe cutoff.
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 N/A: source avoidance bullets contain no ranking symbols.
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. 🟢 Section is populated because avoidance populations are identified.
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 N/A: contraindications are populated.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 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 remaining interaction categories are listed; transplant medication is covered in the contraindications gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each interaction is enclosed in li tags.
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. 🟢 Interaction categories retain concise examples and decision qualifiers without mechanistic discussion.
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). 🟢 Named medicines, supplements, fasting/exercise exposures, and the qualified two-week interruption are 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 N/A: source interaction bullets contain no ranking notation.
9.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. 🟢 Section is populated because interaction concerns are identified.
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 N/A: key interactions are populated.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Regimens are derived from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Three cells cover metabolic, joint-symptom, and bone-study implementation.
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 N/A: at least three distinct implementation aspects exist.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Every action label, dose value, duration, and qualification is populated from the ER.

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 leading procedural bone, joint-function, and weight/body-fat outcome timings.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Prioritizes the measured local bone-formation signal, then the substantial reported joint-symptom change, then the smaller inconsistent weight change; the ER supplies no common scale for comparing these different outcomes.
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 N/A: at least three time-to-effect aspects are available.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Six months after implantation, eight weeks for joint symptoms, and six to sixteen weeks for metabolic assessment match 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 N/A: the ER supplies time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Tier descriptors derive from Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit variables are retained.
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. 🟢 Uses compact outcome names without effect sizes, study details, or explanatory clauses.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parenthetical study details are absent.
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 empty High tier is hidden with CSS display: none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Tier descriptors derive from Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk variables are retained.
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. 🟢 Uses the ER risk headings without added explanations or study details.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parenthetical study details are absent.
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. 🟢 Empty High and Medium tiers are hidden with CSS display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Monitoring rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight source-table markers are listed.
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. 🟢 Includes baseline, one-to-two-week tolerability, eight-to-twelve-week outcomes and justified laboratory repeats, and earlier symptom-driven assessment.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative entries derive from the ER monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Joint function, sleep and tolerability, and functional success are all included.

Issues 27/09/2026 22:09

Pass rate 100.00%. No issues found.