CS-SRC-004 · SRC Source onboarding, ownership and retirement · 4 of 192
Approve an acquisition boundary
Source Owner · Trigger: A proposed flow requests access to data.
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 satisfiedRuntime tests will reject an unapproved field, source object or export destination.
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 satisfiedlifecycledraftapprovalrejectedcustodyunknown
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-012D. Fernandes (Release Manager) → HAL Application API E23Access record· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
stateexpiredreviewacceptedretentionarchived
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.
not yet satisfiedOperates onEVID-016Asset/Furnace-1 · temperature evidence 16Evidence chain· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
custodyunknowncompletenessmissingmaturityconformant
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Requests exceeding approved objects or processing locations will be blocked.
Alternate path. Ownership cannot be evidenced: retire the source and open a downstream access review.
not yet satisfiedlifecycledraftapprovalrejectedcustodyunknown
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: lifecycle = retired, custody = review
Workflow as specified
CoreSync will present the selected objects, read intensity, locality, retention and intended consumers for approval, then bind the approved boundary to deployment.
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.