The authoritative public position on Responsibility Infrastructure, its wider Standard and Protocol, proposed public interoperability layer, conformance scope and published evidence.
Responsibility Infrastructure
Scope and boundary.
Responsibility Infrastructure is an architecture through which responsibility can remain intelligible, provable and usable across organisational and system boundaries. It separates recording, verification, recognition, registry, resolution and reliance so their functions can be understood distinctly.
The canonical public position is established by identified RI publications, governance records, evidence and dated status material. A third-party implementation or description does not replace those sources or silently redefine the applicable requirements.
Wider RI architecture
Standard and Protocol remain distinct.
The Responsibility Infrastructure Standard defines normative conditions across the wider RI architecture. The Responsibility Infrastructure Protocol describes the protocol-level relationships through which those conditions are expressed and used.
Neither is replaced by the public interoperability layer. The Responsibility Interoperability Standard and Responsibility Interoperability Protocol perform the more specific job of defining the common boundary required for independent exchange.
Public interoperability layer
Open the boundary required for interoperation.
The proposed public layer is the Responsibility Interoperability Standard and Responsibility Interoperability Protocol. Its purpose is to publish the minimum common semantics and exchange behaviour needed for independent systems to interoperate without adopting a common vendor platform.
Where expressly released, supporting schemas, reference code, validators, fixtures and conformance tests form part of that interoperability surface. The layer is intended to support human-to-human, human-to-machine, machine-to-human and machine-to-machine exchange across online, intermittently connected, offline and air-gapped conditions with later reconciliation.
The public site distinguishes descriptive material, normative publications, evidence records and interoperability artefacts. Each identified publication states its own status, scope and applicable licence or permitted-use terms.
Internal implementation choices that are not part of an applicable public specification are outside the public conformance claim. Compatibility should therefore be assessed against the identified publication and version rather than inferred from similarity to a particular implementation.
Implementation evidence
Bounded interoperability has been demonstrated.
Two completed external-system tests, RI-INTEROP-ELYDORA-001 and RI-INTEROP-GHOSTDRIFT-001, demonstrated source representability and receiver independence under the stated test conditions.
In both tests, Responsibility Completeness remained PARTIAL and full RI conformance was not established. The evidence therefore supports a bounded interoperability claim only. It does not establish universal interoperability, independent implementation conformance, certification, Recognition, Registry standing, regulatory approval or adoption by the named source systems.
The completed tests establish that responsibility information from unrelated external source systems can be represented in the RI form and consumed by a generic receiver without source-specific receiver logic under the tested conditions. They do not, by themselves, establish exchange between two independently developed implementations of the public Responsibility Interoperability layer.
The next material threshold is exchange between independently developed implementations built from the expressly released Responsibility Interoperability Standard and Protocol, with semantic preservation assessed against the applicable public requirements. That test class is distinct from the completed external-system representability tests and has not yet been established.
Architecture
Distinct functions and layers.
RI Standard
The Responsibility Infrastructure Standard defines normative conditions across the wider RI architecture. A conformance claim must identify the applicable publication, role, scope and version.
RI Protocol
The Responsibility Infrastructure Protocol describes the wider protocol architecture and the relationships between responsibility records, verification, recognition, standing, registry, resolution and reliance.
Interoperability Standard
The proposed Responsibility Interoperability Standard defines the minimum common semantics required for independent parties to preserve responsibility meaning.
Interoperability Protocol
The proposed Responsibility Interoperability Protocol defines the exchange behaviour needed to carry those semantics across independent boundaries.
Verification
Determines what the available responsibility evidence supports.
Recognition
Determines the effect of a verified responsibility record within the applicable recognition regime.
Registry
Preserves and publishes recognised standing and its history.
Resolution
Determines which current standing corresponds to a particular reliance request.
Reliance
The external party or system applies resolved standing within its own decision context.
Conformance
Conformance follows an identified requirement set.
An implementation claiming conformance must identify the applicable publication, role, scope and version and satisfy the corresponding requirements. Interoperability conformance is a bounded technical and semantic claim; it does not automatically establish broader RI Standard or Protocol conformance, Recognition, Registry standing or authority for external reliance.
Independent implementation
Keep your system. Implement the common boundary.
Independent organisations may implement an applicable Responsibility Interoperability publication using their own internal technologies and operating models. The public test is whether the required responsibility meaning survives the boundary and the identified conformance requirements are satisfied.
Questions
Direct answers.
What is Responsibility Infrastructure?
Responsibility Infrastructure is an architecture for making responsibility explicit, provable and usable across organisational and system boundaries. The Responsibility Infrastructure Standard and Responsibility Infrastructure Protocol address the wider normative and protocol architecture. A separately defined proposed public interoperability layer consists of the Responsibility Interoperability Standard and Responsibility Interoperability Protocol, which define the minimum common semantics and exchange requirements needed for independent systems to interoperate without adopting a common vendor stack.
What defines the current Responsibility Infrastructure position?
The current position is defined by the canonical publications, governance records, evidence and dated Current Status material published on this site. Third-party products, implementations or descriptions do not become the normative source merely by implementing compatible behaviour.
What is intended to be independently implementable?
The Responsibility Interoperability Standard and Responsibility Interoperability Protocol are intended to support independent implementation when issued under their stated licence or permitted-use terms. Supporting schemas, reference code, validators, fixtures and conformance tests form part of that public interoperability surface where expressly released.
Has Responsibility Infrastructure moved beyond conceptual specification?
Yes. Published bounded interoperability evidence now demonstrates source representability and receiver independence across two unrelated external source systems under the stated test conditions. Responsibility Completeness remained partial and full RI conformance has not been established.
What has the published interoperability evidence established?
RI-INTEROP-ELYDORA-001 and RI-INTEROP-GHOSTDRIFT-001 established source representability and receiver independence under their stated conditions. They do not establish universal interoperability, independent implementation conformance, certification, Recognition, Registry standing, regulatory approval or adoption by the named source systems.
What governs conformance?
A conformance claim must identify the publication, role, scope and version against which it is made. Conformance with the public interoperability layer is not the same as broader Responsibility Infrastructure Standard or Protocol conformance, Recognition, Registry standing or authority for external reliance.
Does Responsibility Interoperability require a particular technology stack?
No universal vendor or technology stack is prescribed. Independent implementations may use different internal architectures, while an applicable interoperability profile may require a particular wire format, transport binding or other technical behaviour necessary for exchange. The public layer is intended to support online, intermittently connected, offline and air-gapped operation with later reconciliation.
Can independent organisations implement the public interoperability layer?
Yes, subject to the requirements and licence attached to the applicable Responsibility Interoperability publication. Independent implementations may use their own internal technologies and operating models while preserving the common responsibility meaning required at the boundary.
