# Make a staging environment match production again

A staging environment whose settings no longer match production, corrected so testing there is trustworthy.

Category: Release, deploy, and environments
Source: https://letsship.ai/use-cases/bring-staging-into-parity
Published: 2026-08-25

## Goal

Close the configuration drift between a staging environment and production.

## Acceptance criteria

- A configuration diff between the two is produced
- Each difference is closed or documented as deliberate
- Deliberate differences are recorded where the environments are documented
- No production credential or dataset is copied into the lower environment

## What lands as proof

A configuration diff where every remaining difference is annotated as intentional.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Bring {environment} back into parity with production

Description: Close the configuration drift between a staging environment and production.

Acceptance criteria:
- A configuration diff between the two is produced
- Each difference is closed or documented as deliberate
- Deliberate differences are recorded where the environments are documented
- No production credential or dataset is copied into the lower environment

Before you create the issue, diff this repository's environment configurations and replace {environment} with the one that has drifted most.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: close the configuration drift between a staging environment and production. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means a diff of the two configurations, with the drift closed, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.