One foundation. Independent implementations.
Responsibility Infrastructure defines common requirements and interoperable exchange. Products, platforms and services remain free to implement those requirements within their own sectors and operating models.
The Standard sits below the product layer.
The Responsibility Infrastructure Standard defines the requirements. The Responsibility Infrastructure Protocol defines interoperable exchange. Implementations apply those requirements inside products, platforms, services and sector-specific operating models.
Healthcare, financial services, public services, logistics, AI systems and other domains can build different application layers while preserving the same responsibility meaning at the boundary.
Conformance is about requirements, not technology choices.
An implementation may use its own architecture and operating model provided the applicable requirements are satisfied and the required responsibility meaning survives the boundary.
Responsibility Infrastructure does not require:
- A particular API architecture
- A mandatory data format
- A particular cryptographic system
- Blockchain or distributed ledgers
- A particular database or storage technology
- A particular user interface or workflow engine
- A particular vendor or commercial provider
RI can sit around existing operational systems.
ERP, CRM, clinical, logistics, incident, case-management and custom systems can remain in place. RI focuses on preserving responsibility meaning when consequential work moves between people, systems or organisations.
A claim of conformance must be testable.
An implementation claiming conformance must identify the applicable Standard version, role and scope and satisfy the corresponding normative requirements.
Sector-specific features may extend the implementation. They must not silently redefine the common responsibility meaning required for interoperability.