Signal Flows: from a schema change to an approved proposal

00:00:00.000 — Set the response
Orders schema guard watches schema changes, uses before-and-after evidence, and requires a data operator to approve the exact mapping proposal. Version 3 is confirmed live.

00:00:06.000 — Follow the source signal
The Orders stream renamed customer_id to customer_reference. The run connects the source event to the affected customer mapping.

00:00:12.000 — Inspect the finding
Three supporting source references and two checks support a proposed field update. Saving the proposal would change no source records; applying the mapping is a separate action.

00:00:20.000 — Review the exact proposal
Data operations reviews the proposal, its evidence, and the before-and-after preview. The consequence is saving an approved proposal, with zero source records affected. No approval is submitted in this recording.

00:00:29.000 — Wait for confirmation
A later saved state shows the review accepted. The action remains unconfirmed while the run waits for the mapping owner; approval alone does not complete the run.

00:00:34.000 — Know what happened
The completed example confirms that Object Binding saved and read back the approved proposal. The run retains its evidence, decision, and confirmed result. The live mapping and source records remain unchanged.