COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
1.0
SIGNAL DESK APPLICATION
& MULTI-AGENT HARNESS
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Building the engine was hard in the way I expected. But the moment it worked, a second problem appeared: a mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. I designed the operator's surface three times before I got it right.
[YEAR]
2025-2026
[CLIENT]
Own Product
[TOOLS]
Figma, Claude Design
Codex, Pencil &
Claude Code
I built the engine. Then I built the cockpit to fly it. Two hard problems — and the second one only exists because the first SUCCEEDED. THIS PRODUCT CASE STUDY DEMONSTRATES MY WORK BUILDING A CUSTOM MULTI-AGENT HARNESS AND SIGNAL DESK, A TERAX AI APP FORK I BUILT TO CONTROL IT.
[FOREWARD]
A 24/7 agent system is easy to start and hard to live with. Once you have agents writing code, triaging your inbox, and shipping pull requests while you sleep, the real problem isn't capability — it's control. How do you watch a mind that never stops? How do you step in mid-thought without breaking its flow? How do you trust it enough to walk away, and stay close enough to pull it back with one word? I tried to answer that question three times. Twice as a designer reaching for the familiar shapes — a web dashboard, a desktop app. Once, finally, as a power user who lives in the terminal. The first two were well-built and wrong. The third is the one I keep open all day. This case study is about the engine that made the question urgent, and the interface that finally answered it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
ANDROID WEAR
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
AUDIBLE SLEEP
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
P&G BEAUTY SPHERE
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
FI SMART DOG COLLAR
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
[YEAR]
2017-2026
[CLIENT]
Various Studios
[TOOLS]
Figma, Sketch,
Adobe Creative Suite
COMMERCIAL PORTFOLIO
I'm a designer who builds. Over the last year I built an autonomous multi-agent system that runs my work around the clock — it writes code, triages my inbox, and ships pull requests while I sleep — and then designed the surface I actually use to operate it. Both halves of that sentence turned out to be hard, and the second one surprised me. Building the engine was the kind of hard I expected: architecture, constraints, a year of decisions about how a system should behave when no one is watching. But the moment it worked, a second problem appeared that I hadn't planned for. A mind that never stops is only as useful as your ability to watch it, steer it, and trust it enough to walk away. That's not an engineering problem. It's an interface problem — which means it was mine. So I designed the operator's surface three times before I got it right. Twice I reached for the familiar shapes a designer reaches for, and built them well, and abandoned them anyway. The third one is the one I keep open all day. This is the story of both: the engine, and the three attempts it took to find the right way to hold it.
5. OUTRO
[WHERE DO I GO FROM HERE…]
I set out to build an autonomous partner and discovered, somewhere in the middle, that I was really building two things at once: a system powerful enough to be worth operating, and the operator's surface that makes that power usable by a single human. The engine and the cockpit. You can't design one well without deeply understanding the other — and that, more than any individual screen, is what this project taught me.
The detours mattered. Bumba Desktop and Bumba Controller weren't failures so much as the cost of finding out what shape the answer actually had. A desktop app made the agent a place I visited. A web dashboard made me an observer of work I needed to be inside of. Both were well-built; both were wrong; and killing them is what made SignalDesk obvious. The willingness to throw away good work when it doesn't fit the user is, I think, the most underrated skill in design.
As agents get more capable, intelligence stops being the scarce thing. The scarce thing becomes one person's ability to direct a great deal of it without losing the thread. That's not an engineering problem. It's a design problem — and it's the one I intend to keep solving OVER TIME.
Where it nets out: an engine that runs 24/7 and stops on one word, a cockpit I keep open all day, and a concept — Dreamcatcher — that points at where this goes next. Because the through-line of all of it is the same conviction. As agents get more capable, the scarce thing won't be intelligence. It'll be the ability of one person to direct a great deal of it without losing the thread — to see what it's doing, trust it enough to walk away, and stay close enough to pull it back. That's an interface problem. It's a design problem. And it's the one I intend to keep solving.
NEXT PROJECT
BUMBA MODULAR FRAMEWORK
A RESEARCH PROJECT
I built AN engine. Then I built the cockpit to fly it. Both CHALLENGES taught me that building AN AGENT SYSTEM and operating it are two different problems.
[THE CHALLENGE]
A 24/7 agent system is easy to start and hard to live with. Once agents are shipping PRs while you sleep, the real problem isn't capability — it's control: how do you watch a mind that never stops, and trust it enough to walk away while staying close enough to pull it back with one word? I tried to answer that three times. Twice as a designer reaching for familiar shapes — a web dashboard, a desktop app. Once, finally, as a power user who lives in the terminal. The first two were well-built and wrong. The third is the one I keep open all day.
5. OUTRO
[WHERE DO I GO FROM HERE…]
I set out to build an autonomous partner and discovered I was building two things at once: a system powerful enough to be worth operating, and the operator's surface that makes that power usable by a single human. The engine and the cockpit. You can't design one well without deeply understanding the other. The detours mattered. Bumba Desktop and Bumba Controller weren't failures so much as the cost of finding out what shape the answer had — both well-built, both wrong, and killing them is what made SignalDesk obvious. The willingness to throw away good work when it doesn't fit the user is the most underrated skill in design.
As agents get more capable, intelligence stops being the scarce thing. The scarce thing becomes one person's ability to direct a great deal of it without losing the thread. That's not an engineering problem. It's a design problem — and it's the one I intend to keep solving.
Where it nets out: an engine that runs 24/7 and stops on one word, a cockpit I keep open all day, and a concept that points at where this goes next.
NEXT
