Expected outcomes

Technical and business success

Distinguish delivery from the expected downstream result.

A successful HTTP response only proves that an operation was delivered. An expected outcome describes the downstream business object that should appear after a named source event.

Outcome rules

Define the observed operation and its expected result.

Each rule identifies a low-cardinality source event type, the expected business object type, and the maximum allowed delay.

• Keep event types stable across deployments.
• Create separate rules for distinct business results.
• Disable a rule when it should stop participating in evaluation.

Evaluation

See how Seamward evaluates future observations.

Seamward evaluates enabled rules against incoming observations. A missing matching result after the configured delay can become a business-outcome finding and later an incident.