Atlas node · Scenes · study / needs proof

drone-chorus

Exploratory drone and spatial-interaction study investigating how aerial or simulated agents can behave as choreographed performers.

Repository →

What it is

drone-chorus is best framed publicly as a candidate interaction study around spatial agents, choreography, telemetry, and control. It should stay at study scale until a safe proof object makes the actual behavior legible.

What it lets people do

It lets the portfolio name an aerial or simulated spatial branch of the practice without pretending that safety, autonomy, or audience readiness have already been proven.

What is public now

  • Project repo Current source trail for the study.
  • Conceptual Atlas placement The public value right now is the relationship between control, choreography, and safety boundaries.

Evidence status

Status: study / needs proof. The repo exists and the conceptual frame is useful, but the page should not imply stable flight, swarm reliability, or public-ready interaction before a bounded proof object is linked.

Next proof object: 30-second simulation or flight capture paired with a one-paragraph safety and operating-context note.

Boundary note

This page intentionally withholds locations, telemetry detail, unsafe test setups, and any audience or camera material that would create privacy or safety risk.

What remains unresolved

  • The current public page does not establish whether the project is primarily simulation, physical flight, or both.
  • A safety boundary note needs to accompany the first visible proof.
  • No public artifact yet supports claims about autonomy or audience interaction.

Methods surfaced

  • live-rig A clear companion in the scene/control branch where routing and performance topology matter.
  • pointy-clumps Shares the telemetry-driven generative logic in a more sculptural register.
  • live-rig-control Useful for understanding the control-layer side of the performance stack.

Source trail

  • Project repo — Implementation truth.
  • Last reviewed: 2026-05-15

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next

  • Open live-rig — See the larger performance-system branch this study could connect to.