§ Publications/RI-GLOSS-01
RI-GLOSS-01 · RI Series

Responsibility Infrastructure Glossary

Provides defined terms used across the Responsibility Infrastructure publication set.

Published (Current Version)
Version 1.0 · Issued 2026-05-14
§ Status
Published (Current Version)The current issued version within the Responsibility Infrastructure publication set.
§ Related Files
  • RI-GLOSS-01-v1.0.htmlHTML ·
§ Related Publications
§ Abstract

This publication provides defined terms used within the Responsibility Infrastructure category, including Responsibility Infrastructure, Accountability Infrastructure, Responsibility Chain, Responsibility Record, Responsibility Receipt, Structural Gap, Evidence, Verification, and Registry.

§ Publication

1. Purpose

This publication defines the principal terms used across the Responsibility Infrastructure publication set.

The glossary supports consistent interpretation of foundational publications, operational standards, governance instruments, registry frameworks, and Responsibility Records.

2. Scope

The definitions in this publication apply unless a later or more specialised Responsibility Infrastructure instrument expressly provides a narrower definition for a specific context.

Definitions describe category-level concepts. They do not prescribe a particular product, software platform, organisation, or implementation method.

3. Defined Terms

3.1 Accountability Infrastructure

The systems, processes, institutions, and authorities through which conduct, performance, compliance, fault, consequence, or remedy may be judged.

Accountability Infrastructure functions as a system of judgment. It is distinct from Responsibility Infrastructure, which functions as a system of record.

3.2 Acknowledgement

A recorded confirmation that an assigned responsibility has been received or brought to the attention of the relevant actor, role, system, or authority.

Acknowledgement does not by itself establish acceptance, agreement, completion, or discharge.

3.3 Action

An act, intervention, decision, response, omission, or operational step connected to a responsibility.

An action should remain attributable, time-sequenced, and connected to the relevant Responsibility Record.

3.4 Assignment

The formal placement of a defined responsibility upon an identifiable actor, role, system, organisation, or authority.

Assignment should identify the responsibility, recipient, scope, authority, timing, and applicable conditions.

3.5 Authority

The recognised permission, role, mandate, jurisdiction, or power through which an actor or system may create, assign, vary, verify, recognise, transfer, or close a responsibility.

3.6 Capture

The act of recording responsibility as an identifiable object capable of attribution, state tracking, evidence linkage, verification, and reconstruction.

3.7 Claim

An assertion about a responsibility, action, state, event, evidence item, verification result, or outcome.

A claim is not treated as verified solely because it has been recorded or declared.

3.8 Conformance

The condition in which an implementation satisfies the applicable requirements of a Responsibility Infrastructure standard or specification.

Conformance does not by itself establish Recognition, Registry standing, certification, or institutional endorsement.

3.9 Evidence

Information, records, artefacts, observations, documents, data, or other materials supporting a responsibility-related claim.

Evidence becomes meaningful when its origin, relevance, timing, integrity, and connection to the responsibility lifecycle can be established.

3.10 Outcome

The recorded result or current conclusion of a responsibility lifecycle.

An outcome may include completion, discharge, transfer, refusal, suspension, escalation, unresolved status, closure, or another recognised state.

3.11 Provable Responsibility

Responsibility that can be identified, attributed, time-sequenced, evidenced, verified, and reconstructed from preserved records.

3.12 Recognition

A formal determination, made through an authorised and appropriately independent process, that a defined claim, outcome, implementation, or record satisfies specified criteria.

Recognition is distinct from execution, evidence submission, verification, and Registry publication.

3.13 Registry

An authoritative record through which recognised outputs, standing, status, amendments, suspensions, revocations, supersessions, or withdrawals may be published and retrieved.

A Registry records authoritative standing. It does not create the underlying evidence or replace the independent process through which a determination was reached.

3.14 Responsibility

A defined obligation, duty, role, expectation, commitment, or required outcome attributable to an identifiable actor, role, system, organisation, or authority.

