How Termina determines when a deployment occurred

What Counts as a Deployment

A deployment is recorded when a service’s runtime state changes in an environment.

This may include:

• New application versions

• Configuration updates

• Infrastructure changes

• Rollouts or restarts that affect behavior

The focus is on outcome, not intent.

Signals Used to Detect Deployments

Termina evaluates signals such as:

• Version or artifact changes

• Infrastructure updates

• Runtime transitions

• CI/CD execution outcomes

A deployment is registered only when change is observed.

What Does Not Count as a Deployment

The following do not count as deployments:

• Successful pipeline runs without runtime impact

• Build-only actions

• Metadata-only changes

• Dry runs or previews

Deployments must affect live state.

One Deployment, One Event

When multiple signals represent the same change, Termina:

• Correlates them

• Records a single deployment event

• Preserves source context

This avoids duplicate or misleading records.

Why Deployment Rules Matter

Consistent deployment rules ensure:

• Reliable change history

• Accurate incident timelines

• Trust in production visibility

Loose definitions lead to false confidence.