CS-DIS-004 · DIS Discovery, profiling and acquisition selection · 20 of 192
Detect added, removed and renamed source objects
Integration Engineer · Trigger: A new discovery snapshot differs from the baseline.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 3 steps satisfiedA rename test will retain old lineage and a removal test will expose affected consumers.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Objects are discovered, profiled from a bounded sample and deliberately selected into scope.
Step 1. Re-profile a bounded sample so selection is informed, not guessed.
satisfiedOperates onDISC-025RGH Document library E17 · object 25Discovered object· OPTIMON-IND / Raigarh Melt Shop
selectionselectedprofilecompletedriftstable
Moves the record and writes evidence. Permission: test.
Acceptance for this step: profile = complete
Step 2. Select the object into acquisition scope.
not yet satisfiedOperates onDISC-004NGD Partner SaaS D10 · object 4Discovered object· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
selectionnot applicableprofilemissingdriftstable
Moves the record and writes evidence. Permission: register.
Acceptance for this step: selection = selected
Step 3. Resolve the selected object to its canonical subject.
satisfiedresolutionresolvedconflictstableapprovalapproved
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: resolution = resolved, conflict = stable
Exception path
Similar names will not be assumed to identify the same physical or business subject.
Alternate path. The structure changed since last look: acknowledge drift before anything downstream moves.
satisfiedOperates onDISC-025RGH Document library E17 · object 25Discovered object· OPTIMON-IND / Raigarh Melt Shop
selectionselectedprofilecompletedriftstable
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: drift = stable
Workflow as specified
CoreSync will compare structural changes and propose corresponding binding updates while preserving old source references for historical interpretation.
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.