At the replacement Netflix Studio Partner page, what fields, separators and padding does the VFX shot and version naming recommendation state?

Netflix's replacement 'VFX Shot and Version Naming Recommendations' page (fetched 22 Oct 2026) recommends underscore-separated fields in the order showID, episode, seq, scene, shotID#, task, vendorID, version (example AGM_104_TCC_067_0010_comp_NFX_v001), 3-4 digit shot IDs usually incremented by 10, versions beginning with v, and consistent field inclusion across vendors and shots within a project. Curator qualifications: The page's own examples mix 3- and 4-digit shot IDs (producer observation, not re-counted); do not infer a single padding rule. Wording inconsistency preserved: one Usage line says 'optional for LLO', other cells say 'optional for IO'. Recommendations, not requirements; live page without revision id. Post-freeze staged offer: L00 decides whether it joins the next intake. Vendor page JSON read; no files named or validated. Limitations: Vendor guidance. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://studiopartner.netflix.net/api/v2/subsites/studio/page/branded-vfx-shot-version-naming-recommendations",
      "note": "studiopartner.netflix.net API page 'branded-vfx-shot-version-naming-recommendations' (title 'VFX Shot and Version Naming Recommendations')"
    }
  ]
}