Audit: QRS - Phosphatidylinositol for Health & Longevity

Audit conducted on 22/08/2026 02:16 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
Pass Rate	100.00%

• Total = Passed + Failed + N/A
• Pass Rate = Passed / (Passed + Failed) × 100
• N/A items are excluded from the pass rate calculation

---

1. General Rules

#	Description	Result	Comments
1.1	Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER.	🟢	Spot-checked every populated span: at-a-glance against ER Conclusion (L397-401), protocol cells against ER Therapeutic Protocol (L284, L290, L294), time-to-effect magnitudes against ER Expected Benefits (L151, L157) and Practical Considerations (L333), gates against ER Key Interactions & Contraindications (L243-264), monitoring rows against the ER biomarker table (L365-371), qualitative items against ER L375-379. All traceable.
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.	🟢	The ER’s “⚠️ Conflicted” markers on the HDL/apoA-I benefit and on gastrointestinal intolerance are carried through as “, conflicted” (L544, L600). Hedges such as “no significant average change” and “no dose validated beyond twelve weeks” are preserved.
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 remain contraindications and interactions remain interactions; no upgrade or downgrade of evidence tiers relative to the ER.
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 only from the ER’s “Populations who should avoid” list; interactions only from the ER’s interaction bullets. No benefit- or risk-modifying factor (ER L176-184, L230-238) appears in any 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 contains no PMIDs, no NCT identifiers, no author names and no brand names.
1.6	The QRS does not introduce new attributions.	🟢	Only generic references to “the larger trial” and “the positive trial”, both mirroring ER wording (L333, L366).

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, explicitly unsettled framing; the at-a-glance reproduces the ER conclusion’s “narrow and divided base” stance.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numbers are given where the ER gives them; plain-language framing in the at-a-glance keeps it accessible without editorializing.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cells describe what was done and observed in the trials rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives directed at a patient; monitoring cadence is stated as a protocol description drawn from ER L361.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrences of “recommend”, “advise”, “should” directed at a reader.
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	🟢	Technical terms retained (apolipoprotein A-I, normolipidemic, phosphoinositide) are the ER’s own and are load-bearing for accuracy; the at-a-glance is entirely plain.
2.8	Information is presented in a concise and very compact manner	🟢	Eleven ER protocol bullets condensed to three cells; contraindication rationales stripped to the gate facts.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”, “your”, or “yours” 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 monitoring ranges and a seven-marker panel presuppose a proactive, testing-oriented 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.	🟢	Split dosing with the largest fat-containing meal and repeat 4- and 12-week laboratory testing are retained without softening.
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.	🟢	No simplified “ask your doctor” framing; the sheet assumes willingness to run a structured 12-week trial with biomarkers.
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 at-a-glance and benefits tiers foreground the conflicted, low-confidence evidence base rather than promoting the compound.
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.	🟢	No occurrence of “anti-aging”; the header 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.	🟢	“Gastrointestinal intolerance”, “alanine aminotransferase”, “apolipoprotein B” and similar formal terms used throughout; the at-a-glance’s plain wording is required by item 7.4 and mirrors the ER conclusion.

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”	🟢	Verified verbatim at L443, L489, L538, L596, L619, L733 (headings), L561, L574 (gates), L544/L549/L600/L604/L610 (tier labels), L623-625 (column headers).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Sixty variable spans present, covering every variable named in this checklist: page_title, header_, at_a_glance, action_1-3_, time_1-3*, benefits, stop_items, caution_items, risks_, marker_1-7_*, monitoring_cadence, qualitative_item_1-5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The non-variable template spans (website="evidence_review", website="full_review", website="audit") are intact and unmodified at L421, L424, L437.

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	N/A	No source ER section that feeds the QRS is empty; every mapped ER section carries content.
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.	🟢	“Dose range used in humans”, “Timing” and “Single versus split dosing” (L447, L461, L475) reproduce the ER’s bold protocol labels at L284, L290, L294 verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels use ER vocabulary — “Fasting triglycerides” and “HDL cholesterol” from the ER benefit headings, “Response window” from ER L361 (“the intervention’s short response window”). Marker names match the ER biomarker table verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points anywhere in the file; tiers are conveyed by <strong> labels and CSS classes.
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 over-supplied section was condensed rather than carried over: 11 ER protocol bullets → 3 cells, 5 benefit headings → 2 list items, contraindication rationales stripped, mmol/L conversions and conventional-range notes dropped from the monitoring table.

