1.5 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| feedback-notes-are-part-of-the-work-keep-footnotes-endnotes | Standing steward directive (2026-06-28) — footnotes and endnotes are integral to each work and MUST be preserved (converted, never dropped) when graduating a source into the chamber. |
|
Steward directive, 2026-06-28: footnotes and endnotes are integral to each work — keep them. When graduating a source, never drop the notes apparatus as "just references." Convert them to clean portable markdown footnotes ([^N] ref + [^N]: … definition) and retain them; mark them apparatus in the sidecar if non-served, but they stay in the canonical file.
Why: the notes carry argument, attribution, and the author's qualifications — dropping them mutilates the work. (Caught when I served only Taylor's ten chapters and dropped his endnotes + the 59 <sup> in-text markers — wrong.)
How to apply: the EPUB/OCR pipelines already convert footnotes — clean_pandoc_html_residue.py (<sup><a>→[^label]) and clean_epub_residue.py ([N](chunk#nfK)→[^N]). Use them; verify the ref↔definition pairing survives; keep the Notes/endnotes section. The in-text marker AND its definition both stay. Sidecar may scope notes as role: apparatus/citable: false, but they are present in the file. Companion to feedback-engine-sources-become-permanent-chamber-collection.