Contributors

These pages are rendered from the repository's docs/ folder. They describe how the system is built, including work that is planned, and are not the product experience. Each page links to its source file. The complete set, including decisions and delivery records, is in the repository documentation index.

• Product visionTune.Toys lets developers, musicians, curious users and agents create and distribute playable software. It begins with audio instruments and effects and keeps a foundation for logi
• MVP scopeThis document defines the first complete release: the journey that must work end to end, what each capability delivers at each stage, and the acceptance criteria that decide whethe
• System architectureThis document answers three questions for anyone changing the repository: which layer a piece of code belongs to, which folder owns it, and what it is allowed to depend on. Tune.To
• Customizable editor workspaceHow can a creator arrange Patch, Frame Design, Preview, Source JSON, Properties, Layers and History the way they work, and trust that none of it leaks into the Toy? The workspace i
• Patch editorHow does a creator wire a graph on the canvas, and what guarantees hold for every gesture? The patch editor is browser UI over React Flow and the shared authoring operations: every
• Frames and interface compositionThis document answers what a Frame is, how its controls bind to a running instance, which widget kinds exist, and what every host must do when it mounts one. A Frame is a declarati
• Compact nodes and shared interface componentsThis document answers how Patch nodes are sized, how interface components are placed in Patch and Frame Design from one palette, which control faces and displays exist, and the cap
• Shared DSP primitivesThis document answers which processors the shared engine provides, where their numeric contracts come from, and what bounds, latency and evidence apply. The same Rust kernels serve
• Multichannel audio bundlesThis document answers how an audio cable carries 1 to 32 lanes, how widths are inferred through nested definitions, which routers exist, and how each host maps logical lanes to rea
• Execution and optimizationThis document answers how one Rust processing core runs in a browser tab, a DAW plugin and an exported product, what the audio thread may and may not do, and how performance work i
• Trust and service boundariesWhich data is trusted, which code is trusted, and who may do what on which host? This document states the trust boundaries the platform is designed around. It is a design, not a se
• Discovery and public pagesHow does someone who is not signed in find, hear and save a Toy, and how do search engines and social cards see it? This document covers the public routes the API serves, card prev
• Collaborative communityWhat does the full collaborative social community platform require, what exists, and what is still missing? This document is the requirements-and-evidence record for that active ob
• Publishing, libraries and PlayerWhat happens between "I accepted an edit" and "someone else hears it in their DAW"? This document describes the delivery paths that start from one immutable release: web links, the
• Developer platformDeveloper platform design: keys, limits, webhooks, OpenAPI and MCP.
• Authoring for people and agentsHow do the graph editor, the Frame designer, the in-app prompt panel and later CLI/MCP adapters change a Toy without bypassing one another? Every author, human or model, goes throu
• Toy source format 0.1.0This specification governs the portable .toy.json document: what it contains, which references must resolve, which bounds every host enforces, and which parts are still draft. It i
• Releasing TuneToys app versionsHow an app version is built, qualified, promoted and rolled back.
• Container and single-server hostingContainer image, host preparation, promotion and the docs.tune.toys static site.
• Architecture decisionsDated architecture decision records and their status.
• ContributingStart with MVP scope, the architecture overview and the README of the folder you intend to change. AGENTS.md is the working agreement for humans and agents and takes precedence whe