Skip to content

Repository Map (The Rigs)

Use this map to route work to the correct repository within the AeroBeat ecosystem.

Core contract repos

Product and implementation repos

Official current-focus repos

  • aerobeat-assembly-community
  • aerobeat-docs
  • aerobeat-feature-boxing
  • aerobeat-feature-flow
  • aerobeat-input-mediapipe-python

Future-input or future-platform repos still worth preserving

  • aerobeat-input-mediapipe-native
  • aerobeat-input-gamepad
  • aerobeat-input-joycon-hid
  • aerobeat-input-keyboard
  • aerobeat-input-mouse
  • aerobeat-input-touch
  • aerobeat-input-xr
  • aerobeat-ui-shell-mobile-community
  • aerobeat-ui-shell-web-community
  • aerobeat-ui-shell-xr-community

Shared tool/UI repos

  • aerobeat-tool-api (shared API-facing tool lane; keep AeroBeat-owned client/integration surfaces here rather than coupling product repos directly to vendor APIs)
  • aerobeat-tool-settings
  • aerobeat-tool-* authoring products
  • aerobeat-ui-kit-community
  • aerobeat-ui-shell-desktop-community

Shared environment repos

  • aerobeat-environment-core (internal environment package family baseline; reusable environment scenes/resources built on aerobeat-asset-core rather than a new seventh core lane)
  • aerobeat-environment-loader (generic runtime environment loader/bridge for official package-facing environment kinds such as image, video, GLB, and controlled splat requests)
  • aerobeat-environment-gaussian-splat (specialized Gaussian-splat fulfillment/runtime wrapper consumed by the loader or sibling repos that need the lower splat runtime directly)

Planned UGC/API vendor lane

  • aerobeat-tool-api remains the AeroBeat-facing Godot-imported API manager singleton lane
  • aerobeat-vendor-modio is the preferred first provider adapter repo for the current outer-shell path
  • product repos should consume aerobeat-tool-api, not provider SDK/REST code directly

Scope note

A repo existing in the ecosystem does not mean the feature/input/platform is official v1 product scope. The active product slice is camera-first Boxing + Flow on PC first.

This routing map stays focused on active and future-facing lanes. Legacy Dance/Step feature repos are intentionally omitted from the current live map rather than treated as active routing targets.