CS-SRC-002 · SRC Source onboarding, ownership and retirement · 2 of 192
Declare source authority by information type
Data Steward · Trigger: Several systems describe the same operational subject.
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 satisfiedConflicting sample records will retain both origins and follow the approved authority decision.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A source is registered, owned, approved and its custody evidence confirmed.
Step 1. Approve the source and move its lifecycle to active.
not yet satisfiedlifecycleactiveapprovalpendingcustodyreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: approval = approved, lifecycle = active
Step 2. Complete the access review that ownership depends on.
satisfiedOperates onACCE-010R. Mehta (Semantic Steward) → HAL Mobile capture A19Access record· OPTIMON-IND / Nagda Warehouse
stategrantedreviewacceptedretentionheld
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: review = accepted
Step 3. Verify the custody chain recorded for the source.
satisfiedcustodyverifiedcompletenesscompletematurityconformant
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Conflicting authority claims will create a review case rather than defaulting to arrival order.
Alternate path. Ownership cannot be evidenced: retire the source and open a downstream access review.
not yet satisfiedlifecycleactiveapprovalpendingcustodyreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: lifecycle = retired, custody = review
Workflow as specified
CoreSync will bind each information type or field group to an approved authority rule, distinguishing originating measurement, transactional authority and a replicated copy.
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.