Audit: QRS - DT-109 for Health & Longevity
Audit conducted on 09/09/2026 13:36 using AI4L / Opus 5
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. | 🟢 | Every gate item, benefit, risk, protocol cell, monitoring row and qualitative item traces to a specific ER passage; monitoring rows and qualitative items are verbatim. |
| 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. | 🟢 | “Not established” (action_3_value), “No human protocol exists” (action_1_sub), “neither pattern has been tested in humans” (action_2_sub) and “No established target exists” (marker_12_target) 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”). | 🟢 | All benefits and risks stay in the Speculative tier as in the ER; contraindications stay absolute; animal-only framing is retained in every protocol and time-to-effect sub-line. |
| 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. | 🟢 | Gates come from Key Interactions & Contraindications, benefits from Expected Benefits, risks from Potential Risks & Side Effects, protocol from Therapeutic Protocol, monitoring/qualitative from Monitoring Protocol & Defining Success. No modifying factors were promoted. |
| 1.5 | PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. | 🟢 | No PMIDs, NCT identifiers, author names or brand names appear; the drug names in the gates are generic names carried over from the same ER bullets. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No investigator, institution, company or source attribution appears anywhere in the sheet. |
2. Focus, Tone & Audience
| # | Description | Result | Comments |
|---|---|---|---|
| 2.1 | The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. | 🟢 | Sober, evidence-tiered, explicitly preclinical framing throughout, matching the ER. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Numeric targets, extrapolated dosing arithmetic and a complete monitoring panel give the reader concrete handles while remaining objective. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | No imperatives or prescriptions; content is presented as what the record shows. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Cadence and gates are stated descriptively; no “should”, “must”, “recommended” or “advised” appears in document voice. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | All cells are declarative statements of the ER record. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are limited to biomarker names and ER benefit/risk headings where no plain equivalent exists; the lede is jargon-free. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Benefits and risks are compressed into single semicolon-separated runs; gate items are stripped to the key fact. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”, “your”, “yourself” in the document. |
| 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. | 🟢 | Functional (not conventional-lab) biomarker ranges, 24-hour urinary oxalate and MRI-PDFF targets address exactly this audience. |
| 2.11 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | A 12-marker panel including a 24-hour urine collection and imaging assumes a high-effort reader. |
| 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 assumes willingness to source, dose and monitor an unapproved investigational compound. |
| 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 lede leads with the absence of human data, the self-contradictory animal record and single-source evidence — the decisive weighting for a self-experimenting 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. | 🟢 | The string “anti-aging” does not occur; 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)”; “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. | 🟢 | The lede uses “has never been administered to a human”; no “pill”, “shot”, “taken by mouth” or similar consumer-grade phrasing appears. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All headings, gate headings and table column headers match the template byte for byte; the rendered tier label “Speculative: “ is unmodified. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variables are present; marker_#* and qualitative_item# are correctly expanded to 12 and 5 instances respectively. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A structural diff against the template shows differences only in variable content and in the legitimate repetition of marker rows / list items; the website="evidence_review", website="audit" and website="full_review" spans, the CSS block and the footer are untouched. |
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 ER section drawn on by the QRS is empty in a way that calls for empty-state phrasing; the empty benefit/risk tiers are governed by the more specific items 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. | 🟢 | “Arithmetic human-equivalent extrapolation”, “Single versus split dosing” and “Best time of day” are the ER’s bold labels verbatim; all five qualitative items keep the ER’s bold label and em-dash gloss verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No ER bold label was altered; monitoring row labels are the ER table’s biomarker names verbatim. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji occur; the ER’s “⚠️ Conflicted” markers were correctly dropped. |
| 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. | 🟢 | Benefits and risks are collapsed to one line each, gate items to bare facts, and protocol sub-lines to single sentences; the mandatory complete lists (items 9.2, 14.2, 15.2) are carried at minimum length. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Lines 2–14; it is the first element after 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 “—” at line 3, closing “—” at line 13; the descriptive text on line 2 sits before 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. | 🟢 | It is an HTML comment; none of its values are echoed on the sheet except through the intended header variables. |
| 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:02" is quoted, correctly so because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: dt_109_2026-0909-1233_Opus_ER.md. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | Line 6: qrs_creation_date: 2026-0909-1323, correctly formatted. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Line 7: qrs_creator_ai_nickname: Opus. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” is a single word with 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]” | 🟢 | Line 8: qrs_creator_ai_fullname: Opus 5. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” = nickname + version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: dt_109_2026-0909-1233_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. | 🟢 | All nine values are trimmed; quoting is used only where YAML requires it. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | Line 22: “DT-109 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 &) |
🟢 | Line 417: “DT-109 for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “09/09/2026”, correctly derived from qrs_creation_date 2026-0909-1323. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “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. | 🟢 | The header carries only the title and the template’s own 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 the Conclusion’s four elements — what the compound is, what it did in animals, the absence of human exposure, and the single-source/self-contradictory record. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 55 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to the Conclusion (“small chain of three amino acids”, “reduced liver fat, liver injury, arterial plaque and arterial calcium”, “The animal record also contradicts itself”, “The evidence also comes from a single source”). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “three-part amino acid chain”, “liver fat”, “arterial plaque” and “arterial calcium” are plain-language renderings. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | Directional statements only; no magnitudes or statistics. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items come from the ER’s “Populations who should avoid DT-109” list in that section. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER bullets are represented, with the third split into its two independent conditions (cirrhosis; urea cycle disorder). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 556–562: seven discrete <li> elements. |
| 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. | 🟢 | Each item is a bare condition; “Anyone with a history of…” reduced to “History of…”, “Anyone taking clozapine” to “Clozapine treatment”. No dashes or trailing clauses. |
| 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). | 🟢 | The eGFR threshold “below 30 mL/min/1.73 m²”, the staging “Child-Pugh Class B or C”, “of any type” for hyperoxaluria and the age cut-off are all preserved. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | 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 names six such populations, and the section is correctly populated rather than empty. |
| 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 twelve items come from the ER’s interaction bullets in that section. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All twelve ER interaction bullets are present; clozapine is correctly dropped from the antipsychotics item because it is a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 570–581: twelve discrete <li> elements. |
| 9.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | Every ER “Caution/Monitor — rationale … Mitigation: …” tail is stripped; only the agent or exposure name 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). | 🟢 | All named example drugs are retained (metformin/glipizide/insulin/empagliflozin, olanzapine/risperidone, zolpidem/lorazepam, diphenhydramine/doxylamine, atorvastatin/ezetimibe, semaglutide/tirzepatide) as is the “1 g/day or more” vitamin C threshold. |
| 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 names twelve 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 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 (human-equivalent extrapolation), dosing frequency (single versus split) and timing (best time of day) are the three actionable dimensions the ER’s Protocol section offers. |
| 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 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 variables carry substantive ER-derived content; no placeholders remain. |
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 | 🟢 | The ER’s Practical Considerations “Time to effect” bullet names exactly three; all three are carried. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Liver histology and arterial plaque (the headline endpoints) first, then glucose and lipid changes, then the glutathione surrogate. |
| 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 mentions 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. | 🟢 | “3–5 months”, “Weeks” and “1–2 hours” with animal-only sub-lines, all traceable to the ER bullet. |
| 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 |
🟢 | All nine entries are the ER’s Speculative-tier benefit headings. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present at lines 535–546. |
| 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. | 🟢 | Headings only, semicolon-separated; every explanatory sentence beneath each ER heading was dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content survives; the ER’s “⚠️ Conflicted” markers on two headings were correctly removed. |
| 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 carry style="display: none" and are empty, matching the ER’s empty High/Medium/Low tiers. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All eight entries are the ER’s Speculative-tier risk headings. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present at lines 593–604. |
| 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. | 🟢 | Headings only, semicolon-separated; the explanatory paragraph under each ER heading was 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 is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | risks_high, risks_medium and risks_low carry style="display: none" and are empty, matching the ER’s empty High/Medium/Low tiers. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | All rows come from the ER Monitoring Protocol & Defining Success biomarker table. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 12 ER biomarkers are present, and each name, target and “why” string matches the ER table 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. |
🟢 | “Baseline before any exposure, then four weeks, twelve weeks, then every three to six months, with kidney markers repeated sooner if any stone symptom appears.” — a faithful condensation of the ER paragraph. |
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 markers worth tracking alongside the panel” list. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five are present and verbatim, with the ER’s bold labels and em-dash glosses preserved. |
Issues 09/09/2026 13:36
Pass rate 100.00%. No issues found.
Issues 09/09/2026 13:29
- 2.15 — Lay phrasing in At-A-Glance: [at_a_glance] (line 436) writes “artery plaque and artery calcium”, a lay noun-attributive form, where the ER’s Conclusion (ER line 429) and the QRS’s own [time_1_label] (line 497) use the formal adjectival “arterial plaque” / “arterial calcium”.
Fixes 09/09/2026 13:29
- 2.15 — Formal arterial terminology in lede: Changed [at_a_glance] from “artery plaque and artery calcium” to “arterial plaque and arterial calcium”, matching the ER Conclusion and the QRS’s own [time_1_label]. Word count remains 55, within the 60-word limit.