What playable feels like.
I have spent years producing music, and the tools I keep coming back to are the ones where my hands can find the sound without a detour through the manual. Parameter count has almost nothing to do with it.
Perihelion is an attempt to make those relationships feel direct.
The instrument should hand you a sound before it hands you a settings page.
Build around behavior.
The design starts from interactions and sonic consequences, then lets implementation follow. The goal is fewer moments where the musician has to leave the musical idea and become a system administrator.
Why it belongs here
Perihelion looks unrelated to BrainOS or a hand-drawn roller coaster. It is the same study: find the relationship that matters, make it tangible, and refine until the tool disappears into the act.
BUILD → MAKE THE INTERACTION TRUSTWORTHY
BE → LET THE TOOL DISAPPEAR INTO THE ACT