Responsibility Infrastructure
Responsibility Infrastructure
Standards for Provable Responsibility
Current Status · November 2026

Current position.

A dated record of RI technical publications, interoperability proposals, research attribution and the boundaries of 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.

Each published source identifies its author, status, scope and evidence basis.

Domain-neutral scope

AI assurance is one application, not the boundary.

AI assurance is one application of Responsibility Infrastructure; Responsibility Infrastructure is not limited to AI. It can apply wherever responsibility crosses organisational, institutional or system boundaries across people, organisations and machines.

The same architecture can be applied where responsibility must remain explicit and provable across human, organisational and machine boundaries in healthcare, finance, transport, public services, industry and other sectors.

Wider RI architecture

Published technical foundations.

The RI Standard and RI Protocol describe the wider architecture and proposed requirements within their declared scope.

Separate working proposals examine the common semantics and exchange behaviour needed for independent implementations.

Public interoperability layer

Open the boundary required for interoperation.

The minimum shared boundary concerns the responsibility information and exchange behaviour independent systems need to preserve meaning across organisations and technologies.

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.

Publication boundary

Use the identified requirement set.

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.

Publication provenance

Technical records and contributor research are distinct.

RI keeps technical records. La Touche publishes its own research.

Architecture

Distinct functions and layers.

RI Standard
The existing RI Standard records technical requirements under its identified publication, version and status.
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
A working proposal describes common responsibility information and its meaning at an independent exchange boundary.
Interoperability Protocol
A related working proposal describes exchange behaviour for independent systems, with its version and status recorded in the publication.
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 suppliers should be able to implement any agreed minimum shared requirements using their own technologies. No unrelated private RI requirement or vendor service should become a mandatory condition without explicit inclusion and suitable rights.

Questions

Direct answers.

What is Responsibility Infrastructure?

Responsibility Infrastructure documents a founder-originated technical architecture for preserving responsibility information across organisational and system boundaries. Its publications record proposed requirements, governance and technical definitions, not an externally approved consensus standard. Any future standards-development process would determine its own scope, publication form, terminology and requirements.

Is Responsibility Infrastructure only for AI?

AI assurance is one application of Responsibility Infrastructure; Responsibility Infrastructure is not limited to AI. It can apply wherever responsibility crosses organisational, institutional or system boundaries across people, organisations and machines.

What defines the current Responsibility Infrastructure position?

RI's current position is established by its published technical documents, recorded evidence and their stated versions and status.

What is intended to be independently implementable?

The proposed shared boundary covers the minimum responsibility information and exchange behaviour needed for independent systems to preserve responsibility meaning. Applicable requirements and implementation rights are identified in each publication.

Has Responsibility Infrastructure moved beyond conceptual specification?

RI has published technical proposals and traceable publication records. La Touche's research exercises are separately attributed to the organisation that conducted them, with their own methods, outcomes and limits.

Where are contributor research and implementation tests published?

Contributors publish research and implementation tests under their own attribution. RI maintains its technical and governance publications separately, with evidence and assessment status recorded at the source.

What governs conformance?

Conformance is assessed against a named publication, role, scope and version. Verification, Recognition, Registry standing and external reliance are separate determinations.

Does Responsibility Interoperability require a particular technology stack?

The working proposal is implementation-neutral. Any required exchange format or binding must be specified publicly and justified by the applicable interoperability requirements.

Can independent organisations implement the public interoperability layer?

Independent suppliers can implement the published common boundary using their own technologies without purchasing a La Touche product. Claims of conformance remain limited to the applicable requirements and evidence.

Updated .