A ZERO CEREMONY PROJECT
Capy
Software that keeps work moving across systems.
Capy is our first project.
It explores how software on different computers can work together reliably without tying the whole system to one implementation.
What it is for
Say what needs to happen. Let the software work out how.
You should not have to choose every tool, manage each handoff, watch for delays, or rebuild a task after an interruption.
Capy should use the context and software already available. It should ask for attention only when your decision changes the result.
What matters
- work survives a lost connection or closed session;
- accepted work is not confused with completed work;
- interruptions recover predictably;
- one provider cannot trap the whole system;
- technical complexity stays behind the interface.
What we know
These findings come from controlled research, not production use.
Independent implementations have coordinated reliably in our early studies. Continuity and recovery did not depend on sharing one internal system.
We publish the conclusion, not private requests, detailed scenarios, or security-sensitive mechanics.
What we do not know yet
We have not built the complete user experience or tested Capy at public scale.
Production security, reliability, adoption, and broad Internet use remain open. None of the possibilities on this site is a roadmap promise.
What Capy is not
Capy is not an AI model, cloud provider, messaging app, blockchain, token, payment network, or replacement for existing infrastructure.
It may connect those systems. It does not need to own them.
Built to be replaced
Capy should be smaller than the products built around it. No single implementation should own the entire experience.
Managed services can make it easier to use, while the underlying design leaves room for better implementations and interfaces.
Next
We now want to find where this foundation can remove real setup and supervision from everyday work.
Success means asking for an outcome and putting down the implementation plan until the software truly needs you.
Read the problem
Read the principles
See what we are doing now