CS-DB-005 · DB Database snapshots and change-data capture · 55 of 192
Handle primary-key changes and source identity
Data Steward · Trigger: A source changes a key or identifier.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 4 steps satisfiedA key-change test will retain linkage and distinguish changed identity from a genuinely new subject.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A snapshot or change stream is captured, deployed and reconciled against the source of record.
Step 1. Validate the capture definition and its restart position.
not yet satisfiedOperates onFLOW-020SHF Partner SaaS B20 → canonical flowFlow definition· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
definitionreviewdeploymentblockedruntimeHealthhealthy
Moves the record and writes evidence. Permission: test.
Acceptance for this step: definition = approved
Step 2. Deploy the capture to its placement.
not yet satisfiedOperates onFLOW-027HAL Document library C27 → canonical flowFlow definition· OPTIMON-IND / Halol Packaging Line
definitionapproveddeploymentcanaryruntimeHealthdegraded
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: deployment = released
Step 3. Inspect the run ledger for the capture window.
satisfiedOperates onRUN-034NGD File drop F6 → canonical flow · run 20260933Flow run· OPTIMON-IND / Nagda Warehouse
executionpartialadmissioncompletedeliverypartial
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: evidence entry written
Step 4. Verify reconciliation against the database's own counts.
satisfiedOperates onRECO-013Replay — RGH Mobile capture C9 → canonical flowRecovery plan· OPTIMON-IND / Raigarh Melt Shop
planplannedauthorityapprovedverificationverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: verification = verified
Exception path
Ambiguous key reuse or key collisions will enter identity review.
Alternate path. Capture position is lost: plan a bounded re-capture instead of a blind full reload.
satisfiedOperates onRECO-020Backfill — NGD Historian B2 → canonical flowRecovery plan· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
planplannedauthorityrejectedverificationverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: plan = planned
Workflow as specified
CoreSync will preserve old and new source identities and route the change through an approved identity resolution rule rather than silently creating a duplicate canonical subject.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.
Journeys that include it
Not part of a composite journey; exercised through its family views.