Responsibility that survives independent boundaries.
Responsibility Infrastructure provides the broader architecture through which responsibility can be represented, evidenced, verified, recognised, resolved and relied upon across organisational and system boundaries.
The common boundary is public. Implementations remain choices.
The proposed Responsibility Interoperability Standard and Responsibility Interoperability Protocol define the minimum common semantics and exchange behaviour needed for independent systems to preserve responsibility meaning without adopting a common vendor stack.
Where expressly released, supporting schemas, reference code, validators, fixtures and conformance tests may form part of that interoperability surface. Vendors and open-source implementers can build different technology underneath the same public boundary.
Public interoperability does not place the broader Responsibility Infrastructure Standard or Protocol, implementation-specific architecture or non-public implementation material into the public corpus.
The Operational Responsibility Gap
Organisations may have governance, workflows, monitoring and audit trails while still being unable to reconstruct who held responsibility for a specific operational event, under what authority, with what evidence, and what another organisation may rely upon.
RI addresses that cross-boundary responsibility problem without requiring independent organisations to become one platform.
Read the Operational Responsibility Gap definition →Different sectors use different words. The boundary problem is the same.
Responsibility Infrastructure does not require a sector to abandon its established language. A hospital may describe a clinical handover, a bank a Statement of Responsibilities or operational-resilience action, a construction project a dutyholder handover, and an industrial operator a shift handover or permit to work.
These are sector expressions of a common question: when responsibility crosses a boundary, can an independent party establish who held it, under what authority, what response occurred, what evidence supports it and what standing applies?
The examples below are translation aids only. They do not replace sector regulation, professional duties, statutory authority or sector-specific standards.
- Healthcare & care
- clinical handover · transfer of care · discharge · referral · follow-up · safeguarding · escalation
- Finance & insurance
- Statements of Responsibilities · Responsibilities Maps · operational resilience · impact tolerances · remediation ownership
- Construction & building safety
- dutyholders · principal designer · principal contractor · Accountable Person · golden thread · safety case
- Cyber & technology
- incident manager · CSIRT · decision log · action tracking · escalation · service ownership
- Energy & industrial operations
- shift handover · permit to work · operations-maintenance transfer · safe state · isolation
- Transport
- handover protocol · responsible person · safety-critical communication · defect reporting · service continuity
- Defence & mission-critical operations
- command authority · tasking · chain of command · mission assurance · safety case · configuration control · operational handover
- Aviation & maritime
- Accountable Manager · Safety Management System · Designated Person Ashore · occurrence reporting · ship-shore support
- Education & safeguarding
- Designated Safeguarding Lead · child protection file · secure transfer · confirmation of receipt · multi-agency working
- Public sector & commercial
- contract owner · Contract Management Plan · supplier governance · sourcing-to-contract-management handover
- Emergency services
- gold/silver/bronze command · strategic/tactical/operational command · decision log · command handover
- Life sciences & food
- GxP data integrity · CAPA · deviation · change control · HACCP · corrective action · traceability
- AI & automated decisions
- human oversight · assigned responsibility · explainability · contestability · AI assurance
One responsibility interface. Different authorities.
The interoperability layer allows independent institutions to share responsibility meaning while retaining their own statutory, contractual, professional and operational decision rights.
- Regulators & public authorities
- Reference common responsibility requirements without prescribing a supplier, platform or internal operating model.
- Procurement & assurance
- Specify role, scope, version and testable evidence for responsibility and interoperability claims.
- Insurers & relying parties
- Use resolved responsibility evidence or standing as an input while retaining independent decision authority.
- Vendors & open-source implementers
- Implement the expressly licensed public interoperability layer using different technology and test claims against its published requirements.
- Sector systems
- Apply the common interoperability semantics in healthcare, finance, industry, public services or AI without redefining the cross-boundary meaning.
Public interoperability. Controlled implementation detail.
The public corpus includes the definitions, governance, standards material, research, evidence and implementation artefacts required for institutional scrutiny and independent implementation of the applicable interoperability boundary.
Implementation-specific material that is not required for interoperability may remain outside the public corpus or be supplied for a defined institutional or implementation purpose.
Claims stay bounded to the evidence.
Published RI evidence records preserve source material, outcomes and limitations. Interoperability testing does not automatically establish conformance. Conformance does not automatically establish Recognition. Recognition does not replace the authority of a regulator, insurer, purchaser, court or other relying institution.
Change public requirements through governance, not implementation power.
Standard-setting, implementation, evaluation, Recognition, Registry publication, Resolution and Reliance are distinct functions. Market share or technical replication does not silently rewrite the normative corpus.
Published change control and participation processes provide the route for challenge, extension and revision of public interoperability requirements.
Governance and participation →Keep your system. Share responsibility meaning.
Responsibility Infrastructure · Interoperability · Evidence · Institutional use