The protocol comes first so every later layer rests on stable semantics. Roadmap

From specification draft to SDKs, CLI, reference services, and federation.

The roadmap reflects the sequence already outlined in the repository: first the protocol, then interfaces, then reference implementation layers, then ecosystem growth.

Open docs Explore industries

What this page covers

Stabilize the core before broadening the surface area.

Make interfaces consistent across languages and tools.

Keep the protocol vendor-neutral even as commercial implementations emerge.

Treat federation and portability as long-term goals, not marketing slogans.

Highlights

Protocol-native entry points for this surface.

Phase 1

Protocol specification, object model, event model, lifecycle, and reference docs.

See spec

Phase 2

Java, TypeScript, Python, CLI, and MCP.

Browse SDKs

Phase 3 and beyond

Reference implementation, cloud, ecosystem services, marketplaces, and federation.

See cloud

Phase 1  -> Protocol draft and documentation
Phase 2  -> SDKs, CLI, MCP
Phase 3  -> Reference APIs and services
Phase 4+ -> Cloud, marketplaces, federation

Working principles

Keep the protocol stable while implementations evolve.

Stabilize the core before broadening the surface area.

Make interfaces consistent across languages and tools.

Keep the protocol vendor-neutral even as commercial implementations emerge.

Treat federation and portability as long-term goals, not marketing slogans.

Governance

Roadmap choices should remain visible and open to informed discussion.

Join community

Vision

The roadmap only matters if it serves the long-term protocol ambition.

Read vision

Next step

A roadmap for infrastructure, not just features.

Poiva should move deliberately: stabilize semantics, then multiply implementations and domain profiles around that stable base.