plans: replace §4 step 2 backfill plan with pivot redirect#803
Merged
Conversation
The pre-pivot plan committed Backend to a five-source backfill (S1=canonical_entity_id, S2=LML entity.identity, S3=flowsheet_match, S4=fuzzy_resolved, S5=semantic-index reconciliation_log). On 2026-05-09 the project pivoted: Backend stops reading LML's PG and consumes a new POST /api/v1/identity/bulk-resolve-libraries endpoint instead. Replaces the 277-line draft plan with a stub redirecting to the decision record (#800), the wiki amendment (WXYC/wiki#25), and the new tickets (wxyc-shared#103, library-metadata-lookup#272, #802). Captures what survives (substrate from #790, S1 self-migration leg, 2.2 spike memo) and what's discarded (dispatch.ts, lml-provenance-index.ts, resolve-s2.ts). Wave 4 of the cross-cache-identity architecture pivot.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the pre-pivot 277-line
section-4-step-2-backfill-plan.md(five-source Backend backfill: S1canonical_entity_id, S2 LMLentity.identity, S3flowsheet_match, S4fuzzy_resolved, S5 semantic-indexreconciliation_log) with a 20-line stub redirecting to the post-pivot artifacts.The cross-cache-identity project pivoted on 2026-05-09: Backend stops reading LML's discogs-cache PG and consumes a new
POST /api/v1/identity/bulk-resolve-librariesHTTP endpoint instead. Decision record atplans/library-hook-canonicalization/architecture-pivot-2026-05-09.md, merged in #800. This PR is Wave 4 of the action plan.What survives, what's discarded
The stub file documents both. Survives: substrate from #790 (
library_identity+library_identity_source+library_identity_history+ dual-table writer + §3.4.1.1 worked-example regression tests) and the S1canonical_entity_idself-migration leg (runs as a one-shot before the bulk-resolve consumer). Discarded:jobs/library-identity-backfill/dispatch.ts,sources/lml-provenance-index.ts,resolve-s2.ts, most ofrecompute.ts(left ~10 lines for Rule 1 manual override; Rules 2-4 moved to LML), and the §3.2.2.1 LML-to-Backend manual-override-skip endpoint.Why a redirect instead of deleting
Future readers searching
plans/library-hook-canonicalization/for "five source legs" or "S2 LML provenance" should land on a document that explains the rescope and points at the canonical artifacts, not get a 404.Related
jobs/library-identity-consumer/(replaces this plan)api.yamlv0.7 contractTest plan