Presentation QA Lorelog 015: Read-First Review of Nine Records

Maintenance ID: 0.1.00156.lorelog-015 Date: 2026-10-08 Scope: content/lorelog/ — the nine records assigned by workload issue #713 (LLG-0388-EC-ORDER through LLG-0392-SGL)

What changed

• Read all nine assigned records in full, frontmatter through final line. Every assigned file was verified identical to snapshot 8997eebee2a4e620c5dd47fcea97abf515c4cac6 at review time (1,530 source lines total, matching the issue table); no intervening diffs to disclose.
• LLG-0388-EC-ORDER.md line 15: bolded "The second request was approved unanimously." — the reversal the whole record is built on: the calm submission was rejected, the visibly degraded one passed without dissent.
• LLG-0389-AKL.md line 22: bolded "whether gratitude can be reallocated without making the room colder." — the unresolved question the record exists to pose. See needs decision note on the surrounding setext line below.
• LLG-0389-MQM.md line 21: bolded "memorial presence may stabilize tone, but it cannot stabilize arithmetic" — Sister Casserole of Relief's "narrow and devastating" finding, buried mid-sentence; the point where incident becomes doctrine.
• LLG-0390-HAP.md line 22: bolded "no one wants to be recorded as the person who told the absent they had finally become administratively irrelevant." — the reason the appeal can never close. Setext note below applies.
• LLG-0390-KCL.md line 21: bolded "It was grief expressed as metadata." — the definitional verdict the four-step persistence loop resolves into.
• LLG-0391-LAA.md line 36: bolded "It simply declines to call that something authorization." — the archive's own ruling on community-backed urgency; the boundary the record draws.
• LLG-0391-RCD.md line 19: bolded "the phrase has already begun acquiring a legitimacy of its own." — the recursive turn: the corrective euphemism hardening into the next fiction. Setext note below applies.
• LLG-0392-RCS.md line 24: bolded "proof that the town had once bothered to care in public." — the reason the same ribbon became locally original more than once; why the schism cannot resolve.
• LLG-0392-SGL.md line 22: bolded "the administrative embarrassment too evenly distributed to assign with confidence." — the evenly smeared shame that makes clawback impossible. Setext note below applies.

What was deliberately left alone

• All frontmatter, canonical IDs, titles, tags, the relations on LLG-0391-LAA, headings, {#...-2} duplicate-heading anchors, link targets, tables, quoted/documentary material, embedded aphorism/haiku/limerick residue, list-item verse, stanza structure, indentation (including LLG-0391-RCD's indented limerick lines), two-space hard breaks, and trailing spaces on prose lines.
• The --- separator immediately following the closing prose line in LLG-0389-AKL, LLG-0390-HAP, LLG-0391-RCD, and LLG-0392-SGL (text\n--- with no blank line). Boris renders these as setext h2 headings with TOC anchors rather than paragraph + hr; the correct separator form (text\n\n---) is demonstrated by LLG-0380-MATCH and LLG-0399-OCS. Removing an anchor is a protected-region change, so the lines were left exactly as found and flagged needs decision. The bold pivots added inside those closing lines are valid in source and become reader-visible only if the maintainer resolves the separator defect.
• LLG-0389-AKL.md line 34 and LLG-0390-KCL.md line 52: question-form aphorisms carrying ?. double punctuation before the templated "Relief remained outside scope." suffix. Preserved; flagged needs decision.
• LLG-0392-RCS.md line 157: lone U+2019 apostrophe in "it's" inside limerick verse — the same anomaly previously flagged in sibling LIM-LLG-0392-RCS.md. Preserved; flagged needs decision.

Verification performed

• git diff on the nine changed records confirms emphasis markers only; no word, order, ID, link, frontmatter, or whitespace changes.
• BORIS_BIN=/Users/tbuddy/dev/filed.fyi/bin/boris ./bin/validate_graph.sh — passed: Boris graph diagnostics, full Cantilever compile, verse residue check, HTML ID audit, Filed certification.
• Compiled articles inspected: each changed record shows exactly one <strong>; all <br> hard breaks, stanza breaks, and anchors intact. In LLG-0389-AKL, LLG-0390-HAP, LLG-0391-RCD, LLG-0392-SGL the <strong> sits inside the pre-existing setext <h2> (invisible to readers at current styling; .article strong only sets font-weight: 700).
• python3 scripts/check_collection_counts.py — PASS after recounting the changelog trunk and README totals.

Unresolved follow-up

• needs decision items posted on #713: (1) the text\n--- setext-h2 closers in four records — probable missing blank line vs. intentional emphasis quirk; (2) ?. residue punctuation at LLG-0389-AKL.md:34 and LLG-0390-KCL.md:52; (3) the U+2019 apostrophe at LLG-0392-RCS.md:157. The issue stays open until the maintainer resolves or explicitly waives them.