3.15 Responsibility Boundary

The defined point at which responsibility begins, ends, transfers, escalates, becomes constrained, or is discharged.

3.16 Responsibility Chain

The canonical operational lifecycle through which responsibility is processed: Capture, Assign, Acknowledge, Response State, Act, Evidence, Verification, and Receipt.

The Responsibility Chain preserves continuity between the creation of responsibility and its recorded outcome.

3.17 Responsibility Evidence

Evidence connected to a specific responsibility, lifecycle event, actor, action, state, claim, or outcome.

3.18 Responsibility Infrastructure

The institutional category comprising the systems, structures, controls, governance arrangements, evidence mechanisms, operational processes, records, and supporting environments through which responsibility may be identified, attributed, exercised, evidenced, verified, transferred, and reconstructed.

Responsibility Infrastructure functions as a system of record.

3.19 Responsibility Receipt

A recognised record confirming that a responsibility lifecycle, state transition, completion, discharge, transfer, closure, or other defined outcome has been recorded.

A Responsibility Receipt does not erase the underlying Responsibility Record. It provides a retrievable statement of recognised status at a specific point in time.

3.20 Responsibility Record

A cohesive record of custody documenting the existence, identity, condition, evidence, verification, transfer, and outcome of a responsibility lifecycle.

A valid Responsibility Record preserves the structural relationship between Identity, State, Proof, and Outcome.

3.21 Responsibility State

The recorded condition of responsibility at a specific point in its lifecycle.

States may include assigned, acknowledged, accepted, refused, deferred, contested, active, escalated, transferred, verified, completed, discharged, closed, or unresolved.

3.22 Responsibility Traceability

The ability to follow responsibility continuously across actors, states, actions, evidence, transfers, verification events, and outcomes.

3.23 Responsibility Transfer

The controlled movement of responsibility from one actor, role, system, organisation, or authority to another.

A transfer should preserve the identity, scope, timing, authority, state, and continuity of the responsibility.

3.24 Response State

The recorded response to an assigned responsibility.

A Response State may include accepted, refused, deferred, contested, partially accepted, acknowledged without acceptance, or another explicitly defined response.

3.25 Structural Gap

A missing, broken, unclear, or unverifiable connection within a responsibility lifecycle that prevents responsibility from being reliably attributed, tracked, evidenced, verified, transferred, or reconstructed.

3.26 Verification

The independent or appropriately separated examination of a responsibility-related claim, record, evidence item, state, action, or outcome.

Verification may confirm, reject, qualify, suspend, or leave indeterminate the claim being examined.

4. Interpretation

Terms within the Responsibility Infrastructure publication set should be interpreted according to their defined function rather than according to ordinary software, workflow, compliance, or productivity terminology.

Recording an activity does not necessarily establish responsibility. Submitting evidence does not necessarily establish verification. Verification does not necessarily establish Recognition. Recognition does not necessarily establish Registry publication.

5. Relationship to Other Publications

This glossary should be read alongside:

  • RI-001 — Definition of the Responsibility Infrastructure Category.
  • RI-002 — Principles of Provable Responsibility.
  • RI-003 — Core Elements of Responsibility Infrastructure.
  • RI-004 — The Responsibility Record Specification.
  • RI-005 — Characteristics of Responsibility Infrastructure.
  • RI-STD-01 — The Responsibility Chain.
  • RI-STD-02 — Responsibility Evidence Requirements.
  • RI-STD-03 — Responsibility Verification Requirements.

6. Keywords

Responsibility Infrastructure, Accountability Infrastructure, Provable Responsibility, Responsibility Chain, Responsibility Record, Responsibility Receipt, Evidence, Verification, Recognition, Registry, Structural Gap, Responsibility State, Responsibility Transfer, Responsibility Traceability

§ Document Metadata
§ Lifecycle History
  1. 2026-05-14
    Foundational Publication · Version 1.0 first issued
§ Normative References