CS-SRC-003 · SRC Source onboarding, ownership and retirement · 3 of 192
Assess source capabilities and constraints
Integration Engineer · Trigger: A source is proposed for onboarding.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
1 of 3 steps satisfiedAn engineer will see which requested data guarantees the source can and cannot support.
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 satisfiedlifecyclependingapprovalapprovedcustodyverified
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.
not yet satisfiedOperates onACCE-011S. Iyer (Operations Lead) → RGH OT controller C21Access record· OPTIMON-IND / Halol Packaging Line
staterevokedreviewreviewretentioncurrent
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.
satisfiedOperates onEVID-015Asset/Pump-P204 · vibration_velocity evidence 15Evidence chain· OPTIMON-IND / Halol Packaging Line
custodyverifiedcompletenesscompletematurityproposed
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Unavailable capabilities will be explicit rather than inferred from the provider brand.
Alternate path. Ownership cannot be evidenced: retire the source and open a downstream access review.
not yet satisfiedlifecyclependingapprovalapprovedcustodyverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: lifecycle = retired, custody = review
Workflow as specified
CoreSync will record available interfaces, historical depth, timestamp quality, rate limits, maintenance windows, retention, deletion visibility and restart behavior as a versioned capability profile.
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.