Audit: QRS - Binaural Beats for Health & Longevity

Audit conducted on 31/08/2026 03:30 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 84
Failed 0
N/A 9
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 against the ER: protocol values (ER 331-339), time-to-effect (ER 388, 171), benefit and risk tier headings (ER 155-223, 249-277), gate items (ER 295-311), all 7 monitoring rows (ER 422-428) and all 5 qualitative markers (ER 432-436) are literally supported.
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. 🟢 ER carries no empty-state or hedging phrasing that the QRS restates; the ER’s own cautious framing sits in tier assignment, which the QRS mirrors.
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”). 🟢 No tier promoted or demoted; contraindication thresholds (>25 dB at 4 kHz, >20 dB ear-to-ear gap, 200-400 Hz carrier) carried unchanged.
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. 🟢 Benefit-Modifying and Risk-Modifying Factors (ER 228-236, 282-290) are not surfaced in the gates; Contraindications come only from ER 305-311 and Key Interactions only from ER 295-303.
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 No PMIDs, NCT identifiers, expert names, study citations or brand names appear anywhere in the QRS; instrument names (Pittsburgh Sleep Quality Index, State-Trait Anxiety Inventory) are ER table entries.
1.6 The QRS does not introduce new attributions. 🟢 No 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. 🟢 Matches the ER’s measured, non-promotional register.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective and data-driven; the Protocol panel and Monitoring targets give the reader something actionable without overselling.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 No prescriptive verbs; content is stated, not directed.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Monitoring targets and gates are presented as evidence-derived reference values, matching the ER framing.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No ‘recommend’, ‘advise’, ‘should’, ‘consider’ or ‘ensure’ in the document’s own voice; the only ‘must’ (line 578) is verbatim ER text inside a contraindication.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; the technical terms retained (pure-tone audiometry, RMSSD, dB(A)) are the ER’s own biomarker names and are each preceded by a plain-language descriptor.
2.8 Information is presented in a concise and very compact manner 🟢 Highly compact: ER tier headings reduced to semicolon-joined phrases, mitigations and mechanistic rationale stripped from the gates.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: no ‘you’ / ‘your’ tokens.
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 assumes a proactive reader who will run a baseline audiogram and re-score questionnaires at 4 and 12 weeks.
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 asks for daily 15-30 minute sessions, over-ear headphones and periodic audiometry.
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. 🟢 Not written for a general audience; assumes willingness to track PSQI, STAI and RMSSD.
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. 🟢 Risk weighting reflects this audience: cumulative headphone sound exposure is elevated to the leading risk precisely because daily long-term use is assumed.
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’.
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 in the document’s own voice (‘anaesthetic’, ‘sedative’, ‘analgesic requirement’, ‘adverse’); the single colloquial term ‘painkiller’ sits in [at_a_glance], is lifted verbatim from the ER Conclusion (ER 460), and is required there by item 7.4’s plain-language rule.

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 verified against [qrs_template]: ‘Protocol’, ‘Time to effect’, ‘Benefits’, ‘Risk & Side Effects’, ‘Monitoring’, ‘Qualitative Assessment’, ‘Contraindications’, ‘Key Interactions’, tier labels High/Medium/Low/Speculative, and Marker/Target/Why.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 named template spans present, plus the repeatable marker_#name/target/why (7 instances) and qualitative_item# (5 instances).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Byte-for-byte diff of lines 1-410 of the template against the QRS head/CSS shows changes only inside the metadata comment and the element; the non-variable spans (website="evidence_review", website="audit", website="full_review") and the footer disclaimer are untouched.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” N/A No source ER section is empty and the ER uses no empty-state phrasing (‘Not formally studied’, ‘None documented…’) anywhere; the ER’s Risks/High subsection carries prose (ER 245) and is governed by item 13.5 instead.
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 cell labels reuse the ER bold labels verbatim (‘Standard session’, ‘Anxiety and pain protocol’, ‘Sleep protocol’, ER 331-337); all five Key Interaction labels reproduce the ER bold labels including their drug lists (ER 295-303).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label paraphrased, abbreviated or invented.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Unicode scan for emoji ranges returns nothing; the ER’s tier emoji and the six ‘Conflicted’ warning markers are correctly absent.
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 rather than extended: the ER’s 18 Protocol bullets reduce to 3 cells, the 7-row monitoring table drops the ER’s entire Context/Notes column, and the ER’s per-benefit Magnitude paragraphs are omitted entirely.

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 comment opens at line 2, immediately after <!doctype html>, before <html> and any other comment.
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 opens at line 3 and closes at line 13; the preceding label text on line 2 is outside the delimiters.
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. 🟢 Enclosed in an HTML comment closed at line 14; none of its values are echoed by a visible element.
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. 🟢 All values trimmed; only duration: “00:03” is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: binaural_beats_2026-0831-0002_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.7.02, matching the version badge at the head 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) 🟢 qrs_creation_date: 2026-0831-0328, correct YYYY-MMDD-HHMM form.
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) 🟢 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]” 🟢 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) 🟢 Nickname plus version number only, no trailing qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: binaural_beats_2026-0831-0002_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; no stray whitespace or unnecessary quoting on any of the nine keys.

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 &) 🟢 Binaural Beats for Health & Longevity - Quick Reference Sheet; canonical_topic taken from ER frontmatter line 8, with & entity-encoded.
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] = ‘Binaural Beats for Health & Longevity’, identical to canonical_topic, entity-encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 08/31/2026, correctly derived from qrs_creation_date 2026-0831-0328.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 ‘Opus 5’, matching qrs_creator_ai_fullname.
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 carries only the title and the template’s fixed subline; no badge, version stamp, alternate-names line or audit date. The ER’s ‘Also known as’ list (ER 30) is 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 🟢 Distils the ER Conclusion (ER 460-464) in decision order: what it is, cost, strongest finding, weaker findings, principal risk.
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. 🟢 Each of the six assertions maps to a distinct ER passage: mechanism/cost (ER 460 sentence 1 and ER 398), procedural anxiety and pain plus drug sparing (ER 460), sleep in poor sleepers (ER 460), memory and attention (ER 460), headphone sound exposure (ER 464).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms and no specialist classifications; ‘binaural beat’, ‘entrainment’, ‘EEG’, ‘perioperative’ and ‘analgesic’ are all avoided in favour of plain equivalents (‘a pulsing beat the brain builds itself’, ‘painkiller’).
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes or p-values.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No SMDs, confidence intervals, effect sizes or statistics; ‘modestly’, ‘small and inconsistent’ are qualitative.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All five items trace to the ER’s ‘Populations who should avoid Binaural Beats’ list (ER 305-311) inside Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All five ER avoid-populations are represented, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Five <li> elements inside the [stop_items] span (QRS 571-581).
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 trailing em-dash and comma clause of rationale is stripped: ‘rhythmic sensory drive is the shared provoking mechanism’, ‘adds to an already reduced reserve’ and ‘in whom the beat cannot be constructed at all’ are all removed.
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). 🟢 Threshold and severity qualifiers preserved: ‘that is not fully controlled’, ‘more than 25 dB at 4 kHz’, ‘severe, distress-level’, ‘200-400 Hz’, ‘above 20 dB’, ‘for the duration of a session’.
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 bullets contain 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. 🟢 Section is populated, and the ER does name five populations that should avoid the intervention, so the emptiness condition is correctly not invoked.
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 left empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All five items trace to the ER bullets at 295-303.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All five ER interaction bullets carried; none duplicates a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Five <li> elements inside the [caution_items] span (QRS 589-614).
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. 🟢 Reduced to the ER’s verdict clause only; every ‘Mitigation:’ sentence and supporting rationale (e.g. ‘Randomized data show beats reduce the induction dose needed’) is stripped.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 All four parenthetical drug and modality lists preserved in full: (propofol, remimazolam, midazolam); (zolpidem, zopiclone, trazodone); (diphenhydramine, doxylamine); (melatonin, valerian, L-Theanine, magnesium glycinate, glycine); (cognitive behavioural therapy for insomnia, meditation, breathwork, neurofeedback).
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 bullets contain no ranking notation inside parentheses.
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. 🟢 Section is populated, and the ER does identify additive interactions, so the emptiness condition is correctly not invoked.
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 left empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells derive from the ER Therapeutic Protocol section (ER 331-339).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The three sets carry the ER’s three named dosing protocols: the Standard session (with the ER’s ‘Timing before the task’ bullet folded into its sub-line), the Anxiety and pain protocol, and the Sleep protocol. The Focus protocol is appended to action_3_sub under its own verbatim ER label, which is a legitimate one-page condensation rather than a substitution.
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 names more than three actionable implementation aspects; all three sets are used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine sub-fields populated with ER-derived content; values carry the ER’s numbers (15-30 min once daily; beat 1-10 Hz on a 200-400 Hz carrier 20-30 min pre-procedure; beat 1-8 Hz for 20-30 min at bedtime).

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 🟢 Three aspects: within-session onset for anxiety and pain (ER 388), 20-30 min pre-induction exposure for anaesthetic sparing (ER 171), and at least two weeks of nightly use for sleep (ER 388).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High -> Medium -> Low, matching the ER benefit tiers of the related outcomes (procedural anxiety and pain = High; anaesthetic and sedative requirement = Medium; sleep quality = Low).
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 exist 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 sub-fields populated and ER-supported; time_1_sub, time_2_sub and time_3_sub each paraphrase a single ER sentence without adding figures.
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 388), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All four tiers map to the ER Expected Benefits headings (ER 153-223).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated.
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. 🟢 Every item is the ER heading reduced to sentence case; all Magnitude paragraphs, effect sizes, trial descriptions and the six ‘Conflicted’ markers are dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried; the ER’s inline glosses and pooled figures are absent.
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. N/A All four benefit tiers contain at least one ER item (High 2, Medium 2, Low 6, Speculative 1), so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All tiers map to the ER Potential Risks & Side Effects headings (ER 243-277).
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. 🟢 Each item is the ER heading in sentence case with no rationale, prevalence figure or study detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried; the ER’s pooled prevalence figures and population attributable fraction are absent.
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’s High tier holds no risk item (ER 245), and [risks_high] is correctly emptied and set to style=”display: none” at QRS 626 rather than filled with empty-state text.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol & Defining Success section (ER 414-428).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 7 ER biomarker rows are present in the same order, with Optimal Functional Range mapped to Target and Why Measure It? mapped to Why; the RMSSD target is faithfully condensed from the ER’s two-clause entry.
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. 🟢 Populated from ER 416-418: baseline before starting, questionnaires re-scored at 4 and 12 weeks, hearing test every 12-24 months or sooner if tinnitus or muffled hearing appears.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER’s ‘Qualitative markers worth tracking alongside the numbers’ list (ER 430-436).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 5 ER qualitative markers listed, verbatim and in ER order.

Issues 31/08/2026 03:30

Pass rate 100.00%. No issues found.