Protocol

Dry-run the real-shaped input without the real write

Real data can teach you something before it is allowed to change anything.

About 1 min read

Before you use it

Use when
  • Test fixtures are too clean and production data shape is a major source of risk.

Keep this limit in mind

  • A dry run may miss write-side triggers, locking, permissions and downstream side effects; test those separately before assuming full equivalence.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Run the transformation or decision logic on production-shaped input while suppressing authoritative writes. Capture proposed outputs, errors, counts and performance, then compare them with the live or expected path. This is especially useful for data pipelines, migrations and agent workflows whose failures depend on real input diversity.

Steps

  1. The dry run receives representative production-shaped input.
  2. Authoritative writes and external side effects are disabled or redirected safely.
  3. Outputs and failures are captured for comparison.
  4. Differences are reviewed before live mutation is enabled.
  5. Sensitive production data remains protected under the same access rules.

An example

Run a customer transformation against current records into a temporary table and compare the proposed target fields before enabling update mode.

Check your result

The team has evidence from realistic input without yet exposing the authoritative target to the change.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingDry-run the real-shaped input without the real write

Evidence and sources
Supports

Google SRE describes dry-run or canary pipeline execution that uses production data while skipping writes to production storage.

A no-write path may not exercise all write-side constraints, triggers or downstream effects.

Improve and Optimize Data Processing Pipelines · Canarying data pipelines; two-phase mutation

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details