One standard. Independent implementations.
Responsibility Infrastructure defines common requirements and interoperable exchange. Products, platforms, open-source projects and sector systems remain free to implement those requirements within their own operating models.
Anyone may reference or independently implement the published Responsibility Infrastructure specifications. Such use does not itself establish Verification, Recognition, certification, accreditation, endorsement, Registry standing, or official participation. General external participation, evaluation, Recognition, and Registry programmes are not presently open unless a specific published programme states otherwise.
Public implementation materials define only the minimum external requirements necessary for interoperability and reliance. Proprietary operating methods, implementation logic, internal evaluation methods, authority-resolution processes, commercial controls, programme administration systems, Registry security controls, and other methods that reproduce La Touche’s commercial advantage are not published.
An organisation may truthfully state that an identified implementation references a named Responsibility Infrastructure publication and version. That factual statement is not an official designation and does not create Verification, Recognition, certification, endorsement, Registry standing, or authority for external reliance.
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.
The existence of an implementation is therefore not the source of RI authority. A product may reproduce every technical function and still need to establish any claim it makes about RI conformance, Recognition, standing or suitability for external reliance.
Public specification. Technology-neutral implementation.
No particular API, data format, ledger, cryptographic system, database or software is required to implement Responsibility Infrastructure.
Implementers publish the minimum interface needed for interoperability and reliance. They do not publish internal event schemas beyond what interoperability requires.
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
Commodity technical capability does not create institutional standing.
RI does not treat the ease, cost or openness of an implementation as evidence that its responsibility claims should be accepted by another organisation. Institutional reliance requires the applicable claim, evidence, role, scope and version to be examined on their merits.
- Publishing source code or an SDK does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Calling a product an open protocol does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Operating a registry service does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Providing verification or scoring does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Implementing recognition or standing workflows does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Providing telemetry, alerts or real-time enforcement does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
- Passing a vendor's own test suite does not by itself establish RI conformance, Recognition, Registry standing or authority for external reliance.
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.