CURRENT WORK
Work
Our first project is Capy. It is early research, and its shape will change as we learn.
Capy
Research and development
Capy asks a practical question: can software own the follow-through without making the user assemble and supervise the system?
We are starting with reliability across computers and the freedom to change implementations later.
What we know
Early technical validation
Separate implementations have coordinated reliably in controlled studies. They also recovered from the interruptions we tested without losing or duplicating accepted work.
We have early evidence that continuity can survive changes in software and devices.
This is a technical result, not a finished product.
Current focus
Current focus
Find out where software can take over setup, follow-through, and recovery without taking control away from the user.
Can you ask once, move on, and hear back only when you are needed?
We are looking at where current tools succeed and where setup, supervision, or handoffs still fall to the user.
Capy only needs to exist where it makes that experience clearly better.
How we work
We start with a familiar task, try the best available tools, and build the smallest thing that answers our next question.
We share the conclusions and their limits. Private requests, scenarios, and implementation records stay private.
Not in scope
There is no public beta, universal agent, token, payment network, or mandatory Capy cloud in development.
We are not replacing messaging, email, Git, HTTP, operating systems, or cloud providers. Future services will need a clear reason to exist.