CS-AUT-001 · AUT Governed assistance and low-touch integration operations · 173 of 192
Draft an integration from a user-stated data need
Integration Engineer · Trigger: A user describes the required source and consumer outcome.
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 satisfiedThe proposal will be editable, evidence-linked and blocked from deployment until its release requirements are satisfied.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Assistance proposes; a human disposes. Nothing is applied without review and a stated boundary.
Step 1. Restrict the action boundary to proposal only.
satisfiedOperates onSUGG-004Proposed cadence change 4Assisted suggestion· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
reviewpendingboundaryproposal onlyoutcomesuperseded
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: boundary = proposal only
Step 2. Re-run the suite that tests the proposal.
satisfiedOperates onLABR-011Line onboarding blueprint 11 · conformance run 11Laboratory run· OPTIMON-IND / Halol Packaging Line
executionsucceededconformanceconformantacceptancerejected
Moves the record and writes evidence. Permission: test.
Acceptance for this step: execution = succeeded
Step 3. Accept the proposal and stage it against its target.
not yet satisfiedreviewacceptedboundarypermitted with approvaloutcomepending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: review = accepted, outcome = accepted
Exception path
Natural-language intent will not create credentials, approve a new source or activate production by implication.
Alternate path. The basis is weak: reject the proposal and retain the reasoning.
not yet satisfiedOperates onSUGG-004Proposed cadence change 4Assisted suggestion· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
reviewpendingboundaryproposal onlyoutcomesuperseded
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: review = rejected, outcome = rejected
Workflow as specified
CoreSync will produce a proposed flow from approved catalogue metadata and reusable definitions, identifying unresolved access, mapping, policy and contract requirements.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.