Understand the problem
Poiva exists because every platform keeps reinventing work execution differently.
Read the vision
This page helps new builders approach the draft efficiently.
Getting started
A practical path into the protocol for architects, developers, and operators.
Poiva is easiest to understand when you start with the problem it solves, then map the lifecycle, then look at interfaces like SDKs, CLI, and MCP.
What this page covers
Begin with the manifesto and introduction.
Decide which concepts are core and which are extensions.
Model participants by capability rather than role.
Design verification before claiming completion.
Highlights
Protocol-native entry points for this surface.
Map the lifecycle
Follow a mission from intent to evidence, approval, and settlement.
Study lifecycleChoose an interface
SDKs, CLI, and MCP expose the protocol in different operating environments.
Browse interfaces
Suggested onboarding path
bash
1. Read /about and /protocol
2. Open /docs/specification
3. Review /sdk and /cli
4. Explore /mcp and /cloud
5. Map your domain using /industries
Working principles
Keep the protocol stable while implementations evolve.
Begin with the manifesto and introduction.
Decide which concepts are core and which are extensions.
Model participants by capability rather than role.
Design verification before claiming completion.
Related pages
Continue through the public protocol surface.
Industry profiles
See how the same execution model adapts across domains.
Explore industriesReference implementation
Understand where Poiva Cloud fits relative to the protocol.
See cloud
Next step
From reading to implementation.
Once the lifecycle feels clear, use the SDK and CLI pages to imagine how your own systems would expose missions, evidence, and verification.