Audit: QRS - Kanna for Health & Longevity
Audit conducted on 16/08/2026 21:32 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 populated span traces to ER text: protocol cells to ER Therapeutic Protocol, time cells to ER Practical Considerations “Time to effect”, benefit/risk tiers to ER sub-headings, gates to ER Key Interactions & Contraindications, monitoring rows and cadence to the ER biomarker table, qualitative items verbatim from ER lines 428-433. |
| 1.2 | Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. | 🟢 | No cautious ER phrasing is reworded; the QRS carries ER wording such as “the dose used in every positive human trial” and “the one trial that recorded it” unchanged. |
| 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”). | 🟢 | Avoidance populations stay in the STOP gate at full strength (MAOI, SSRI/SNRI, pregnancy, under-18, bipolar, PHQ-9 >9, uncontrolled hypertension); caution-level interactions stay in the caution gate. |
| 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. | 🟢 | No content from ER Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or risk card; each QRS block draws only from its mapped ER section. |
| 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, author names, NCT identifiers, or brand names; ER brand examples (Robitussin DM, Delsym, Zembrin) were dropped rather than introduced. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind appear outside the fixed template header line. |
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. | 🟢 | Measured, evidence-first register matching the ER; the at-a-glance mirrors the ER Conclusion framing of a narrow, thin evidence base. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and doses are paired with plain-language rationale in every sub-line. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as observed evidence (“the design under which the anxiety effects were demonstrated”), not as instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives directed at a reader; monitoring targets are presented as functional ranges carried from the ER table. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommended”, “advised”, “should take”, or equivalent in the QRS’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document body. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are limited to necessary marker and drug-class names carried from the ER; the at-a-glance uses “brain messenger system” rather than transporter terminology. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every list item is a single condensed clause; benefit and risk tiers are semicolon-joined heading distillations. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your” in the rendered content. |
| 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. | 🟢 | Content assumes willingness to run bloodwork, track a weekly anxiety score, and verify a certificate-of-analysis-grade product. |
| 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. | 🟢 | Eight-marker monitoring panel and staged cadence assume a high-effort implementer. |
| 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 consumer framing; the sheet presumes lab access and self-quantification. |
| 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 foregrounds the two decision-relevant hazards (antidepressant stacking, product variability) and explicitly denies a broad mood lift. |
| 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 carries the ER canonical topic “Kanna for 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. | 🟢 | Formal register throughout (“treatment-emergent adverse effects”, “motor incoordination”, “serotonergic”); the few plain terms are carried verbatim from the ER. |
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 headings, gate headings, tier labels, and the Marker/Target/Why column headers match the template byte for byte. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variables are present; the repeatable marker_#_* and qualitative_item_# spans are expanded to marker_1-marker_8 and qualitative_item_1-qualitative_item_6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The non-variable spans website="evidence_review", website="audit", and website="full_review" are unchanged; a structural diff against the template shows no edits outside variable content. |
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 mapped to a QRS variable is empty; the two absent tiers (High benefit, High risk) are governed by items 12.5 and 13.5, which mandate hiding rather than empty-state phrasing. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | “Standard daily protocol”, “Acute situational protocol”, and “Time of day” are the ER’s bold protocol labels verbatim; monitoring row labels match the ER Biomarker column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Protocol and marker labels are verbatim; the three time-to-effect cell labels derive directly from the ER benefit headings they index, since the ER supplies no per-aspect bold label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji codepoints anywhere in the file; the ER’s ⚠️ Conflicted markers and tier squares were stripped. |
| 4.5 | The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. | 🟢 | Every section is condensed to single-clause items; the at-a-glance is 56 words and no ER section was carried at full 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. | 🟢 | The comment opens on line 2, immediately after <!doctype html> on line 1, and closes on line 14 before any other markup. |
| 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 --- on line 3, closing --- on line 13; the preceding descriptive line sits outside the block. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | Contained entirely within the HTML comment; no metadata value is repeated in the header, footer, or any span. |
| 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 so because it contains a colon; all other values are bare and trimmed. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: kanna_2026-0825-1904_Opus_ER.md, matching the ER’s own filename frontmatter value. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: 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) | 🟢 | Line 6: qrs_creation_date: 2026-0816-2120, 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” is nickname plus version with no context-window or tier qualifier appended. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: kanna_2026-0825-1904_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 nine keys including git_user and git_issue; no stray whitespace or unnecessary quoting. |
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: Kanna for Health & Longevity - Quick Reference Sheet, with the ampersand correctly entity-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: Kanna for Health & Longevity, matching the ER canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/16/2026, the correct reformatting of 2026-0816-2120. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: Opus 5, matching the qrs_creator_ai_fullname frontmatter value. |
| 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 holds only the title and the template subline; the ER’s alternate_names list 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 |
🟢 | Condenses the ER Conclusion into mechanism, the three measured effects, the explicit null, and the two decision-relevant hazards. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 56 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct sentence of the ER Conclusion (ER lines 455-457). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “brain messenger system” replaces serotonin-transporter terminology and “prescribed antidepressants” replaces the SSRI/SNRI class names. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | Only the generic phrase “small trials in healthy volunteers” appears; no author, year, or sample size. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No η², Cohen’s d, p-value, or percentage appears. |
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 “Populations who should avoid Kanna” list at ER lines 296-302. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoidance populations are represented, one-for-one, with none added or omitted. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Seven discrete <li> elements inside the stop_items span (lines 571-577). |
| 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 em-dash rationale is stripped: “no safety or efficacy data exist”, “no trial has enrolled anyone below 18”, “serotonergic agents can precipitate mania”, and “the exclusion threshold used in the current recruiting trial” are all absent. |
| 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 14-day MAOI washout, the “under 18” age bound, the PHQ-9 “>9 or any suicidality item above 0” thresholds, and “(above 160/100 mmHg)” are all 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. | N/A | The ER uses no ranking notation inside parentheses anywhere in Key Interactions & Contraindications. |
| 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 seven avoidance populations, and the section is correspondingly 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 eight items come from the ER interaction bullets at ER lines 278-292. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | The eight non-contraindicated ER interactions are carried; the SSRI, SNRI, and MAOI bullets are correctly excluded because they appear in the STOP gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eight discrete <li> elements inside the caution_items span (lines 585-597). |
| 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. | 🟢 | All ER “Caution; …” rationales and “Mitigation: …” clauses are stripped; each item is the bare agent or class name plus its example list. |
| 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 list is preserved and trimmed only where permitted: “(tramadol, triptans, linezolid, lithium)”, “(cough syrups)”, “(diphenhydramine, doxylamine)”, “(5-hydroxytryptophan, L-Tryptophan, St. John’s wort, S-adenosylmethionine)”, “(ashwagandha, L-Theanine, kava, valerian)”, “(roflumilast, apremilast)”. |
| 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 eleven interactions, and the section is correspondingly populated rather than empty. |
| 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 action cells trace to ER Therapeutic Protocol bullets at ER lines 326, 330, and 338. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard daily dose, acute situational dose, and time of day are the three decision-bearing implementation aspects; the remaining ER bullets are informational (half-life, genetics, sex, age) or explicitly untested. |
| 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 well over three actionable aspects; all three 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 carry ER-derived content; no placeholder or empty value remains. |
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 “Time to effect” bullet (ER line 385) names exactly three intervals — within 60 minutes, three weeks, and eight days — and all three are carried. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered situational anxiety, cognitive flexibility, complex reaction, matching the ER Expected Benefits ordering and the descending strength of the reported magnitudes. |
| 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 supplies exactly three time-to-effect aspects; all three sets are populated. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine spans carry ER-derived content; the sub-lines paraphrase ER line 385 without adding facts. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER provides explicit 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 |
🟢 | Every listed item corresponds to an ER Expected Benefits sub-heading. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present at lines 541, 544, 550, and 556. |
| 12.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Each tier is a semicolon-joined list of bare ER headings; no p-values, Cohen’s d, η², sample sizes, or PDE4 mechanism text is carried. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefits span. |
| 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 ER states “No benefit of kanna currently reaches this evidence level” for High, and benefits_high carries style="display: none" with no empty-state text (line 541). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Every listed item corresponds to an ER Potential Risks & Side Effects sub-heading. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present at lines 609, 612, 618, and 624. |
| 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 tier is a semicolon-joined list of bare ER headings; the 14% weight-gain incidence, 39-fold hordenine range, and CYP17 mechanism are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any risks span; the ER’s “(loss of coordinated movement)” gloss is stripped. |
| 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 ER states “No risk of kanna reaches this evidence level” for High, and risks_high carries style="display: none" with no empty-state text (line 609). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | All rows come from the biomarker table in ER Monitoring Protocol & Defining Success (ER lines 415-424). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eight ER biomarkers are present: seated blood pressure, resting heart rate, serum sodium, ALT, AST, morning cortisol, GAD-7 anxiety score, and sleep-onset latency, with targets carried 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. |
🟢 | Lines 753-757 carry the full ER cadence from ER line 413: weekly anxiety score for the first month, blood pressure and heart rate at four weeks, sodium and liver enzymes at three months and then six to twelve months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items come from the qualitative markers list in ER Monitoring Protocol & Defining Success (ER lines 428-433). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present and carried verbatim: subjective calm, task-switching ease, reaction quality, sleep onset and grogginess, appetite direction, and absence of serotonergic excess signs. |
Issues 16/08/2026 21:32
Pass rate 100.00%. No issues found.
Issues 16/08/2026 21:26
- 12.3 — Trailing elaboration in Benefits Low: The
benefits_lowitem at line 552 of the QRS reads “appetite and thirst suppression — not supported by the trial data”; the clause after the em-dash is an elaboration/qualifier that the Low tier already encodes and must be stripped.
Fixes 16/08/2026 21:26
- 12.3 — Trailing elaboration in Benefits Low: Stripped the em-dash clause from the
benefits_lowitem, changing “appetite and thirst suppression — not supported by the trial data” to “appetite and thirst suppression”.