The documentation set tracks the protocol draft and its design principles. Documentation

Read the working draft like infrastructure, not marketing.

Documentation is organized around universal execution concepts, lifecycle semantics, and long-lived compatibility rules.

What this page covers

Read the introduction and scope first.
Trace the mission lifecycle end to end.
Understand verification before thinking about implementations.
Use extensions for industry-specific concepts.
Highlights

Protocol-native entry points for this surface.

Getting started

A quick path through the concepts, docs, and implementation surfaces.

Start here

Protocol overview

The public-facing overview of why Poiva exists and what it standardizes.

See the overview
Read the draft in order bash
docs/manifesto.md
docs/vision.md
docs/protocol/01-introduction.md
docs/protocol/02-design-principles.md
docs/protocol/03-domain-model.md
Working principles

Keep the protocol stable while implementations evolve.

Read the introduction and scope first.
Trace the mission lifecycle end to end.
Understand verification before thinking about implementations.
Use extensions for industry-specific concepts.
Related pages

Continue through the public protocol surface.

Open governance

Future changes are expected to move through public discussion and Poiva Enhancement Proposals.

Join the community

Public roadmap

Track how the protocol, SDKs, CLI, and cloud references evolve.

View the roadmap
Next step

Need the fastest path through the draft?

Start with the introduction, then design principles, then the domain model. The pages under Docs preserve that progression.