The first deck
What bounced.one is
bounced.one is a music-collaboration platform. The visible layer is a shareable A/B comparison tool for mixes - its own line: "DAW plugins compare mixes. Web tools share them. Nobody does both." Under it sits the larger system: an extensive asset-management backend and plugins that sync outputs directly from Logic Pro and other DAWs, so versions arrive with provenance instead of being exported, renamed, and texted around.
The backend is in daily production use by the founder and collaborating musicians. The public comparison layer is live and free - and was put up as a deliberate productization experiment: a single layer of a much larger system, published to see what the product shape would look like, with the full knowledge that it would not be promoted. More on why below, because the why is the point.
The problem that made it
Before any of this existed, the workflow was the one every collaborating musician knows: bounce a mix, text the file to the other person, describe in words what changed or what should change, receive a different file back, lose track of which version contained which decision. In the founder's phrase, a total lack of central hubbery. The descriptions were the problem. A mix difference described in a text message is lossy in exactly the way that matters - the words stand in for the thing, and the thing gets lost.
The same shape, built twice
Look at what got built to fix it, feature by feature: versions with provenance. Sync straight from the creation tool. Comparisons captured as shareable state - the exact loop region, the exact alignment, loudness-matched, blind if you want it - so a collaborator opens a link and hears precisely the comparison you set up, not their reconstruction of it. Feedback anchored to that comparison instead of floating in a thread. Sample-level difference detection, because describing a difference in words is lossy and measuring it is not.
That is context infrastructure. Captured intent, preserved decisions, anchored feedback - for music. Deckwright was not derived from a market analysis; the thesis showed up first as musicians failing to describe mixes to each other, got solved concretely in one domain, and then turned out to generalize. The same shape was built twice before it had a name.
Built on the machine before the machine had a name
bounced.one was built using the systems that became Deckwright. Early versions of the Bridge, with officer context cross-pollination - the founder's conviction, then and now, that routing developed context between different reasoning streams is how you get the real power out of inference. Tools were added as the work demanded them. Then early versions of the Mission Board, to govern the work. The platform was not designed and then applied; it accreted around a real project that needed it, one missing capability at a time, and around real musicians who had other things on their minds than keeping track of file versions.
One capability did not exist yet: the Bench. There was no canvas to talk and gesture at, and many hours went where the canvas would have gone. The Bench was designed afterward, against exactly those remembered hours - which is why it is the way it is.
The bounced.one deck still exists inside Deckwright - boards, cards, and decisions. The origin story is not a story; it is a deck.
The shard
Most founders fear that process, because every chip looks like loss. The founder's earlier trade is writing - novels teach you to throw away material you once believed would win you a prize, and to recognize that what you cut was subsidizing what you keep. In two previous startups he watched the shape that needed to change lose out to arguments about staying the course, and did not insist on what he knew. Those companies failed. Would they have succeeded otherwise? Open question. They would have failed far less expensively.
bounced.one is a shard. When the infrastructure growing around it became the more consequential system, the product was chipped from the arrowhead: kept alive, used daily, deliberately not promoted - so that the point of the arrow could be Deckwright. Zero users on the public layer is not neglect and it is not failure to launch. It is what scope discipline looks like from the outside, and it is the specific lesson of the previous companies, applied.
The EP: the system carrying real work
The music project that drove all of this is an EP, We're glad you like it, at ineffectmusic.com. Every track was tracked and mastered through this system - the asset backend, the DAW-sync plugins, the version-comparison tools, mix decisions made through the comparisons the platform captures.
To be direct about what is being claimed: these are demos, not finished cuts, and they are offered here as verification, not as polished releases - evidence that the system carries real creative work end to end, from tracking through mastering, under real collaboration. Judge the pipeline by them, not the polish.
Status, stated plainly
- The backend is operational and in daily production use by the founder and collaborating musicians. That is real usage by people other than the builder; it is not market traction, and this page does not claim otherwise.
- The public comparison layer is live, free, and functional. It has never been promoted anywhere and has no external users - by decision, per the shard doctrine above, not by neglect. It could be launched; launching it is not currently the point of the arrow.
- What this evidences: the systems that became Deckwright produced a complete second product that is not Deckwright, and the context thesis appeared independently in a second domain before it had a name.
- What this does not evidence: external validation of Deckwright. One person built both systems. The collaborating musicians use bounced.one, not Deckwright.
- Forthcoming: a recorded walkthrough of the backend and the DAW-sync plugins doing real work, in the same evidence style as the product walkthroughs. A live walkthrough of the backend is available in diligence meetings.