Audit: QRS - ACD856 for Health & Longevity

Audit conducted on 04/09/2026 18:40 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.	🟢	All protocol values, biomarker ranges, cadence, contraindications, interactions, benefit and risk items trace to explicit ER passages.
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.	🟢	“No established protocol; investigational”, “Unknown”, “An unvalidated biomarker, not a cognitive outcome”, “Theoretical tumor-promoting potential” all mirror the ER.
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”).	🟢	Contraindication severity and the “no human efficacy data” framing are preserved unchanged.
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 “Populations who should avoid ACD856”; cautions from the interaction bullets; no Benefit-/Risk-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.	🟢	The QRS carries no PMIDs, no NCT numbers, no author names and no brand names.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

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-limited register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Objective and data-led; the reader is equipped to judge an investigational compound rather than warned off it.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cells state what was studied (“Trials dosed fasted”), not what to do.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Protocol and monitoring content is descriptive of the phase 1 schedule throughout.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No recommending or advising verbs in the document’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained technical terms (lipase, ALT, eGFR, Child-Pugh) are the ER’s own biomarker and classification names and are not avoidable.
2.8	Information is presented in a concise and very compact manner	🟢	Every item is reduced to a short phrase; no ER rationale or citation text carried over.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; no direct 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.	🟢	Framing assumes a reader evaluating an investigational compound for cognitive resilience.
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.	🟢	Monitoring panel and weekly qualitative tracking presuppose that willingness.
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.	🟢	Content depth (six-biomarker panel, day 1/4/8 cadence) is beyond general-population material.
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.	🟢	The trial-only access constraint and the absence of any human efficacy endpoint are both surfaced prominently.
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; the title uses “Health & Longevity”.
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.	🟢	“adverse events”, “oral solution”, “serum lipase”, “brain-wave” (the ER’s own term) — no consumer-grade substitutions.

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 byte-identical to the template, including “Risk & Side Effects” and the “Marker / Target / Why” header row.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; marker_#/qualitative_item_# correctly expanded to marker_1–6 and qualitative_item_1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The website="evidence_review", website="audit" and website="full_review" spans are untouched; the entire CSS block and footer diff clean against 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 QRS-mapped ER section is empty; the empty benefit/risk tiers are governed by the more specific rules 12.5 and 13.5, which forbid 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.	🟢	“Studied regimen”, “Best time of day”, “Food”, “Time to effect”, “Half-life” and all five qualitative labels are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The one non-bold-label cell, time_2_label “Brain-wave changes”, is lifted from the ER sentence “Brain-wave changes were measurable within days of starting.”
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; the ER’s “⚠️ Conflicted” marker was correctly dropped from the speculative risk item.
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 to the minimum set the completeness items (8.5, 9.5, 12.x, 13.x, 14.2, 15.2) mandate; no ER rationale, citation or magnitude text was carried through.

---

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.	🟢	Comment opens on line 2, immediately after <!doctype html> 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 --- line 3, closing --- line 13; the descriptive text on line 2 precedes the block.
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 into the body.
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 requiring it.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: acd856_2026-0904-1534_Opus_ER.md, matching the ER’s own filename frontmatter value.
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, matching the version badge in 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-0904-1813, correct 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.
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)	🟢	“Opus 5” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: acd856_2026-0904-1534_Opus_QRS.html, matching 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.	🟢	Verified across all nine 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 &)	🟢	ACD856 for Health & Longevity - Quick Reference Sheet, matching the ER’s canonical_topic with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	ACD856 for Health & Longevity.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/04/2026 from 2026-0904-1813.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5, matching the frontmatter.
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 the title and the template’s fixed subline; the ER’s “Also known as” line was 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 all four Conclusion paragraphs: mechanism, preclinical case, human findings, and the sponsor-only evidence base.
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.	🟢	Each clause maps to a distinct Conclusion sentence, including “Safety data are thin” and “all data come from the compound’s owner”.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “positive allosteric modulator” rendered as “makes brain cells more responsive to their own growth signals”.
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 numeric results of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items come from the “Populations who should avoid ACD856” list in that section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are represented, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five 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 ER’s trailing em-dash clauses (“— the compound is not approved…”, “— no reproductive or pediatric data exist”) and the “since clearance is entirely metabolic” rationale are all stripped.
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).	🟢	“3× the upper limit of normal” and “(Child-Pugh Class B or C)” are retained; only the ER’s explanatory glosses were trimmed.
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 ER does identify such populations and the section is correctly 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	🟢	All nine items map one-to-one onto the nine interaction bullets in that ER section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	No overlap with the five contraindication items.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine well-formed <li> elements inside the 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.	🟢	The ER’s “Caution — additive cholinergic excess”, “Caution — additive mood activation” and all “Mitigation:” clauses are stripped; the surviving “(potentiating, benign)” is a severity class that 9.5 requires preserved.
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 in trimmed form; none is dropped entirely.
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 ER identifies nine such interactions and the section is correctly 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 derive from the ER “Therapeutic Protocol” bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/schedule, timing, and food are the three actionable bullets; the remaining bullets are comparative or explicitly non-actionable (“no evidentiary basis”, “entirely unknown”).
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 provides three or more 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.	🟢	All nine fields populated from the ER; the “No established protocol; investigational” caveat is carried into action_1_sub.

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	🟢	Clinical time-to-effect (unknown), the brain-wave biomarker timing, and half-life/steady state/washout are the only time aspects the ER supplies.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered from the headline clinical endpoint down to the pharmacokinetic parameter, consistent with the ER’s own weighting.
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 provides three 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.	🟢	All nine fields populated from the ER; time_3_sub pairs the ER’s steady-state statement with the washout figure from Discontinuation & Cycling.
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; the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All seven items are the ER’s speculative benefit sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present.
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 item is the ER heading alone; no supporting sentence, citation or magnitude was carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in the benefits item.
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, benefits_medium and benefits_low are all style="display: none" and empty, matching the ER’s three empty tiers.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Three Low items and four Speculative items match the ER sub-headings exactly.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present.
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.	🟢	The ER’s “Magnitude:” lines (2 of 24, 1 of 6) and all citations were correctly dropped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in either risk item.
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 and risks_medium are style="display: none" and empty, matching the ER’s two empty tiers.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table rows come from the ER “Monitoring Protocol & Defining Success” biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All six ER biomarkers present: serum lipase, serum amylase, ALT, eGFR, prolactin, serum brain-derived neurotrophic factor. Targets and “why” text are verbatim.
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.	🟢	Reproduces the day 1/4/8 schedule, the two-week follow-up, weekly questionnaires, steady-state recording, and the 4/12-week then 6–12-month outpatient extension.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items come from the ER’s qualitative marker list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers present with their bold labels verbatim: cognitive clarity, memory, mood and drive, sleep quality, pain sensitivity.

