Revisions, runs, and comparison

A saved Capture Session and its referenced State Capsule material are immutable. ScenarioDeck verifies their integrity before use so every checkpoint, Journey, revision, run, and share remains attributable to the exact recorded source.

Overlays

A controlled experiment is represented as a validated overlay rather than an edit to the source artifact.

An overlay may include supported changes such as:

explicit Replay/Local/Block policy for approved routes;
a bounded redacted JSON response patch from the safe editor;
other versioned experiment fields allowed by the current runtime contract.

Captured/source credentials are never inserted into an overlay or forwarded to Local automatically.

Safe response editing

For an eligible replayed JSON response, Desktop may expose a bounded redacted projection in:

Form mode;
Tree mode;
JSON mode.

You review the exact safe old/new diff before applying the overlay.

ScenarioDeck does not expose generic captured request data, headers, cookies, tokens, binary bodies, arbitrary original response payloads, or auth mutation through this editor. Stale, oversized, non-JSON, unsupported, or unverifiable data is not editable.

Save as revision

After an overlay has been applied successfully, choose Save as revision.

The new revision records:

source State Card / Capture Session / Capsule identity
+ approved immutable overlay
+ revision provenance

The source artifact remains unchanged. Returning to the original card/revision restores the original experiment state.

Runs

Every Open, Frozen Journey, or verification attempt produces bounded safe run evidence tied to the exact:

State Card/revision;
source artifact integrity;
selected checkpoint or Journey;
browser mode;
routing/overlay policy;
typed outcome.

Run evidence does not become a raw traffic/body/credential log.

Comparison

From History and comparisons, choose compatible runs from the current Desktop session to inspect supported aggregate differences.

ScenarioDeck may show that an observed response/outcome/checkpoint changed. It does not infer root cause or automatically label the bug Fixed from incomplete evidence.

If two runs are incompatible, partial, integrity-failed, or otherwise unsafe to compare, ScenarioDeck says so rather than inventing equivalence.

Clean verification

Only a completed Clean Session against the exact card/revision may produce Verified. A Development Profile run remains useful for daily work but cannot prove that hidden local profile state was unnecessary.

If verification reports an integrity/provenance failure, stop and recapture or restore the valid artifact. Do not edit artifact files by hand.