Project Structure

Flowinator creates this structure inside the selected project location:

PROJECT_CODE/
  00_Pipeline/
    Metadata/
      project.json
      users.json
      asset_types.json
      Assets/
        Characters/
          index.json
          Duck/
            asset.json
            Default/Rig/Default.json
      Shots/
        index.json
        EP01/SQ010/SH010/
          shot.json
          Animation/Default.json
    Users/
    Config/
  01_Assets/
    Characters/
    Props/
    Environments/
  02_Scenes/
  03_Renders/
  04_Resources/
  05_Publish/
  99_Flowinator_Recycle/

Important folders

Folder	Contents
00_Pipeline/Metadata	Project and user records, lightweight indexes, hierarchy manifests, and per-work-item version JSON data.
Metadata/Assets/*/index.json	Small asset indexes used to populate asset lists without reading version history.
Metadata/Assets/.../asset.json	Asset identity, variants, work types, and work item hierarchy.
Metadata/Assets/.../<Work Type>/<Work Item>.json	One asset work item's work/publish/Live/version metadata.
Metadata/Shots/index.json	Lightweight episode, sequence, and shot index.
Metadata/Shots/.../shot.json	Shot identity and work item hierarchy.
Metadata/Shots/.../<Work Type>/<Work Item>.json	One shot work item's work/publish/Live/version metadata.
01_Assets	Asset workfiles, arranged by type and branch.
02_Scenes	Scene and shot workfiles.
05_Publish	Numbered publishes and stable Live publish files.
99_Flowinator_Recycle	Files moved by Flowinator delete actions.

Do not manually edit JSON files while Flowinator is running. Use the UI for normal changes and keep 00_Pipeline under project backup policy.