About Liability Relationship Standard (LRS)
About Liability Relationship Standard (LRS)
What Is the Liability Relationship Standard?
The Liability Relationship Standard (LRS) is the LIGA™ Parent Standard for governing the Subjects and relationships that form the relational structure of a potential Liability matter.
Once a Governed Liability Object and Governed Liability Basis have been established, LRS determines who or what is relevant to the Liability inquiry, what roles those Subjects hold, how they relate to one another, and how those relationships connect to the relevant Object and Basis.
LRS creates the relational structure required before Liability Conditions, Liability-Relevant Connection, Attachment, or Determination can be evaluated.
Canonical Meaning
A Liability Subject is a governed participant whose identity, role, state, conduct, authority, obligation, control, relationship, or other relevant characteristic may become material to a Liability inquiry.
A Liability Relationship is a governed relationship involving Liability-relevant Subjects that may materially affect how potential Liability is subsequently evaluated.
Neither concept establishes Liability.
Liability Subject ≠ Liable Subject.
Liability Relationship ≠ Liability.
Why Is the Standard Necessary?
Complex Liability matters rarely consist of one event, one actor, and one simple relationship.
A single matter may involve:
multiple organizations, multiple individuals, owners, operators, providers, manufacturers, contractors, agents, insurers, AI systems, autonomous systems, and several overlapping contractual, operational, ownership, control, authority, or other relationships.
Without explicit relationship governance, systems may incorrectly move from:
Occurrence → Actor → Liability LRS introduces the required relational layer:
Governed Liability Object → Governed Liability Basis → Subjects → Relationships → Conditions → Connection → Determination This prevents operational involvement or relational proximity from being mistaken for Liability.
What Does LRS Govern?
LRS governs the methodological structure of Liability-relevant Subjects and Relationships, including:
Subject Identity, Subject Roles, Relationship Identity, Relationship Type, Relationship Direction, Relationship Scope, Relationship Boundary, Subject–Subject Relationships, Subject–Object Relationships, Subject–Basis Relationships, Direct and Indirect Relationships, Multi-Subject Relationships, Multiple Relationships, Relationship Dependencies, Relationship Hierarchies, Relationship Networks, Formal and Operational Relationships, Temporal Relationship States, Relationship Uncertainty, Relationship Change, and Relationship Continuity.
Its principal output is a:
Governed Liability Relationship Structure
What Does LRS Not Govern?
LRS does not determine:
whether Liability Conditions are satisfied, whether a Liability-Relevant Connection exists, whether Liability attaches, whether a Subject is legally liable, the Scope of established Liability, how Liability is allocated, how Liability is transferred, whether Recourse exists, whether Liability has been resolved, or whether Liability has reached Finality.
These questions belong to later LIGA™ governance spaces.
LRS structures the relationships.
It does not decide the Liability outcome.
Liability Subject and Liable Subject
A Subject becomes relevant to LRS because its participation may matter to the Liability inquiry.
That does not mean the Subject bears Liability.
A manufacturer may be relevant.
An operator may be relevant.
An owner may be relevant.
A contractor may be relevant.
A provider may be relevant.
An AI system or autonomous system may be operationally relevant.
The existence of that relevance does not establish Liability.
Liability relevance is not Liability Attachment.
Liability Relationship and Liability
The existence of a relationship between Subjects does not establish Liability.
A contractual relationship does not automatically establish contractual Liability.
An ownership relationship does not automatically establish owner Liability.
A control relationship does not automatically establish controller Liability.
An agency relationship does not automatically establish principal or agent Liability.
A service relationship does not automatically establish provider Liability.
LRS therefore preserves the distinction:
Relationship → potential Liability relevance not:
Relationship → Liability
Responsibility, Accountability and Liability
Responsibility and Accountability may be important inputs to Liability Relationship governance.
They remain separate governed concepts.
Responsibility ≠ Liability.
Accountability ≠ Liability.
AGA™ governs Responsibility and Accountability.
LIGA™ governs Liability.
A Subject may therefore be responsible or accountable within a system without LRS or later LIGA™ governance automatically determining that the Subject bears Liability.
Formal and Operational Relationships
A formal relationship may differ from the relationship that exists in Operational Reality.
An organization chart may identify one controller while actual operational control is exercised elsewhere.
A contract may identify one operator while another Subject performs the relevant operational function.
A nominal role may therefore differ from an operational role.
LRS can preserve both structures where the distinction is materially relevant.
Formal Relationship ≠ Operational Relationship by default.
Relationship Networks
Liability should not be assumed to consist of one relationship between one actor and one consequence.
A single matter may create a network of Liability-relevant relationships.
For example:
Subject A → Subject B Subject B → Subject C Subject A → Subject D Subject D → Subject C Each relationship may arise from a different Basis, role, authority, obligation, or operational structure.
LRS preserves these relationships separately so later Liability governance can evaluate them without collapsing the complete network into a single actor–Liability assumption.
One Liability Relationship ≠ Complete Liability Network.
Position in the LIGA™ Governance Flow
The canonical LIGA™ Governance Flow is:
Liability Context → Liability Object → Liability Basis → Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Scope & Allocation → Liability State & Change → Liability Transfer & Recourse → Liability Resolution & Discharge → Liability Continuity & Finality LRS governs:
Liability Relationships
It receives:
Governed Liability Basis
and produces:
Governed Liability Relationship Structure
for:
Liability Conditions Governance
Relationship to Adjacent Architectures
LRS may receive governed inputs from other OOF® architectures without taking ownership of their domains.
GOA™ may provide Authority, Scope, and Delegation structures.
ORA™ may establish actual operational roles and relationships.
AGA™ may provide Responsibility, Accountability, Authority, and Attribution states.
HAGA™ may identify Harm-relevant actors and relationships.
ADIT® may provide evidence concerning identities, roles, relationships, authority, and historical states.
VALIDOS™ may validate relationship-relevant information.
OBIDENITY® may provide Identity, Ownership, Authority, Permission, Provenance, and Continuity states.
AIG® and ASGA™ may provide AI-system and autonomous-system governance relationships.
These inputs may become relevant to LRS.
They do not become Liability merely because they enter Liability governance.
Critical Distinctions
Liability Subject ≠ Liable Subject Liability Relationship ≠ Liability Subject Identity ≠ Subject Role One Subject ≠ One Role Same Subjects ≠ Same Relationship One Subject Pair ≠ One Liability Relationship One Liability Relationship ≠ Complete Liability Network Responsibility ≠ Liability Accountability ≠ Liability Authority ≠ Liability Control ≠ Liability Ownership ≠ Liability Delegation ≠ Liability Transfer Contractual Relationship ≠ Contractual Liability Agency Relationship ≠ Liability Attribution Formal Relationship ≠ Operational Relationship by default Nominal Role ≠ Operational Role by default Relationship Scope ≠ Liability Scope Relationship Structure ≠ Liability Allocation Liability Relationship ≠ Liability-Relevant Connection Liability Relationship ≠ Liability Attachment Harm-Producing Actor ≠ Liability-Bearing Party by default Liability-Bearing Party ≠ Paying Party by default
Use Case 1 — AI-Enabled Service
An AI-enabled service involves a technology provider, deploying organization, operator, customer, and AI system.
A Liability-relevant event occurs.
LRS does not select the nearest visible actor and treat that actor as liable.
Instead, it structures the relevant relationships:
provider ↔ deployer, deployer ↔ operator, provider ↔ AI system, operator ↔ AI system, deployer ↔ customer, and any other materially relevant relationships.
Formal authority, operational control, contractual roles, and actual operational roles may differ.
LRS preserves those differences for later Liability Conditions, Connection, and Determination governance.
No Subject becomes liable merely because it appears in the relationship map.
Use Case 2 — Industrial Equipment Matter
An industrial equipment matter involves a manufacturer, equipment owner, operating company, maintenance provider, contractor, and operator.
The same equipment may simultaneously participate in:
an ownership relationship, a maintenance relationship, an operating relationship, a contractual relationship, and a control relationship.
LRS identifies the relevant Subjects and maps the relationships separately.
The operator who was physically closest to the event is not automatically treated as the Liability-bearing party.
Likewise, ownership, maintenance responsibility, or contractual participation does not automatically establish Liability.
The resulting Governed Liability Relationship Structure provides the relational foundation for later evaluation of Conditions and Liability-Relevant Connection.
Canonical Closing Statement
Liability cannot be determined reliably when the relationships surrounding it remain undefined.
LRS establishes who or what participates in the potential Liability structure and how those participants relate to one another without converting participation, role, responsibility, authority, control, or proximity into Liability.
Relationship creates structure. It does not create Liability.
Map the relationships before determining who bears Liability.