Outcome over activity
Poiva measures finished outcomes and accepted deliverables instead of hours, meetings, or status updates.
World-first distributed fulfilment protocol
Open protocol for work execution
The open protocol for distributed fulfilment of work.
Poiva is the world's first computer protocol designed to coordinate distributed fulfilment from human resources, AI agents, organizations, and machines across software, healthcare, logistics, construction, legal work, and more.
It standardizes how intentions become missions, how capabilities are matched, how evidence is collected, and how outcomes are verified and settled without locking execution into a single platform.
Protocol graph
Intent Outcome signal
Example intent
Discharge a patient safely before 17:00
A sponsor expresses the outcome, urgency, constraints, and acceptable result without prescribing every step.
TriggerClinician marks patient ready
InputsOutcome, deadline, constraints
Mission Scoped work
Example mission
Review and redline a supplier agreement before signature
The intent becomes a protocol object with sponsor, deliverables, review path, pricing rules, and completion semantics.
DeliverableApproved contract markup
ConstraintsPolicy, jurisdiction, deadline
Execution Fulfilment run
Example execution
Ship an invoice export, route a courier, or inspect a live site
Humans, organizations, AI agents, and automations contribute activities while the protocol keeps shared state and traceability.
ActorsEngineer, courier, inspector, AI
OutputsDeliverables plus event history
Evidence Portable proof
Example evidence
Pull requests, signatures, GPS trails, photos, lab results
Proof stays attached to the work so completion can travel across systems instead of living inside one vendor workflow.
FormatsLinks, files, events, attestations
GoalMake verification reusable
Verification Outcome accepted
Example verification
Rules confirm “merged + tests green”, “drop complete”, or “clinical sign-off captured”
Policies evaluate evidence and return accepted, rejected, or revision-needed with a durable completion record.
DecisionAccepted / rejected / revise
Next stepSettlement or rework loop
48+
domain profiles
5
participant types
1
shared lifecycle
Built for protocol-native execution engines
Portable across vendors and internal systems
Compatible with human and AI fulfilment
Evidence-first by default
Designed for cross-domain execution
Why Poiva exists
Every platform keeps reinventing work. Poiva standardizes distributed fulfilment.
Jira, GitHub, Slack, ERP systems, legal platforms, logistics tools, and healthcare workflows all model similar concepts in incompatible ways. Poiva defines the common language once so independent systems can interoperate without lock-in.
Evidence over trust
Pull requests, inspections, signatures, tracking data, photos, and evaluations make verification portable.
Capabilities over titles
Participants are selected for what they can do, whether they are humans, teams, AI systems, or machines.
How it works
A shared lifecycle from intent to verified completion.
The exact tools change. The execution semantics do not. Poiva gives distributed teams and systems one portable path for fulfillment across domains.
Intent
A desired outcome enters the protocol.
Mission
Scope, objectives, requirements, and sponsor are defined.
Planning
Activities, risks, cost, and capability needs are modeled.
Provisioning
The right human resources and systems are selected.
Execution
Participants produce deliverables and attach evidence.
Verification
Policies evaluate proof and determine completion.
Settlement
Commercial or contractual completion is recorded.
Workflow overlays
Popular human workflows, mapped directly onto the protocol.
These examples show how familiar real-world workflows overlay cleanly on the same Poiva stages: the protocol stays stable while each domain keeps its own language and operational detail.
Software engineering
Popular software delivery workflow
Healthcare
Popular clinical care workflow
Legal
Popular legal services workflow
System engineering
Popular systems change workflow
Architecture
Popular architectural design workflow
Inspection
Popular inspection workflow
Package delivery
Popular parcel delivery workflow
Shared drivers and couriers
Popular dispatch and courier workflow
RFP and procurement
Popular procurement workflow
Car manufacturing
Popular automotive production workflow
Factory operations
Popular factory operations workflow
Gas operations
Popular gas field workflow
Mining
Popular mining operations workflow
Navigation and vessel operations
Popular navigation workflow
Construction
Popular construction delivery workflow
Manufacturing
Popular manufacturing workflow
Logistics
Popular logistics workflow
Education
Popular education workflow
Government
Popular public-service workflow
Core principles
Infrastructure-grade rules for interoperable execution.
Poiva is intentionally opinionated about the lifecycle and deliberately neutral about implementation details.
Outcome over activity
Evidence over trust
Capability over role
Protocol before platform
Vendor neutrality
Human and AI parity
Extensible core
Event-driven history
Backwards compatibility
Ecosystem
One protocol, many implementations.
Poiva sits beneath products rather than replacing them. Internal workforce platforms, marketplaces, orchestration engines, and AI tooling can all speak the same protocol while remaining implementation-independent.
Applications
CraftStack, enterprise systems, government services, logistics platforms, healthcare products, AI agents
Execution engines
Poiva Cloud, internal orchestration, verification services, capability matching, settlement workflows
SDKs and interfaces
Java, TypeScript, Python, Go, CLI, MCP, REST, GraphQL, gRPC, events
Protocol core
Mission, activity, participant, capability, knowledge, deliverable, evidence, verification, settlement
Supported participants
Built for mixed fulfillment across humans, AI, and systems.
Humans
Specialists, reviewers, operators, inspectors, and domain experts.
AI agents
Estimators, assistants, analyzers, and execution co-pilots.
Organizations
Internal teams, external providers, firms, agencies, and partners.
Robots
Field devices, autonomous tools, and hardware systems contributing to missions.
Automation
Event processors, scripts, integrations, workflows, and background services.
Industry profiles
One protocol, many domains.
The same execution semantics can coordinate distributed fulfilment in software, logistics, healthcare, legal work, education, public services, and beyond.
Software engineering
Coordinate distributed product delivery with verifiable outputs.
View profileHealthcare
Coordinate clinical workflows with evidence-based verification.
View profileLegal
Coordinate contract work and compliance review with portable evidence.
View profileSystem engineering
Coordinate multi-team infrastructure and systems change with clear stage ownership.
View profileArchitecture
Coordinate architectural design from brief to approved package.
View profileInspection
Coordinate inspections, reports, and remediation decisions across field teams.
View profilePackage delivery
Coordinate parcel movement from shipper request to proof of delivery.
View profileShared drivers and couriers
Coordinate on-demand human fulfillment for rides, errands, and courier work.
View profileRFP and procurement
Coordinate bid responses, review, and vendor selection through a structured lifecycle.
View profileCar manufacturing
Coordinate design changes, production readiness, and line execution for vehicle programs.
View profileFactory operations
Coordinate ongoing production, maintenance, and workforce planning in a portable workflow model.
View profileGas operations
Coordinate field operations, maintenance, and safety workflows around critical infrastructure.
View profileMining
Coordinate extraction, safety, maintenance, and reporting across remote operations.
View profileNavigation and vessel operations
Coordinate route execution, crew operations, and compliance for moving assets.
View profileConstruction
Coordinate building work, specialist trades, and approvals across field teams.
View profileManufacturing
Coordinate assembly, quality assurance, and maintenance as structured missions.
View profileLogistics
Coordinate deliveries and handoffs through verifiable execution states.
View profileEducation
Coordinate course design, assessment, and research collaboration.
View profileGovernment
Coordinate public-service execution with auditability and interoperability.
View profile
Developer experience
Interfaces for builders, operators, and AI systems.
The protocol can be consumed through SDKs, CLI workflows, MCP, APIs, and event streams. Each interface keeps the lifecycle and evidence model intact.
CLI
SDK
MCP
poiva mission create
poiva capability search
poiva evidence attach
poiva verify
const mission = await poiva.missions.create(...)
verification = client.verifications.evaluate(...)
assistant.submitDeliverable(...)
Open source posture
Poiva is designed to stay open, vendor-neutral, and extensible across many implementations.
Public roadmap
The work starts with the specification, then expands into SDKs, CLI, MCP, cloud references, and federation.
Community-first governance
Protocol evolution belongs in public discussion so compatibility and neutrality stay intact over time.
Final call
Help build the future of work execution.
If work should be portable, verifiable, and open, Poiva is the protocol surface designed to make that future real.