Relay Migration Studio · Evidence & scope

A real interface.
Explicit evidence boundaries.

Selected-resource example

Choosing Cedar queue 1 and enabling supported dependency capture produced seven records: the queue, its division, four wrap-up codes and a flow prerequisite. Willow is explicitly selected as the destination. The selected Plan keeps the unresolved flow and queue blocked; no Apply was performed for that example.

Broader programme qualification

The later review, execution and verification scenes use a separate broader programme: 61 captured records, 51 fictional parent creates and 57 table rows, with real local service, planner, SQLite/R2 persistence and immutable receipts. Independent fictional readback produced an all-SKIP repeat Plan without accidental source-ID reuse. A separate lost-response fixture retains uncertainty and a spent attempt without replay.

Live proof remains a separate class

The retained product evidence includes a live, same-organisation inert recreation with readback and restore checks. That does not prove real cross-org portability, operational activation or restoration of unsupported families. Authorised real second-org admission and exact native qualification remain outstanding.

Recorded narration

The full story includes 13 separately recorded, approved Demo Audio Studio chapters, using the selected Google voice. Press Play story to hear them in sequence with their matching scenes. The revised full story runs about four minutes, with 13 separate recordings and short chapter pauses. Chapters 5–13 use simpler language; the first four recordings are unchanged. Narration is embedded for offline playback; no speech service is called while watching. The 90-second overview retains captions and optional device voice; it has no Studio recording.

Coverage and recovery

The catalogue covers 34 resource types, including 11 managed types that support creation or supported updates. Other types have capture, reference or separately controlled native support; the total is not a claim that every type can be fully migrated. An optional name prefix helps distinguish new copies; existing shared resources can be reused unchanged.

Recovery retains before-change snapshots and result records. An explicit encrypted workspace backup can protect them. A reviewed restore can recover supported previous settings, but newly created resources, target-only rows and associations remain. Required dependencies cannot simply be removed in the plan; revise the configuration and rebuild it.

Capture context

Product baseline: Relay PR #67, source revision bf01381. IPI branding captures use a8bfbca / documentation child 4e2f4e1; the separate synthetic lost-response fixture uses b570088. Different takes have different programme IDs and timestamps. The source/evidence reports remain in the private authoring repositories; this public page contains only the audience summary.

Dependencies are checked at export/capture and review. The walkthrough does not claim an instant dependency popup when a checkbox is selected. A linked resource may require recreation, verified destination reuse or a separate qualified native stage.