---

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.	🟢	Single comment at L2-14, immediately after the doctype at L1 and before <html> at L15.
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 L3, closing --- at L13; the preceding title text at L2 is permitted.
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.	🟢	Contained entirely within the HTML comment; no metadata value is echoed into the body except the model name and date, which are required by items 6.3 and 6.4.
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, correctly, because it contains a colon. No stray whitespace on any value.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	L4: er_filename: phosphatidylinositol_2026-0822-0009_Opus_ER.md, which matches the ER’s own filename field (ER L17).
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	L5: qrs_prompt_version: 26.7.02, matching the version badge at the top of 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)	🟢	L6: qrs_creation_date: 2026-0822-0210, 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]”	🟢	L7: 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” — single word, no version or qualifier.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	L8: 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 number, no context-window or tier qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	L9 states phosphatidylinositol_2026-0822-0009_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.	🟢	Re-verified across all ten keys; only the colon-bearing duration value is 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., & for &)	🟢	L20: “Phosphatidylinositol for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic (ER L8) 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 &)	🟢	L415: “Phosphatidylinositol for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	L419: “08/22/2026”, the correct reformat of 2026-0822-0210.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	L423: “Opus 5”, matching the frontmatter value at L8.
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 subline; the ER’s “Also known as” line (ER L30) was correctly 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	🟢	L432-435 compresses all four paragraphs of the ER conclusion (L397-403) into what the compound is, how strong the case is, and where the harms sit.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“minor fat … steer growth and sugar handling” → ER L397; “narrow and divided base” and the two-trial contrast → ER L399; “Harms are mostly digestive and dose-dependent” → ER L401.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms. “HDL” rendered as “protective cholesterol”, triglycerides as “blood fats”, gastrointestinal as “digestive”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Only “a short trial” and “a larger one”; no author, year, registry number or participant count.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No percentages, ratios or significance claims; the 13%/18%/36% figures appear only in the Time-to-effect cells, where they belong.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items map to the “Populations who should avoid Phosphatidylinositol” list at ER L257-264.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Complete: soy allergy, pregnancy and lactation, CKD 4-5, decompensated cirrhosis, pancreatic exocrine insufficiency / IBD flare, under-18s. Six ER entries, six list items.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	L564-569, six <li> elements inside the stop_items span.
8.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Every ER rationale clause stripped: “where no safety data of any kind exist”, “where circulating inositol is already elevated”, “where bile-dependent phospholipid handling is impaired”, “for whom no dosing or safety data exist”. No dash-trailing content remains.
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).	🟢	“stage 4–5 (glomerular filtration rate below 30)” and “(Child-Pugh Class B or C)” retained; only the unit string and the lay gloss were trimmed, and the staging itself is intact.
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’s contraindication list contains no ranking notation inside parentheses.
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 rather than left 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 seven items map to the interaction bullets at ER L243-255.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All seven ER interaction bullets present; none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	L577-586, seven <li> elements inside the caution_items span.
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	The ER’s Caution/Monitor verdicts and mechanism-plus-mitigation sentences are all stripped; each item is the drug class alone. No dash-trailing content.
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Every ER example-drug parenthetical is carried verbatim: cholestyramine/colestipol/colesevelam, orlistat, cyclosporine/tacrolimus/amiodarone/ketoconazole, A/D/E/K, statins/ezetimibe/fenofibrate/extended-release niacin, lecithin/phosphatidylcholine/phosphatidylserine.
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’s interaction parentheticals are plain comma-separated drug lists with 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.	🟢	The ER identifies seven 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 trace to the ER Therapeutic Protocol bullets at L284, L290 and L294.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing relative to food, and single-versus-split dosing are the three execution decisions in the ER protocol; the remaining bullets are background (half-life, sex, age, genetics) or non-actionable caveats.
10.3	If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	The ER supplies more than three actionable aspects; all three action sets are populated.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine spans populated with ER-derived content; no placeholders remain (L447-484).

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	🟢	Triglyceride response at 2 weeks, HDL response at 2 weeks, and the 12-week overall response window — the only time-to-effect data the ER reports (L151, L157, L333).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered by ER-reported magnitude: 36% triglyceride fall first, then the 13-18% HDL rise, then the non-quantified response window.
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	Three distinct time-to-effect aspects are present in the ER; 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 spans populated (L495-529); magnitudes match ER L157 and L151 exactly.
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 (ER L333), so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All five benefit headings from ER L147-171 are represented across the Low and Speculative tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at L540-548.
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.	🟢	Reduced to the ER’s own benefit headings; the ER’s magnitude paragraphs, mechanism sentences and trial descriptions are all dropped. The retained “conflicted” is part of the ER heading itself (ER L147) and is required by item 1.2.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in either benefit list item; the ER’s gloss “(HDL’s main protein)” was correctly dropped.
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 are empty with style="display: none" (L540-541), matching ER L143 (“No benefit … reaches high or medium confidence”).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All six risk headings from ER L193-225 are represented across the Medium, Low and Speculative tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at L598-608.
13.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢	Each item is the ER heading alone; the ER’s magnitude paragraphs, dose thresholds and trial details are omitted. “Conflicted” is part of the ER heading (ER L193).
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in any risk list 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 is empty with style="display: none" (L598); the ER’s highest risk tier is Medium.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows map one-to-one onto the ER Monitoring Protocol & Defining Success biomarker table (ER L363-371).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven ER biomarkers present: HDL cholesterol, apolipoprotein A-I, triglycerides, apolipoprotein B, alanine aminotransferase, gamma-glutamyl transferase, high-sensitivity C-reactive protein. No additional measurable marker appears in the ER narrative (L359, L361).
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.	🟢	L725-726 reproduces ER L361: baseline, lipid panel and liver enzymes at 4 and 12 weeks, then every 6-12 months if continued.

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” list at ER L375-379.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	Five ER qualitative markers, five list items, carried verbatim: stool consistency and frequency, bloating/nausea/upper abdominal fullness, appetite and body weight, afternoon energy, tolerance of fatty meals.

Issues 22/08/2026 02:16

Pass rate 100.00%. No issues found.