Presentation QA Reference 016: Managed Absence, Entropy, and Ingestion Records
Maintenance ID: 0.1.00218.reference-016
Date: 2026-10-08
Scope: content/reference/fref-0140-ocvs.md, content/reference/fref-0150-mapa.md, content/reference/fref-0160-maii.md, content/reference/fref-0170-lgef.md, content/reference/fref-0180-tdci.md, content/reference/fref-0190-slhr.md, content/reference/fref-0195-fwru.md (issue #787)
What changed
fref-0170-lgef.mdline 11: bolded the definitional contrast,**not a correctness-oriented database**— the distinction the whole entropy framework rests on. The body carried no prior emphasis.fref-0180-tdci.mdline 206: inserted a blank line before the---separator. Previously it sat directly under "Correction: reintroduce constraint, not variation", which compiled that sentence (with "Detection priority: early.") into an<h2>and injected it into the page table of contents. Now renders as paragraph +<hr>, matching every other section boundary in the record. No new emphasis; the record already carries eight bold spans.fref-0195-fwru.mdline 11: bolded**operational distress is externally legible**— the mechanism the title's "Recognizable Urgency" names. The three-paragraph body carried no prior emphasis.- Recounted
content/changelog/source records, including this docket, and set the trunk'sCount:to 125. Recounted README totals to actual: 2,330 pages, 11 trunks, 2,319 satellites.
What was deliberately left alone
fref-0140-ocvs.md: the checklist already carries ~10 bold spans as form machinery (four bolded screening questions, bolded Yes/No branches, "three or more boxes"). The closing couplet ("Over‑coherence is not the absence of error. / It is the absence of texture.") already holds prominence by isolation; added emphasis would be decoration, not pivot.fref-0150-mapa.mdandfref-0160-maii.md: twelve structural bold labels already mark the glossary codes (CAAR/LCGU/STCP/AAOA) and report fields; the records' near-identical bodies were left as the deliberate duplicates they are.fref-0190-slhr.md: all five numbered principles and the four restricted-vocabulary terms are already bolded; no further pivot earned.- All Related Aphorisms / Related Haikus / Related Limericks blocks,
{#...-N}anchors,:::noteliteral fences with their trailing residue verses,[^1]markers, hard-broken verse, margin annotations, and trailing-whitespace residue in all seven records — protected or residue, left exactly as found.
Verification performed
git diff 8997eebee2a4e620c5dd47fcea97abf515c4cac6 HEAD -- <7 assigned paths>: empty — all assigned files identical to the issue snapshot before editing.BORIS_BIN=/Users/tbuddy/dev/filed.fyi/bin/boris ./bin/validate_graph.sh: passed before and after edits (Boris graph diagnostics, full Cantilever compile, verse residue check, HTML ID audit, Filed certification).- Compiled HTML inspected:
FREF-0180-TDCI.htmlnow emits<p>…Correction: reintroduce constraint, not variation</p><hr />and the spuriousdetection-priority-early-correction-reintroduce-constraint-not-variationheading/TOC entry is gone;FREF-0170-LGEF.htmlandFREF-0195-FWRU.htmleach contain exactly one new<strong>;FREF-0140-OCVS.htmlretains 38<br>hard breaks. python3 scripts/check_collection_counts.pyafter mergingorigin/main: see PR body for exact outcome.
Unresolved follow-up
fref-0150-mapa.mdandfref-0160-maii.mdeach carry 22[^1]footnote markers with no[^1]:definition; the same dangling-marker pattern appears incontent/lorelog/map-inc-14.mdandcontent/mascots/672.map-72-absentia.md. The markers render as literal[^1]text. Confined to the MAP-Annex cluster and consistent with its managed-absence theme (footnotes to absent referents), but needs decision: deliberate residue to keep, or a missing footnote layer to restore. Not edited.- The corpus-wide
:::noteliteral-fence question already flagged on #699 applies to the fences infref-0140-ocvs.md,fref-0170-lgef.md, andfref-0180-tdci.md; no new flag opened.