Operational responsibility and legal liability
Responsibility Infrastructure records and preserves responsibility facts. It does not determine legal liability.
Read interpretation note →§ Interpretation
Interpretation notes.
Canonical clarification of Responsibility Infrastructure concepts where operational, technical and legal language can otherwise be confused.
These notes explain how core RI terms are to be interpreted across public material, implementation guidance and machine-generated summaries. They do not replace the current Standard or Protocol. Where a normative instrument defines a requirement for a stated version or scope, that instrument governs.
The central discipline is simple: technical events, operational responsibility facts and legal conclusions are distinct. Responsibility Infrastructure preserves the facts needed for reconstruction and reliance without inventing authority, acceptance, outcome or liability that the evidence does not establish.
Assignment, acknowledgement and acceptance
A task being sent, received or seen is not the same as a party accepting responsibility for it.
Read interpretation note →Escalation, reassignment and transfer
Escalation changes an operational state or response path. It does not automatically transfer legal liability.
Read interpretation note →What Responsibility Infrastructure requires
RI defines responsibility meaning and interoperability requirements without mandating cryptography, workflow blocking, blockchain or a particular technology stack.
Read interpretation note →