Issues 04/09/2026 18:40

Pass rate 100.00%. No issues found.

Issues 04/09/2026 18:31

1. 1.3 — Hypothetical schedule stated as fact: [monitoring_cadence] at line 709 renders the ER’s conditional “A longer outpatient schedule would repeat the panel at 4 weeks, 12 weeks” (ER line 387) as the declarative “A longer outpatient schedule repeats the panel at 4 and 12 weeks”, strengthening a hypothetical into an asserted schedule.
2. 11.4 — Time-to-effect cell contradicts itself: [time_2_value] states “Within days” (line 514) while [time_2_sub] states “Measurable within hours of the dose” (line 518); the sub was taken from the ER’s “Best time of day” bullet (ER line 314) instead of the ER’s own time-to-effect wording “measurable within days of starting” (ER line 361).

Fixes 04/09/2026 18:31

1. 1.3 — Hypothetical outpatient schedule restored: Changed [monitoring_cadence] from “A longer outpatient schedule repeats the panel at 4 and 12 weeks” to “would repeat”, matching the ER’s conditional phrasing (ER line 387).
2. 11.4 — Time-to-effect cell made self-consistent: Changed [time_2_sub] from “Measurable within hours of the dose” to “Measurable within days of starting”, aligning it with [time_2_value] “Within days” and with the ER’s time-to-effect wording (ER line 361).

Issues 04/09/2026 18:25

1. 4.5 — Key Interactions gate over budget: The nine caution_items (lines 579-598) carry the ER’s full multi-drug parentheticals and render to roughly twenty lines in a half-width column, against nine lines for the parallel Contraindications column, exceeding the per-section one-page budget that item 9.5 explicitly allows trimming to meet; the monitoring_cadence (lines 715-720) is likewise carried at near-verbatim ER length.

Fixes 04/09/2026 18:25

1. 4.5 — Key Interactions gate condensed: Shortened all nine caution_items to one rendered line each by trimming the example drug lists to one or two representatives and compressing the item stems (e.g., “Strong inhibitors or inducers of drug-metabolizing enzymes (ketoconazole, ritonavir, grapefruit juice, rifampicin, carbamazepine)” → “Enzyme inhibitors or inducers (ketoconazole, grapefruit juice, rifampicin)”). Every ER interaction is still represented and no example list is dropped entirely.
2. 4.5 — Monitoring cadence tightened: Condensed monitoring_cadence from the near-verbatim ER sentence to “Pancreatic and liver enzymes on days 1, 4 and 8, then two weeks after the last dose; questionnaires weekly; brain-wave recording at steady state. A longer outpatient schedule repeats the panel at 4 and 12 weeks, then every 6–12 months.”

Issues 04/09/2026 18:18

1. 1.1 / 7.3 — In-vitro finding presented as animal data: [at_a_glance] (lines 434-435) states “In animals it protected nerve cells and restored memory in old mice”, but the ER attributes the neuroprotection to cell culture only (“In cultured primary cortical neurons the compound limited cell death… The basis is in-vitro only”, ER line 150) and its Conclusion says “In laboratory work it protected neurons from stress” (ER line 430).

Fixes 04/09/2026 18:18

1. 1.1 / 7.3 — In-vitro finding presented as animal data: In [at_a_glance] changed “In animals it protected nerve cells and restored memory in old mice” to “In laboratory work it protected nerve cells and restored memory in old mice”, matching the ER Conclusion’s own wording; the revised sentence keeps [at_a_glance] at 60 words, within the limit.