Mission operations
Create, inspect, and advance missions through the same lifecycle the protocol defines.
See lifecycle
Command lines are often the fastest way to operationalize a protocol.
CLI
A protocol-native command line for builders and operators.
The CLI should let teams create missions, inspect lifecycle state, submit evidence, watch events, and verify outcomes without inventing a parallel mental model.
What this page covers
Keep commands aligned to protocol concepts.
Favor inspectability over magic.
Make evidence and verification explicit.
Support long-running, asynchronous work cleanly.
Highlights
Protocol-native entry points for this surface.
Verification workflows
Submit evidence and run verification from the terminal.
Read verificationEvent watching
Observe immutable protocol history as work progresses.
See integrations
Representative commands
bash
poiva mission create
poiva mission list
poiva evidence attach
poiva verify
poiva events watch
Working principles
Keep the protocol stable while implementations evolve.
Keep commands aligned to protocol concepts.
Favor inspectability over magic.
Make evidence and verification explicit.
Support long-running, asynchronous work cleanly.
Related pages
Continue through the public protocol surface.
SDKs
Pair CLI usage with embedded implementations and services.
Browse SDKsCommunity
Follow CLI evolution through public feedback and open governance.
Join community
Next step
For humans operating protocol infrastructure.
Poiva is about distributed fulfilment by human resources, AI agents, and systems. The CLI is the sharp edge for human operators.