Mission
The desired business outcome, including objectives, priority, deliverables, and settlement policy.
Foundation-layer execution standard
Protocol scope
The common language for work execution.
Poiva defines the lifecycle, core concepts, verification model, and compatibility rules needed for independent systems to coordinate work through a shared protocol.
It is positioned as the world's first computer protocol for distributed fulfilment from human resources and other execution participants across multiple domains, without vendor lock-in.
In scope
What Poiva specifies
- Core domain concepts such as mission, activity, participant, and evidence
- Lifecycle semantics from planning through settlement
- Verification rules, event semantics, and immutable history
- Extension mechanisms, versioning, and compatibility expectations
Out of scope
What remains implementation-specific
- User interfaces, dashboards, and product workflows
- Database schemas, programming languages, and deployment architecture
- Identity providers, payment processors, and billing integrations
- Marketplace behavior, matching algorithms, and workflow engine internals
Core concepts
A deliberately small model with broad applicability.
Every compliant implementation preserves the semantics of these objects even when it adds domain-specific behavior on top.
Activity
A unit of execution that may run sequentially, in parallel, or recursively within a mission.
Participant
Any execution entity: human, organization, AI agent, robot, or external system.
Capability
Reusable descriptions of what a participant can do, used for provisioning instead of rigid roles.
Knowledge
Immutable context such as documents, repositories, diagrams, regulations, media, or URLs.
Deliverable and evidence
Outputs plus the proof required to verify them across platforms and domains.
Design principles
Stable rules that guide every extension and implementation.
Outcome over activity
Evidence over trust
Capability over role
Protocol before platform
Vendor neutrality
Human and AI parity
Event-driven architecture
Extensible core
Backwards compatibility
Lifecycle and governance
Portable work depends on verifiable stages and conservative evolution.
Mission lifecycle
Draft, knowledge collection, planning, estimation, review, provisioning, execution, deliverables, verification, approval, settlement, completed.
Protocol governance
Changes should arrive through open discussion, Poiva Enhancement Proposals, semantic versioning, and compatibility-preserving design.
Extensions
The core stays boring so implementations can innovate aggressively.
Software development, construction, healthcare, legal services, logistics, education, and future domains can add industry-specific concepts without changing the meaning of the core protocol.
Software: repositories, pull requests, build pipelines
Construction: inspections, safety reports, building permits
Healthcare: clinical resources, diagnoses, regulatory validation
Logistics: shipments, warehouses, tracking events
Transport choices: REST, GraphQL, gRPC, events, queues, WebSockets
Continue reading
Follow the draft from protocol scope into interfaces and industries.
The protocol description is only one layer. The docs, SDK, CLI, cloud, and industry pages show how the same semantics extend into real execution environments.