One step makes the next possible.
Start with useful work. Learn together. Build the capacity for more.
Make everyday work easier.
Bring people, tools and decisions into one shared place.
Connect what we learn.
Carry knowledge and experience from one challenge into the next.
Shape what comes next.
Explore the places and communities we could create together.
These are horizons for the work, not release dates or promises.
Read the full project overview
An honest map of where the work stands. Concept means the direction is written and testable. In build means it exists and is being used to build the rest of the system. Running means it carries real work today. This page changes as the work does, and the strategy explains why the order looks like this.
One thing to read the tables with: the ecosystem is currently its own first customer. What is marked running is running because the work of building Unifyhub depends on it, not because it is ready to be handed to a community. That distinction is the whole difference between a status page and a brochure.
Product status
| Product | Role | Status |
| Alpha | Infrastructure substrate | Running |
| Horizon | Shared foresight | Running |
| Cortex | Governed reactions | In build |
| Scout | Collection and evidence | In build |
| One | Community control plane | In build |
| IAM | Identity and access | In build |
| ANT | Physical automation | Early build |
| Capital | Money and holdings | Early build |
| Echo | Personal digital persona | Concept |
| Praxis | Embodied interaction | Concept |
Capability status
| Plane | Status |
| Infrastructure substrate | Running |
| Delivery and assurance | Running |
| Events and data | Running |
| Interface composition | In build |
| Domain services | In build |
| Agentic operations | In build |
| Knowledge and memory | In build |
| Collection and evidence | In build |
| Models and inference | In build |
| Physical automation | Early build |
Now
The vision, principles, architecture, and strategy are public and versioned, on our own infrastructure.
The substrate runs the whole ecosystem, and the delivery path that changes it is declarative, gated, and reversible.
The shared contracts (identity, policy, audit, events, migration) are being designed in the open, protocol before product.
The system is being made legible to itself, so that scale does not become opacity.
Next
The first proof: one narrow, complete product experience that makes the values visible in ordinary use, aimed at one painful problem. The leading candidates: shared membership and roles across tools, community memory for decisions, and trusted delegation for automation.
The identity and policy foundation (IAM) serving that first experience through the public contracts, consolidated into one realm and one policy plane.
Delegated automation held to the full delegation standard rather than to an internal convention.
Later
The remaining products maturing against the same contracts: the control plane in the hands of communities that did not build it, embodied interaction, protocol governance under user context.
Conformance suites and compatibility marks, so independent implementations can prove compatibility without asking us.
Federation, once the policy, abuse, and audit work that makes it safe to govern exists.
The long horizon, which is direction rather than schedule and is stated so it can be argued with.
Deliberately unscheduled
Growth mechanics, marketplaces, and convenience features stay off this roadmap until the core keeps its promises in daily use. The risks page lists the drift signals we watch for; if you catch one here, say so.
All products · All capabilities · The use cases · The strategy