Drift detection

Detected changes

Review supported structural and outcome differences.

Seamward compares structural shapes and fingerprints rather than raw values. Supported findings include field presence, field rename candidates, primitive type changes, and missing expected outcomes.

Baselines

Understand how observations establish comparison evidence.

A baseline is derived from accepted observation evidence for the same integration and operation boundary. Release and commit context help distinguish provider drift from an application deployment.

Finding lifecycle

Follow a finding from detection to incident grouping.

1. A validated observation is stored inside its workspace scope.
2. The worker compares it with the relevant contract or outcome expectation.
3. A normalized finding is persisted and grouped with related evidence.
4. The resulting incident becomes the unit for investigation and repair review.