Audit: QRS - Tetradecylthioacetic Acid for Health & Longevity

Audit conducted on 27/06/2026 03:24 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 87
Failed 0
N/A 4
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 content traced to ER (dose, time-to-effect, benefits, risks, contraindications, interactions, monitoring).
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. 🟢 “clinically unproven”, “no circadian data”, “suggested” preserve ER’s cautious register.
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”). 🟢 Contraindications kept as hard stops (Pregnancy, Breastfeeding); no strengthening/softening detected.
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 and Interactions both drawn from ER “Key Interactions & Contraindications”; no cross-category relabeling.
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 IDs, expert names, or brands appear in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions 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. 🟢 Objective, cautious tone mirrors ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert yet accessible; data-driven framing throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence; no prescriptive directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No advice phrasing; footer disclaimer present.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Descriptive phrasing (“suggested”, “used”) rather than recommendation.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain-language at-a-glance; technical terms minimized.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cells, lists, and table.
2.9 It DOES NOT address the reader directly 🟢 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. 🟢 Framing targets risk-aware optimizers (monitoring, sourcing caveats).
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 an engaged, effort-willing audience.
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. 🟢 Detailed biomarker monitoring is not general-population framing.
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. 🟢 Weighting reflects experimental, unproven status for a proactive 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. 🟢 “longevity” used; no “anti-aging” voice.
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 used; “blood fats” appears only in plain-language at-a-glance per 7.4.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified (card/section headings, gate headings, tier labels, Monitoring column headers) 🟢 All fixed headings/labels present and unmodified (Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, tier labels, Marker/Target/Why).
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All fixed-name spans present; repeatable marker_#/qualitative_item_# correctly expanded.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Unaddressed spans 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” 🟢 No empty source sections that required surfacing; empty tiers hidden via display:none per 12.5/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 labels (“Standard dose range (as studied)”, “Best time of day”, “Single versus split dosing”) match ER bold labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels match ER 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 present.
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 condensed; semicolon-joined tiers and trimmed cells keep to one page.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Metadata comment is first element after doctype (lines 2-14).
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 — on lines 3 and 13.
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. 🟢 Inside HTML comment; not rendered.
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 is quoted (contains colon); all others clean.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: tetradecylthioacetic_acid_2026-0627-0130_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]” 🟢 qrs_prompt_version: 26.5.18 matches 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-0627-0130.
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) 🟢 “Opus” is a single word.
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 4.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) 🟢 “Opus 4.8” — nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: tetradecylthioacetic_acid_2026-0627-0130_Opus_QRS.html.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Values trimmed; only colon-bearing duration quoted.

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 &) 🟢 “Tetradecylthioacetic Acid for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Tetradecylthioacetic Acid for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 06/27/2026 from 2026-0627.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8”.
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 contains only title and standard subline; no extra content.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distills Conclusion (lines 388-392) into a dense summary.
7.2 [at_a_glance] is no longer than 60 words 🟢 57 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to Conclusion passages.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; uses “blood fats”, “fat-burning machinery”.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial citations.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER line 248 “Populations who should avoid TTA”.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All ER avoid-populations represented.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> items.
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 — these trailing clauses are stripped. Just the key fact. 🟢 Concise; no trailing dash 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. 🟢 “(e.g., Child-Pugh Class B or C)” and “(NYHA Class III–IV)” 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. 🟢 No bare ranking symbols carried through.
8.7 If no [stop_items] are present the section is left empty N/A stop_items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER interaction bullets (lines 236-246).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Six interaction items; none overlap contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Six <li> items.
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 — these trailing clauses are stripped. Just the key fact. 🟢 Concise; no trailing dash clauses.
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. 🟢 Example drug lists preserved (fenofibrate, gemfibrozil; pioglitazone, rosiglitazone; warfarin, aspirin, clopidogrel; etc.).
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. 🟢 No bare ranking symbols.
9.7 If no [caution_items] are present the section is left empty N/A caution_items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER Therapeutic Protocol (lines 266-291).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose range, timing (with meals), single vs split dosing.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A Three distinct aspects exist; all three used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action sets fully populated from 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 🟢 ER supplies two distinct time-to-effect facts (animal lipid change days-to-weeks; human none-within-a-week); both used, third hidden.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered around the primary benefit (lipid lowering).
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. 🟢 Third set empty and display:none (line 503).
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used time sets populated from ER line 321.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER Expected Benefits (lines 136-172).
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. 🟢 Tiered headers condensed into key facts only.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried into benefits.
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 and benefits_medium set to display:none (lines 521, 524).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from ER Potential Risks & Side Effects (lines 188-218).
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. 🟢 Tiered headers condensed into key facts.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “(Phase 1)” stripped from “Mild, transient adverse events”.
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 set to display:none (lines 568, 571).

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol & Defining Success (lines 343-357).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 7 ER biomarkers present (TG, chol panel, ALT/AST, glucose, HbA1c, insulin/HOMA-IR, hs-CRP) with targets matching ER.
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. 🟢 Cadence matches ER lines 345-347.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER qualitative markers (lines 359-364).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 4 ER qualitative markers present.

Issues 27/06/2026 03:24

Pass rate 100.00%. No issues found.

Issues 27/06/2026 03:18

  1. 7.4 — Technical term in At-A-Glance: The At-A-Glance text (line 433) uses “mechanistically interesting”, a clinical-register term a non-specialist would not use unprompted with exact meaning; a plain-language phrasing is required.

Fixes 27/06/2026 03:18

  1. 7.4 — Plain-language At-A-Glance term: Replaced “mechanistically interesting” with “biologically interesting” in the At-A-Glance text (line 433) to remove the clinical-register adverb while keeping ER support.

Issues 27/06/2026 03:15

  1. 11.3 — Unused time set not hidden: Only two time-to-effect sets are used, but the unused third set (time_3, lines 503-513) is left with empty spans without being made invisible (no display:none on the pcell or a wrapping span), so the third protocol-grid column renders as a blank cell.

Fixes 27/06/2026 03:15

  1. 11.3 — Unused time set not hidden: Added style="display:none" to the unused third time-to-effect pcell (time_3) so the empty third protocol-grid column no longer renders as a blank cell.

Issues 27/06/2026 03:10

  1. 8.4 — Pregnancy parenthetical not stripped: The contraindication “Pregnancy (absolute contraindication)” (QRS line 541) carries an elaboration parenthetical that is not a protected qualifier (threshold/severity class/time window/staging); per 8.4 it should be reduced to just “Pregnancy”.

Fixes 27/06/2026 03:10

  1. 8.4 — Pregnancy parenthetical stripped: Changed contraindication “Pregnancy (absolute contraindication)” to just “Pregnancy”, removing the elaboration parenthetical not protected by 8.5.