Open LifeProtocol for Actors
Like OpenAPI for processes. OLP defines a shared contract so any system can exchange, execute, audit, and automate critical life and business workflows.
Life is fragmented
across systems.
The same person exists across banking, healthcare, education, legal, family, and work systems with no shared model. Applications model fragments of life, but life spans all of them.
A shared language
for critical processes.
Open Life Protocol standardizes the core object model for life and business workflows, so institutions and applications can execute the same contract across systems.
Actor
Event
Case
Workflow
Task
Document
Communication
Decision
Evidence
Outcome
Asset
Payment
Domain first.
Software second.
Model Reality
Model life as it is lived, not how a specific product stores records.
Human Centric
Keep people at the center across relationships, events, and decisions.
Open and Portable
Anyone can build on the protocol and data can move across systems.
Privacy By Design
Individual control and consent are foundational protocol concerns.
Specification to execution,
without losing interoperability.
A canonical ledger
for human domains.
Build from the
contract first.
OLP treats the specification as the source of truth: define the contract once, then generate tooling, validate conformance, and publish reusable workflows.
entity Person {
id: OLP.Identifier
relationships: Relationship[]
events: Event[]
goals: Goal[]
}Public by default.
Durable by design.
Open Life Protocol is stewarded as a public standard with transparent specifications, examples, and community collaboration.
Open Life Foundation
stewardship model
Open Life Protocol is not owned by a single application. Governance protects neutrality, continuity, and trust in the standard.
Stewardship
Standards maintenance
Schema evolution
Interoperability testing
Public RFC process
Cross-domain coordination
Many applications.
One shared protocol.
OLP enables an ecosystem of interoperable domain systems built on one process contract.