Audit: QRS - Thylakoids for Health & Longevity

Audit conducted on 28/09/2026 02:48 using AI4L + evidence-mcp / GPT 6

Iterations

Summary

Items Count
Total 94
Passed 90
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. 🟢 Dose, timing, benefits, risks, gates, and monitoring are traceable to the named ER; no additional clinical claim identified.
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. 🟢 Uncertainty is retained for interactions, research dosing, time to effect, long-term safety, and practitioner targets; tier cards follow their specific condensation rules.
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”). 🟢 Research use remains distinct from a validated longevity regimen, and avoidance populations are retained without weakening.
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. 🟢 Benefits, risks, interactions, and contraindications remain in their corresponding ER decision categories.
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. 🟢 Kresser is named only for the same glucose ranges; named medicines match the ER interaction section.
1.6 The QRS does not introduce new attributions. 🟢 No new expert, study, or product attribution appears.

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. 🟢 The cautious, evidence-focused tone matches the ER Conclusion.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 The compact account presents possible appetite support alongside practical limits objectively.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Research dose and pragmatic monitoring are identified without prescribing treatment.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No validated longevity regimen or universal glucose-treatment target is implied.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 The populated content describes studies and monitoring context rather than issuing recommendations.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No direct reader address occurs in the populated content; the fixed template disclaimer is preserved.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Clinical concepts are explained in plain terms, including body mass index, appetite-hormone medicines, and average blood glucose.
2.8 Information is presented in a concise and very compact manner 🟢 Short cells, tier lists, and compact monitoring rows maintain a concise format.
2.9 It DOES NOT address the reader directly 🟢 The content uses impersonal statements throughout.
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. 🟢 The lede explicitly addresses relevance to adults with strong nutrition and exercise habits.
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. 🟢 Repeated monitoring and existing nutrition and exercise habits suit an engaged 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. 🟢 The evidence framing assumes active health optimization, with no convenience-only 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. 🟢 The lede limits expected value for already active adults to possible appetite support.
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 sheet uses health and longevity language without anti-aging terminology.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. 🟢 Oral supplements, extract mass, and scientific endpoint names retain formal terminology.

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 fixed section, gate, tier, and Monitoring column headings match the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Programmatic comparison found every template data-qrs-var anchor present, including marker_# and qualitative_item_# anchors.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Populated variables correspond to explicit checklist regions; website integration spans remain unchanged.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” 🟢 No unsupported empty-state wording is introduced; absent benefit and risk tiers are hidden under the specific tier rules.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 Protocol and qualitative labels reproduce their ER bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Visible content labels match the source protocol, benefit, risk, or monitoring labels; no invented endpoint label was found.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators appear in the QRS content.
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. 🟢 A4 print sizing, 9 mm print padding, compact typography, and condensed sections support the single-page design; source-only assessment as required.

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. 🟢 The metadata HTML comment immediately follows the doctype.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. 🟢 A single opening and closing YAML delimiter enclose the metadata.
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. 🟢 The metadata is contained in an HTML comment; visible date and model are the separately required header fields.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Values are trimmed; only the colon-containing duration value is quoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename names thylakoids_2026-0927-2228_GPT_ER.md, matching the supplied staging source.
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 is 26.9.28, matching the prompt badge.
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 uses the required 2026-0928-0240 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 is present as GPT.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT is a single word without 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]” 🟢 qrs_creator_ai_fullname is present as GPT 6.
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) 🟢 GPT 6 consists of the nickname and version only.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the audited HTML basename exactly.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 No unneeded quotes or surrounding whitespace appear in metadata values.

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 &) 🟢 The title uses the ER canonical_topic plus the required suffix, with ampersand entity encoding.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 header_topic matches the ER canonical_topic with ampersand entity encoding.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/28/2026 matches the metadata creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model matches GPT 6.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only template-defined title and subtitle content appears; website audit span remains empty.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 The opening defines plant membranes concentrated into oral spinach supplements and names appetite and weight management.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 The lede condenses the Conclusion into expected value, uncertainty, and nutrition and muscle concerns.
7.3 [at_a_glance] is no longer than 70 words 🟢 Programmatic whitespace word count is 64 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 The Conclusion supports the appetite signal, inconsistent metabolic findings, active-adult relevance, uncertain safety, and unproven lifespan and disease prevention.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 The lede contains no unexplained acronyms or specialist classifications.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No named trial, year, participant count, or p-value appears in the lede.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numerical effect size or statistical result appears in the lede.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 The avoidance list comes from the ER Key Interactions & Contraindications section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Allergy, pregnancy and breastfeeding, children, underweight, eating disorders, undernutrition, and unintentional weight loss are retained.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Every contraindication is contained in an li element.
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. 🟢 Contraindications contain key facts and decision qualifiers without explanatory 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). 🟢 Supplemental-dose scope, active eating disorders, ongoing weight loss, and the body mass index threshold below 18.5 kg/m² are retained.
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 unexplained ranking notation is carried into the avoidance list.
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 section is populated because the ER names avoidance populations.
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 Condition does not apply: stop_items is populated.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 The interaction list comes from the ER Key Interactions & Contraindications section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 The list covers antibiotics, other mineral-sensitive medicines, warfarin, glucose-lowering medicines, other weight interventions, nonprescription orlistat, and supplements.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Every interaction entry is contained in an li element.
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. 🟢 Items are compact medicine or supplement lists; retained parentheticals identify product applicability and untested status rather than elaborate mechanisms.
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). 🟢 Ciprofloxacin, doxycycline, levothyroxine, alendronate, glipizide, semaglutide, orlistat, psyllium, glucomannan, and berberine are preserved with relevant applicability qualifiers.
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 unexplained ranking notation is carried into the interaction list.
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 section remains populated because the ER identifies relevant interactions.
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 Condition does not apply: caution_items is populated.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action cells derive from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Research dose, meal timing, and single versus divided doses cover the three main implementation aspects.
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 Condition does not apply: three distinct actionable aspects are available and 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 action fields contain source-supported dose, timing, formulation, or uncertainty information.

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 🟢 Both supplied time horizons are included: appetite changes within hours and body-weight evaluation over weeks to months.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 The higher-evidence appetite endpoint precedes the low-evidence body-weight endpoint.
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. 🟢 The unused third time cell is empty and hidden with display: none.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 The two used time sets match Practical Considerations and distinguish evaluation time from established weight benefit.
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 Condition does not apply: the ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All benefit descriptors and their tiers derive from Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 The four required benefit variables are 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. 🟢 Benefit entries contain source descriptors without effect sizes, study details, or explanatory additions.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical study, effect, or mechanism content appears in the benefit entries.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 The empty Medium tier is hidden with display: none and has no empty-state sentence.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All risk descriptors and their tiers derive from Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 The four required risk variables are 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. 🟢 Risk entries retain source risk titles without additional study details or mechanistic explanations.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical frequency, severity, or study content appears in the risk entries.
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. 🟢 The empty High and Medium tiers are hidden with display: none and have no empty-state sentences.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Monitoring targets, reasons, and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six quantitative entries are listed: body weight and waist, fasting glucose, HbA1c, lipids, nutrient status, and warfarin clotting test.
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, one-to-two-week symptoms and intake, weekly weight trends, monthly weight and waist, 12-week blood tests, and individualized warfarin checks are included with pragmatic-schedule qualification.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative assessment reproduces the Monitoring section subjective categories.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Appetite and cravings, energy and strength, and tolerance all appear with their corresponding observations.

Issues 28/09/2026 02:48

Pass rate 100.00%. No issues found.

Issues 28/09/2026 02:43

  1. 1.2 / 1.3 — Missing target uncertainty qualifiers: Monitoring target cells and cadence omit “established” from the ER’s absence-of-established-target wording, including “No thylakoid-specific laboratory targets” at QRS line 637. This turns an evidence-status qualification into an unqualified absence claim.
  2. 2.7 — Unexplained technical drug class: Key Interactions at QRS line 579 uses “GLP-1 receptor agonists” without the ER’s plain-language explanation “appetite-hormone medicines.”

Fixes 28/09/2026 02:43

  1. 1.2 / 1.3 — Restored target uncertainty qualifiers: Restored “established” in the weight/waist, lipid, nutrient-status, and warfarin target cells. Changed cadence wording to the ER’s “No thylakoid-specific laboratory target is established.”
  2. 2.7 — Explained technical drug class: Replaced “GLP-1 receptor agonists” with the ER’s “Appetite-hormone medicines,” retaining semaglutide and the combination-uncertainty qualifier.