adhoc-edits-workflow

Add the citation definition to the matching research file first, then integrate the prose into the correct section file using the same semantic citation ID. Run the citation assembler to rebuild the final draft, then export HTML and PDF with the branded export script.

Edits made directly to the final draft file are overwritten because it is a build artifact regenerated by the assembler. Prose must live in the section files and citation definitions in the research files to survive re-assembly.

A literal footnote marker means the inline citation reference has no matching definition anywhere, so Pandoc renders it as plain text. Add the citation definition to the appropriate research file and re-run the assembler before exporting.

No, hand-typed numeric IDs are unsafe because the assembler renumbers all citations sequentially on every run. Always use semantic citation IDs so references remain stable across assembly passes.

Use it when the change is scoped to one or a few specific edits, such as adding a customer, correcting a financing detail, or inserting a chart. A full pipeline re-run is only warranted for broad regeneration of the memo.