Use cases

Three jobs where the route map earns its keep. Each names the role, the task before the deadline, the steps, and what “done” looks like.

1. Media-collab API engineer inventorying leftover /v2 callers

Who: A media-collab-api-engineer owning services that upload review links, list assets, and manage project membership via Frame.io.

Task: Before 2026-12-01, find every /v2 client and produce one rewrite ticket instead of five partial PRs.

Steps: Grep for /v2 and legacy hosts; paste paths into the home map; mark non-C2C; copy Markdown; attach the deprecation notice; schedule V4 base + resource renames with owners.

Result: A single pack that lists inventory → /v4 rewrite → smoke tests so Dec 1 is not discovered in production overnight.

2. Platform team mapping teams → workspaces without breaking IDs

Who: Platform eng maintaining stored Frame.io team IDs in an internal CMS.

Task: Migrate stored identifiers and API calls to workspaces / files / folders / version_stacks without orphaning historical links.

Steps: Export ID maps from staging; use the route map’s resource rename hints; dual-write or batch-migrate IDs; verify read paths on V4; re-run the tool after cutover to document “observe.”

Result: Resource renames and base-path rewrites land together, avoiding half-migrated clients that still POST to teams URLs.

3. Device/firmware owner confirming C2C exempt vs must-move

Who: Engineer supporting Camera to Cloud devices that still speak legacy Frame.io paths.

Task: Decide whether device traffic stays on the exempt fork or needs a coordinated firmware + API move before Dec 1.

Steps: Tick C2C on the home tool; read current official exempt language; keep device traffic out of the general /v2 rewrite sprint unless notes say otherwise; document the fork choice beside the exported map for auditors.

Result: App API rewrites proceed without accidentally breaking C2C ingest, and the exempt decision is written down rather than assumed.