bib: two rule items per FR document for 2019-16041 and 2024-14828 — merge to one key #836
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found 2026-09-24 while de-duplicating search results: two Federal Register document numbers have two bib
ruleitems each, both withfr_anchors, so every paragraph of those rules is indexed twice in therulescollection under different item keys and cited twice (same label).VXSUDWCR(url dated 2024/08/02, fr_page 61382, cms_id '') andXFGGRBDH(url dated 2024/07/31, fr_page 61596, cms_id 0938-AV33) — the public-inspection vs publication URL of the same document.Q8R92EHTandMAE2WDTG.Retrieval side is patched (
llm.search.dedupe_by_label, and the chat merges by label), but the duplicates still cost index space, double thecode_eventanchors that reference both keys (e.g. 99441/99490 lineage rows cite both VXSUDWCR and XFGGRBDH), and split tags. Fix at the source: pick the publication-date item as canonical, re-pointfr_anchors,fr_anchor_docs,pfs.code_event/code_element/code_guidancerows, tags and Zotero links to it, delete the twin, thenstack llm index --collection rules --force --key <canonical>andstack llm prune-rules. Add a uniqueness check onextra_json.document_numberfor rule items instack bib discover-pfs-rulesso it cannot recur.