Eddy · In planning
Before intent, there is a thought
Every product promise starts as something smaller: a passing idea, a decision made in a hallway, a note to ask someone about. Most never become a promise at all. Eddy is planned for that first step.
The step before intent
Most thinking is lost before anyone writes it down
Engineers and product managers working with agents get more done than ever, and so they have more to keep track of: ideas, decisions, questions and things to raise with someone.
Those end up in drafts, sticky notes and the last lines of a chat with an agent. Writing one down properly asks too much at the wrong moment: which folder, which project, is this a task or a note? So the thought waits, and often it is gone.
How they fit
The loop, one step earlier
The home page's five steps begin at intent. We think the loop begins one step before that, when a thought is first written down.
- Capture. Get a thought down the moment you have it, without deciding where it goes. Eddy
- Intent. Write down what the product promises, and who owns each promise. Intentset
- Execution. Plan each change and move it forward, with people and agents on the same work. Streamlane
- Verification. See which promises have a check passing on this commit, and which have no check at all. Intentset
- Release. Record what each release is meant to do for users, before it ships. Driftline
- Feedback. Watch real users meet it, see where adoption stalls and why, and take what you learn back to intent. Driftline
Capture feeds the rest of the loop. A decision becomes a promise, an action item becomes shared work, and what a team learns from use comes back as the next thing worth writing down.
What Eddy is
A place where thinking becomes context
Eddy is planned as a workspace for engineers and product managers, on the desktop and on the phone.
- Capture never asks a question. A keyboard shortcut, the terminal, a phone's share sheet or an agent: every thought lands in one inbox.
- Organizing comes after. With your own AI key, Eddy proposes a project, people and dates for each thought, and one keystroke accepts or corrects it.
- Agendas build themselves. What you meant to raise with someone collects in one place for your next conversation with them.
- Agents read the context. Each project keeps a brief of its goals, decisions and open questions that coding agents can read and add to.
How it connects
Built on the same foundations
Notes in Eddy are planned as Markset documents: plain text that agents write and people read, wherever the files go. A decision confirmed in Eddy can become an Intentset record, and an action item ready for the team can become a Streamlane task. Like the other four, Eddy is planned to stand on its own.
Next steps
Help shape Eddy
Eddy is in planning. If you would like to help decide what it becomes, tell us who you are and how you keep track of your thinking today.
Or write to hello@coralreefventures.com.