Glossary

The vocabulary used across Tune.Toys.

Core vocabulary

Toy: The portable authored creation; can be a component or complete application
Patch: Familiar editor/community term for a Toy graph, not a separate file model
Definition / group: Reusable implementation with typed ports and public parameters
Instance: One use of a definition with independent values, DSP state, and observations
Frame: Explicit playable UI bound to one definition in an instance context
Project: Editable Toy source and working assets/history
Release: Immutable resolved content plus evidence and distribution terms
Catalog entry: Mutable title/discovery/visibility metadata pointing to releases
Library: A user's bookmarks, tags, ratings, acquisitions, and installed/cached releases
Player: TuneToys plugin/application that loads Toys; not a general third-party plugin host
Independent plugin: A compiled Toy exported under its own persistent plugin identity

The core vocabulary comes from the product vision. More terms follow, alphabetically.

A connection from one node's output port to another's input port. See Cables and channels.

The server's record that your account may download a paid product.

A small Toy attached to a node page that teaches one idea. See Nodes.

One processing unit in a Patch, such as a delay or an oscillator.

A named numeric value of a node or a Toy, with a range, default, unit and scale. A parameter exposed to a Frame is a public control.

A typed input or output of a node. Types are audio, control and event.

A saved set of parameter values. See Presets.

A publisher's listed offering, with versions, offers, reviews and documents.

An account or team that owns products and a storefront at @handle.

A publisher's public page, designed from validated theme tokens.