# Pascal Signal Flows

Source: https://www.trypascal.io/platform/signal-flows

A data change. A clear next step.

Investigate changes in your data, bring a proposed response to review, and follow it through to a confirmed result.

## Capabilities

### Schema Drift Repair

A source schema changes. Investigate the affected relationship and bring a cited mapping proposal to review. Saving the proposal leaves the live mapping unchanged.

### Quality Anomaly Investigator

A quality check flags an anomaly. Gather the supporting evidence and return a cited diagnosis for the team, without changing data.

### Materialization Triage

A refresh fails. Investigate the failure and propose a reviewed dry run or live materialization run. Keep the confirmed run attached to the investigation.

### Object Set Watcher

Records enter or leave an object set. Investigate the change and propose running an allowed Workflow, with its scope and review requirements attached.

### Model Monitor Analyst

A model monitor raises a signal. Inspect the retained production evidence and propose an Evaluation run to investigate the behavior.

### Destination Sync Guard

A destination sync fails. Investigate the failure and prepare a writeback proposal for review. Sending the change to the external system remains a separate step.

## Connected context

Bring source events and agent investigations into one record. Use the findings to propose a mapping change, refresh a dataset, start a Workflow, evaluate a model, or prepare a destination update.

- Source streams, object sets, materializations, model monitors, and destinations
- Saved source evidence, released agent deployments, allowed actions, and review policies
- Immutable flow versions, run histories, review decisions, and owner confirmations

## Controls and permissions

Choose the source, agent, allowed actions, and reviewers. Test a draft without live changes, then publish and activate it. Each run keeps its evidence and decisions, including any result that still needs confirmation.

## Example

The Orders stream renames customer_id to customer_reference. An active schema guard brings the before-and-after schema and mapping evidence into an investigation. Pascal proposes a change to one source mapping, preserving the customer relationship. A data operator reviews the exact proposal. Object Binding confirms that the approved proposal was saved. The run retains the evidence, approval, and confirmation; applying the mapping is a separate action.

## Workflow

### Set the response before the signal arrives

- Orders schema guard watches the source, brings the schema and customer mapping into the investigation, and requires a data operator to review any proposal. Version 3 is confirmed live in this example.

### A renamed field starts the investigation

- The Orders stream replaces customer_id with customer_reference. Open the run to see the source event and the customer relationship that needs attention.

### See why the agent proposes a change

- Read the finding alongside three source references and two checks. The proposed mapping points the customer relationship at the renamed field.

### Review the exact proposal

- The review brings the evidence, before-and-after preview, and affected items together. A data operator decides whether to save the proposal. No source records would change.

### Confirm what actually happened

- The run waits for confirmation after approval. It completes when the mapping service confirms the proposal was saved. The live mapping remains unchanged; applying it is a separate action.

## Next steps

Choose a signal your team already handles. Define the evidence an agent needs, the changes it may propose, and the review required before action.

- [Contact sales](https://www.trypascal.io/contact)
- [People and agents working together](https://www.trypascal.io/solutions/pascal-work)