Research & evidence
Researchers, academics, evaluation specialists and methodologists examining operational responsibility, interoperability, governance, organisational behaviour and evidence.
§ Participation
Participation and working groups.
Responsibility Infrastructure is developed through evidence, implementation experience, technical criticism and multidisciplinary challenge. Participation does not require adoption of a particular commercial product or implementation.
Who can contribute
Organisations, implementers, researchers, practitioners, policymakers, public administrators, assurance specialists, regulators, standards practitioners and other affected parties may contribute evidence or proposals relevant to a published Responsibility Infrastructure requirement, protocol rule, conformance condition or governance question.
Expertise needed
Responsibility Infrastructure crosses organisational, technical and institutional boundaries. Development therefore requires evidence and challenge from multiple disciplines rather than a single profession, sector or implementation community.
Systems & interoperability
Software engineers, architects, product teams and system owners testing whether Responsibility Infrastructure can be implemented and interpreted independently across technical boundaries.
Operational practice
Practitioners and operational leaders with direct experience of consequential handoffs, decisions, escalation, transfer, evidence and outcome across organisational boundaries.
Assurance & risk
Assurance, audit, safety, risk, legal and compliance specialists able to test claim boundaries, evidence requirements and external-reliance assumptions.
Policy & public administration
Policymakers, public administrators and regulatory-policy specialists able to examine how responsibility requirements interact with public policy, institutional duties and cross-organisational governance.
Standards & governance
Standards practitioners, governance specialists, regulators and institutional reviewers contributing experience of consensus, conformance, recognition, standing and controlled change.
Public interest
Affected parties, consumer and public-interest representatives able to challenge whether proposed requirements remain understandable, proportionate and capable of supporting legitimate external reliance.
Cross-sector by design
Responsibility Infrastructure is intended as a common foundation rather than a sector-specific operating model. Sector expertise is used to test whether common responsibility requirements remain valid under different operational, regulatory and technical conditions. Sector participation does not create a separate version of the core Standard or Protocol unless a formally published profile is established.
Application environments
Participation is particularly relevant where responsibility crosses consequential organisational or system boundaries. Current areas of research, implementation or policy interest may include the following environments without limiting the domain-neutral scope of Responsibility Infrastructure.
- Healthcare and care
- Regulated services
- Public administration and government
- AI-assisted and autonomous systems
- Supply chains and multi-party operations
- Safety-critical and high-consequence environments
How change is proposed
A proposal should identify the publication or requirement concerned, the problem observed, the proposed change, the expected interoperability or governance effect, and any evidence from implementation, research, policy analysis or testing that supports the proposal.
How proposals progress
- 01ProposalA change, issue or implementation concern is submitted with a defined scope and supporting rationale.
- 02ReviewThe proposal is assessed against the current Standard, Protocol, published requirements and existing version history.
- 03ConsultationWhere broader input is required, the proposal is exposed for recorded comment, implementation evidence and competing views.
- 04ResolutionMaterial disagreements, alternatives and reasons for the selected treatment are recorded before a normative decision is made.
- 05PublicationAccepted normative changes are incorporated only through a versioned publication with an explicit status and effective scope.
Disagreement
Disagreement is part of standards work. Material competing positions should be preserved in the record rather than collapsed into an unexplained decision. A normative change is made only through the applicable change-control and publication process.
Working groups
A working group is constituted for a defined cross-sector subject and scope. Its charter identifies the question being addressed, participation conditions, decision method, publication output and relationship to the wider Responsibility Infrastructure corpus. Working groups may draw on sector-specific evidence or application panels without making the core infrastructure dependent on a single industry.
No standing working group is currently listed on this page. Working-group records will be published when a group is constituted.
Versions and conformance
Participation does not change the version an implementation conforms to. Conformance is assessed against the identified publication, role, scope and version. Draft or proposed changes do not become normative until formally published in the applicable status.