LSHRM — Liability Sharing Module
LSHRM — Liability Sharing Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Transfer & Recourse Standard (LTRS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Sharing
Module ID: LIGA-LTRS-LSHRM-001
Origin ID: OOF.CM.LIGA.10.02.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 24 September 2026
Compatibility: OOF® Methodology OS™ · Modular OOF® Architecture Ecosystem
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection: MIP® — Methodological Intellectual Property
Canonical Language: English (UCL™)
Canonical Definition
The Liability Sharing Module (LSHRM) governs how established Liability or a defined Liability-related consequence may be shared, participated in, or distributed across multiple Subjects after the primary Liability structure has been established.
LSHRM identifies the Sharing Object, participating Subjects, Sharing Basis, Sharing Scope, individual shares, conditions, effective time, dependencies, unresolved portions, and relationship between the Sharing structure and the primary Liability from which it arises.
It distinguishes subsequent Liability Sharing from the initial Liability Allocation governed by LSAS.
LSHRM does not assume that multiple Liability Subjects bear equal shares, that payment proportions define substantive Liability shares, or that Sharing creates a new Liability Origin.
It preserves the primary Liability structure while making subsequent multi-Subject participation explicit and governable.
It governs the transition:
Identified Liability Transfer Structure / Governed Liability Structure → Sharing Relevance → Sharing Object → Participating Subjects → Sharing Basis → Share Structure → Sharing Boundary → Governed Liability Sharing
Structure
Its foundational distinction is:
Initial Liability Allocation ≠ Subsequent Liability Sharing.
Operational Role
The operational role of LSHRM is:
to govern how a defined Liability or Liability-related consequence is shared among multiple Subjects without silently rewriting the primary Liability, its original Scope, or its original Allocation.
The module determines:
what is being shared, who participates, why Sharing exists, how far it extends, how individual shares relate to one another, and what remains outside the Sharing structure.
Position in the LTRS Internal Flow
The internal LTRS progression is:
Liability Transfer Identification → Liability Sharing → Liability Recourse Identification → Liability Recourse Network → Liability Transfer Continuity LSHRM governs:
Liability Sharing
Its relevant input may include:
Identified Liability Transfer Structure
and the associated established Liability structure.
Its principal output is:
Governed Liability Sharing Structure
Its downstream handoff supports:
LREIM — Liability Recourse Identification Module
where Sharing, performance, payment, or imbalance creates potential Recourse relevance.
Central Operational Question
What Liability or Liability-related consequence is being shared, among which Subjects, on what basis, to what extent, and without rewriting the primary Liability structure from which the Sharing arises?
Sharing Relevance
LSHRM begins where an established Liability structure contains or develops legitimate multi-Subject participation in a defined Liability or Liability-related consequence.
Sharing relevance may arise through:
agreement, joint participation, Contribution structure, indemnification, insurance arrangements, succession, performance arrangements, institutional mechanisms, or another legitimate basis.
Sharing relevance does not itself establish a governed Sharing structure.
Therefore:
Sharing Relevance ≠ Governed Liability Sharing.
Primary Liability Association
Every Sharing structure should remain associated with the primary Liability from which it arises.
This association should preserve, where relevant:
Liability Origin, Determination, Scope, Allocation, Subjects, Relationships, State, and history.
Therefore:
Liability Sharing without Primary Liability Association ≠ Fully Governed Liability Sharing.
Sharing Object
LSHRM should identify exactly what is being shared.
A Sharing Object may include:
a Liability-related obligation, economic burden, performance requirement, payment burden, defined Liability consequence, or substantive Liability participation where applicable.
The Sharing Object must be explicit.
Sharing Object vs Primary Liability
The object being shared may be narrower than the complete primary Liability.
Therefore:
Sharing Object ≠ Complete Primary Liability by default.
Sharing Object Classification
A Sharing structure should distinguish whether Subjects share:
substantive Liability participation, obligation, performance, economic burden, payment, or another defined Liability-related consequence.
These forms should not be collapsed.
Participating Subjects
Every Sharing structure should identify all materially participating Subjects.
A Subject may participate in one shared component while remaining outside another.
Therefore:
Participation in One Sharing Structure ≠ Participation in All Liability Structures.
Subject Role
Each participating Subject should have an explicit role.
Roles may include:
Liability-bearing Subject, performing Subject, paying Subject, indemnifying Subject, insured Subject, insuring Subject, contributing Subject, or another governed role.
Multi-Role Subjects
One Subject may occupy more than one role.
The roles should remain separately identifiable where their governance effects differ.
Therefore:
One Subject ≠ One Liability Role by default.
Sharing Basis
Every governed Sharing structure requires an identifiable Sharing Basis.
The basis may arise through:
law, agreement, existing Liability Relationship, Contribution structure, indemnification, insurance mechanism, succession, or another legitimate source.
Sharing Basis vs Primary Liability Basis
The basis for Sharing may differ from the basis that established primary Liability.
Therefore:
Primary Liability Basis ≠ Sharing Basis by default.
Sharing Authority
Where authority is required, LSHRM should identify:
the applicable authority, authority source, authority scope, and affected Sharing Object.
Authority to establish one Sharing structure does not automatically authorize modification of the complete primary Liability.
Sharing Scope
The Sharing Scope defines the portion of the relevant Liability-related structure governed by Sharing.
It should identify:
what is included, what is excluded, which Subjects participate, which Relationships are affected, and any material limitations.
Sharing Boundary
A Sharing Boundary prevents a defined shared structure from expanding into unrelated Liability components.
Therefore:
Shared Component ≠ Entire Liability Structure by default.
Complete Sharing
A defined Sharing Object may be fully distributed among participating Subjects.
Complete distribution of the Sharing Object does not mean that the complete primary Liability has been shared.
Partial Sharing
Only part of a Sharing Object may be distributed.
The shared and unshared portions should remain explicit.
Therefore:
Partial Sharing ≠ Complete Sharing.
Individual Share
Each materially relevant Subject's share should be separately identifiable.
A share may be represented through:
proportion, amount, obligation, defined performance, economic exposure, or another governed measure.
Equal Sharing
Equal Sharing should be represented only where an applicable Sharing Basis establishes it.
Therefore:
Multiple Liability Subjects ≠ Equal Liability Shares.
Unequal Sharing
Different Subjects may legitimately possess different shares.
The difference should remain traceable to the applicable Sharing Basis or governed structure.
Fixed Share
A share may be defined as a fixed portion or amount.
The unit and object to which the fixed share applies should remain explicit.
Variable Share
A share may vary according to governed conditions, time, performance, exposure, or another defined variable.
The variation mechanism should remain explicit.
Conditional Share
A Subject's participation may depend upon defined conditions.
Therefore:
Conditional Share ≠ Active Share by default.
Unresolved Share
Where a Subject's exact share cannot yet be established, it should remain unresolved rather than being assigned arbitrarily.
Therefore:
Unresolved Share ≠ Zero Share.
Unknown Share
Where available information cannot establish the share, the state should remain Unknown.
Therefore:
Unknown Share ≠ No Share.
Uncertain Share
Where several materially plausible shares remain, uncertainty should remain explicit.
Therefore:
Uncertain Share ≠ Authority to Select a Preferred Share.
Disputed Share
Where materially competing governed positions exist concerning a Subject's share, the dispute should remain represented.
Therefore:
Disputed Share ≠ Determined Share.
Share Total
Where shares are quantitatively represented, LSHRM should assess whether the represented shares correspond to the defined Sharing Object.
A discrepancy should not be hidden.
Under-Represented Sharing
Where represented shares do not account for the complete Sharing Object, the unresolved portion should remain explicit.
Therefore:
Incomplete Share Total ≠ Complete Sharing Structure.
Over-Represented Sharing
Where represented shares exceed the Sharing Object or otherwise overlap improperly, the inconsistency should be identified.
Overlapping Shares
Two shares may legitimately overlap only where the governance structure permits overlapping participation.
Overlap should never be assumed.
Sharing vs Initial Allocation
LSAS determines how established Liability is initially scoped and allocated.
LSHRM governs subsequent Sharing of Liability or Liability-related consequences.
Therefore:
Liability Allocation ≠ Liability Sharing.
A Sharing structure should not silently rewrite the historical Allocation.
Sharing vs Reallocation
Where the primary Allocation itself must change, the matter should return to LSAS.
LSHRM should not perform that change indirectly.
Therefore:
Subsequent Sharing ≠ Primary Liability Reallocation.
Sharing vs Transfer
Transfer concerns movement of a defined Transfer Object from one Subject to another.
Sharing concerns participation of multiple Subjects in a defined structure.
Therefore:
Liability Sharing ≠ Liability Transfer.
Sharing Following Transfer
A transferred Liability-related object may subsequently become shared.
The Transfer and Sharing events should remain separately identifiable.
Transfer Following Sharing
A Subject's share may subsequently transfer.
The Sharing structure should preserve the pre-Transfer share and identify the affected portion.
Sharing vs Contribution
Contribution may create or modify an economic relationship among Subjects after one Subject bears more than an applicable share.
Sharing defines participation.
Contribution concerns recovery or balancing among Subjects.
Therefore:
Liability Sharing ≠ Contribution.
Sharing vs Recourse
Recourse creates a secondary recovery relationship.
Sharing identifies participation in a Liability-related structure.
Therefore:
Liability Sharing ≠ Liability Recourse.
Sharing vs Payment
Payment may satisfy all or part of a Subject's shared obligation.
Payment itself does not define the Subject's substantive share.
Therefore:
Payment Proportion ≠ Liability Share by default.
Sharing vs Performance
Performance may differ from substantive share.
A Subject may perform more or less than its share for operational reasons.
Therefore:
Performance Proportion ≠ Liability Share by default.
Sharing vs Economic Burden
The economic burden ultimately borne by a Subject may differ from its substantive Liability share because of insurance, indemnification, Contribution, or Recourse.
Therefore:
Economic Burden Share ≠ Liability Share by default.
Sharing vs Harm Contribution
A Subject's contribution to Harm does not automatically establish its Liability share.
Therefore:
Harm Contribution ≠ Liability Share by default.
Sharing vs Responsibility
Responsibility distribution does not automatically determine Liability Sharing.
Therefore:
Responsibility Share ≠ Liability Share by default.
Sharing vs Accountability
Accountability distribution does not automatically establish Liability Sharing.
Therefore:
Accountability Distribution ≠ Liability Sharing.
Sharing Effective Time
LSHRM should identify when a Sharing structure or individual share becomes operative.
Sharing Formation Time
The time a Sharing arrangement is formed may differ from its effective time.
Therefore:
Sharing Formation Time ≠ Sharing Effective Time by default.
Sharing Recording Time
The time Sharing is recorded may differ from the time it becomes effective.
Therefore:
Sharing Recording Time ≠ Sharing Effective Time by default.
Prospective Sharing
A Sharing structure may be established for future effect.
Therefore:
Future Sharing Structure ≠ Current Sharing State.
Retrospective Sharing Identification
A Sharing structure may be identified after it became effective.
Historical effective time and later discovery time should remain distinct.
Sharing State
A Sharing structure may be represented as:
Proposed, Pending, Conditional, Active, Partially Active, Suspended, Modified, Disputed, Unknown, Uncertain, Superseded, or another explicitly governed state.
These are methodological states, not universal legal classifications.
Shared Liability State
Different Subjects may occupy different states within the same Sharing structure.
Therefore:
Shared Liability ≠ Shared Liability State.
Subject-Specific Sharing State
A change affecting one Subject's share does not automatically alter another Subject's share.
Therefore:
Subject A Sharing Change ≠ Subject B Sharing Change by default.
Sharing Change
A Sharing structure may change over time.
A material change should identify:
the prior structure, the changed component, the affected Subject, the basis, effective time, and resulting structure.
Share Increase
A Subject's share may increase under a legitimate basis.
An increase should not silently reduce another Subject's share unless the governing structure establishes that relationship.
Share Reduction
A Subject's share may decrease.
The destination or treatment of the reduced portion should remain explicit where relevant.
Share Termination
A Subject's participation may cease.
Termination of one share does not automatically terminate the complete Sharing structure.
Therefore:
Share Termination ≠ Sharing Structure Termination.
Share Succession
A Subject's share may continue through succession.
The predecessor, successor, affected share, basis, and effective time should remain explicit.
Share Transfer
A share may itself become the object of a Transfer.
The Share Transfer should remain associated with both the Sharing structure and the Transfer structure.
Share Performance
Performance against a share should remain distinguishable from the share itself.
Therefore:
Share Performance ≠ Share Identity.
Excess Performance
A Subject may perform more than its governed share.
Excess performance may create Contribution or Recourse relevance.
It does not automatically alter the original share.
Therefore:
Excess Performance ≠ Increased Liability Share by default.
Underperformance
A Subject may perform less than its share.
Underperformance does not automatically redistribute the substantive shares of other Subjects.
Therefore:
Underperformance ≠ Automatic Share Redistribution.
Sharing and Recourse Trigger
A mismatch between governed share and actual payment or performance may create potential Recourse relevance.
Therefore:
Share–Performance Imbalance ≠ Established Recourse.
The matter should proceed to LREIM where appropriate.
Multi-Relationship Sharing
A Sharing structure may span several Liability Relationships.
Each Relationship should remain distinguishable.
Therefore:
Shared Structure ≠ Single Liability Relationship by default.
Liability Network Sharing
Where Sharing exists across a Liability Network, LSHRM should preserve:
Relationship identity, Subject identity, individual shares, cross-Relationship dependencies, and network boundaries.
Local Share vs Network Share
A Subject's share within one Relationship should not automatically become its share across the complete Liability Network.
Therefore:
Local Liability Share ≠ Network-Wide Liability Share by default.
Network Share Aggregation
Where aggregation is useful, the aggregate should remain traceable to the underlying individual shares.
Therefore:
Aggregate Share ≠ Replacement for Relationship-Level Shares.
Sharing Dependencies
A share may depend upon:
another Subject's participation, a condition, a Transfer, an obligation, an authority decision, performance, or another governed structure.
Dependencies should remain explicit.
Sharing Conflict
Different sources may produce incompatible Sharing structures.
The conflict should remain represented until legitimately resolved.
Therefore:
Conflicting Sharing Structures ≠ One Governed Sharing Structure by default.
Duplicate Sharing Records
Multiple records may represent the same Sharing arrangement.
Duplicates should not create additional shares.
Therefore:
Multiple Sharing Records ≠ Multiple Liability Shares by default.
Sharing Evidence Association
Evidence may support:
participating Subjects, Sharing Basis, share amount, conditions, effective time, or performance.
Evidence does not itself create the share.
Therefore:
Evidence of Sharing ≠ Liability Sharing itself.
Sharing Authority Boundary
An authority may govern one part of the Sharing structure without controlling all Liability Relationships.
Therefore:
Sharing Authority ≠ Universal Liability Authority.
Sharing Provenance
A Governed Liability Sharing Structure should preserve sufficient provenance to reconstruct:
its primary Liability origin, Sharing Object, participating Subjects, Sharing Basis, share formation, changes, effective times, authority, and supporting governed inputs.
Sharing Rationale
Where a share is established or changed, the reason should remain reconstructable.
Therefore:
Share Value ≠ Sharing Rationale.
Historical Integrity
A new Sharing structure should not erase the primary Liability Allocation or prior Sharing structures.
Therefore:
Current Sharing Structure ≠ Complete Sharing History.
Sharing Correction
Where a Sharing record was incorrect, it may be corrected while preserving the prior record and correction history.
Therefore:
Sharing Correction ≠ Historical Erasure.
Sharing Reassessment
A previously legitimate Sharing structure may require reassessment when materially relevant circumstances change.
Therefore:
Sharing Reassessment ≠ Sharing Correction.
Sharing Supersession
A later Sharing structure may supersede an earlier structure.
The earlier structure should remain reconstructable.
Therefore:
Sharing Supersession ≠ Historical Deletion.
Upstream Re-Entry
Where Sharing governance reveals that the original Liability Scope or Allocation is materially defective, governance should return to the earliest materially affected LIGA™ space.
LSHRM must not repair upstream defects through secondary Sharing.
The rule is:
Re-enter the earliest materially affected governance space.
Re-Entry Integrity
Where re-entry occurs:
Reassess what materially changed. Preserve what remains valid.
and:
Re-entry must not rewrite history.
No Determination Shortcut
Sharing does not establish whether primary Liability exists.
Therefore:
Liability Sharing ≠ Liability Determination.
No Scope Shortcut
Sharing does not independently redefine primary Liability Scope.
Therefore:
Liability Sharing ≠ Primary Liability Scope Determination.
No Allocation Shortcut
Sharing should not silently replace initial Liability Allocation.
Therefore:
Liability Sharing ≠ Primary Liability Reallocation.
No Recourse Shortcut
A shared Liability structure does not automatically create Recourse.
Therefore:
Liability Sharing ≠ Established Recourse.
No Resolution Shortcut
Sharing does not establish Resolution or Discharge.
Therefore:
Liability Sharing ≠ Liability Resolution.
No Finality Shortcut
Sharing does not establish Liability Finality.
Therefore:
Liability Sharing ≠ Liability Finality.
Automated Sharing Governance
AI or automated systems may assist with:
Subject identification, share calculation, Sharing Object classification, dependency mapping, performance comparison, conflict detection, and historical reconstruction.
Automated calculations should not independently establish authoritative Liability shares.
Therefore:
Automated Share Calculation ≠ Authoritative Liability Sharing by default.
Governed Liability Sharing Structure
The principal output of LSHRM is:
Governed Liability Sharing Structure
It should identify, where applicable:
Primary Liability association, Sharing Identity, Sharing Object, Sharing Object classification, participating Subjects, Subject roles, Sharing Basis, Sharing authority, Sharing Scope, Sharing Boundary, individual shares, unresolved shares, conditions, dependencies, Sharing State, effective time, changes, Transfer associations, Succession associations, performance associations, payment associations, potential Contribution relevance, potential Recourse relevance, Relationship structure, network relevance, uncertainty, disputes, conflicts, rationale, provenance, and history.
Meaning of the Output
A Governed Liability Sharing Structure means that multi-Subject participation in a defined Liability or Liability-related consequence has been sufficiently identified, bounded, distributed, and preserved for continued LTRS governance.
It does not mean that every Subject has performed its share.
It does not mean that Recourse has arisen.
It does not mean that primary Liability has been reallocated.
Therefore:
Governed Liability Sharing Structure ≠ Completed Liability Performance.
Handoff to Liability Recourse Identification
Where Sharing governance identifies:
excess performance, unequal payment relative to governed share, Contribution relevance, indemnification, reimbursement, or another potential secondary recovery relationship, the relevant structure proceeds to:
LREIM — Liability Recourse Identification Module
The boundary is explicit:
LSHRM governs Sharing.
LREIM identifies potential Recourse.
Minimum Implementation Framework
A conforming implementation of LSHRM must provide exactly the following eight capabilities:
Primary Liability & Sharing Object Association
Capability to associate Sharing with the primary Liability and identify the exact Liability, obligation, performance, economic burden, payment burden, or other Liability-related consequence being shared.
Participating Subject, Role & Sharing Basis Governance
Capability to identify participating Subjects, distinguish their Liability, payment, performance, insurance, indemnification, and contribution roles, and establish the applicable Sharing Basis and authority.
Sharing Scope, Boundary & Individual Share Governance
Capability to establish Sharing Scope, included and excluded structures, individual shares, complete and partial Sharing, fixed, variable, conditional, unresolved, Unknown, Uncertain, and Disputed shares.
Allocation, Transfer, Performance & Economic-Burden Distinction Governance
Capability to distinguish subsequent Sharing from primary Allocation, Transfer, Contribution, Recourse, payment, performance, economic burden, Harm contribution, Responsibility, and Accountability.
Temporal, State, Dependency & Change Governance
Capability to govern Sharing effective time, formation and recording times, Sharing States, dependencies, share increases, reductions, termination, succession, Transfer, correction, reassessment, and supersession.
Multi-Relationship, Network, Aggregation, Conflict & Duplicate Governance
Capability to govern Sharing across multiple Liability Relationships and Networks while preserving local shares, network boundaries, aggregation traceability, conflicts, and duplicate records.
Historical Integrity, Provenance, Re-Entry & Upstream Preservation
Capability to preserve primary Liability Allocation, Sharing history, rationale, evidence association, provenance, and targeted upstream re-entry without silently rewriting Determination, Scope, or Allocation.
Recourse Identification Handoff Governance
Capability to produce a Governed Liability Sharing Structure sufficiently explicit and traceable to identify excess performance, payment imbalance, Contribution, indemnification, reimbursement, or other potential Recourse relationships for LREIM.
Governance Logic
The canonical LSHRM governance logic is:
Established Liability Structure / Identified Liability Transfer Structure
↓
Identify Sharing Relevance
↓
Associate Primary Liability
↓
Identify Sharing Object
↓
Identify Participating Subjects & Roles
↓
Identify Sharing Basis & Authority
↓
Establish Sharing Scope & Boundary
↓
Establish Individual Shares
↓
Identify Unresolved / Unknown / Uncertain / Disputed Shares
↓
Distinguish Sharing from Allocation / Transfer / Payment / Performance / Recourse
↓
Establish Effective Time & Sharing State
↓
Identify Dependencies & Changes
↓
Assess Multi-Relationship / Network Structure
↓
Preserve Primary Allocation & Historical Integrity
↓
Assess Contribution / Recourse Relevance
↓
Governed Liability Sharing Structure
↓ Handoff to Liability Recourse Identification where applicable
Governance Outputs
LSHRM may produce:
Sharing Identity
Primary Liability Association
Sharing Object
Sharing Object Classification
Participating Subject Set
Subject Role Structure
Sharing Basis
Sharing Authority Association
Sharing Scope
Sharing Boundary
Individual Liability Share
Fixed Share
Variable Share
Conditional Share
Unresolved Share
Unknown Share
Uncertain Share
Disputed Share
Share Total Assessment
Sharing State
Sharing Effective Time
Sharing Dependency Record
Sharing Change Record
Share Succession Record
Share Transfer Association
Performance Association
Payment Association
Multi-Relationship Sharing Structure
Network Sharing Structure
Sharing Conflict Record
Sharing History
Sharing Rationale
Sharing Provenance Record
Potential Contribution Record
Potential Recourse Relevance Record
The principal output is:
Governed Liability Sharing Structure
Critical Distinctions
LSHRM preserves the following distinctions:
Initial Liability Allocation ≠ Subsequent Liability Sharing Sharing Relevance ≠ Governed Liability Sharing Liability Sharing without Primary Liability Association ≠ Fully Governed Liability Sharing Sharing Object ≠ Complete Primary Liability by default Participation in One Sharing Structure ≠ Participation in All Liability Structures One Subject ≠ One Liability Role by default Primary Liability Basis ≠ Sharing Basis by default Shared Component ≠ Entire Liability Structure by default Partial Sharing ≠ Complete Sharing Multiple Liability Subjects ≠ Equal Liability Shares Conditional Share ≠ Active Share by default Unresolved Share ≠ Zero Share Unknown Share ≠ No Share Uncertain Share ≠ Authority to Select a Preferred Share Disputed Share ≠ Determined Share Incomplete Share Total ≠ Complete Sharing Structure Liability Allocation ≠ Liability Sharing Subsequent Sharing ≠ Primary Liability Reallocation Liability Sharing ≠ Liability Transfer Liability Sharing ≠ Contribution Liability Sharing ≠ Liability Recourse Payment Proportion ≠ Liability Share by default Performance Proportion ≠ Liability Share by default Economic Burden Share ≠ Liability Share by default Harm Contribution ≠ Liability Share by default Responsibility Share ≠ Liability Share by default Accountability Distribution ≠ Liability Sharing Sharing Formation Time ≠ Sharing Effective Time by default Sharing Recording Time ≠ Sharing Effective Time by default Future Sharing Structure ≠ Current Sharing State Shared Liability ≠ Shared Liability State Subject A Sharing Change ≠ Subject B Sharing Change by default Share Termination ≠ Sharing Structure Termination Share Performance ≠ Share Identity Excess Performance ≠ Increased Liability Share by default Underperformance ≠ Automatic Share Redistribution Share–Performance Imbalance ≠ Established Recourse Shared Structure ≠ Single Liability Relationship by default Local Liability Share ≠ Network-Wide Liability Share by default Aggregate Share ≠ Replacement for Relationship-Level Shares Conflicting Sharing Structures ≠ One Governed Sharing Structure by default Multiple Sharing Records ≠ Multiple Liability Shares by default Evidence of Sharing ≠ Liability Sharing itself Sharing Authority ≠ Universal Liability Authority Share Value ≠ Sharing Rationale Current Sharing Structure ≠ Complete Sharing History Sharing Correction ≠ Historical Erasure Sharing Reassessment ≠ Sharing Correction Sharing Supersession ≠ Historical Deletion Liability Sharing ≠ Liability Determination Liability Sharing ≠ Primary Liability Scope Determination Liability Sharing ≠ Primary Liability Reallocation Liability Sharing ≠ Established Recourse Liability Sharing ≠ Liability Resolution Liability Sharing ≠ Liability Finality Automated Share Calculation ≠ Authoritative Liability Sharing by default Governed Liability Sharing Structure ≠ Completed Liability Performance
Cross-Architecture Boundary
LSHRM may receive governed inputs from adjacent OOF® architectures.
ORA™ may establish relevant operational participation and performance.
HAGA™ may establish Harm and Harm distribution without determining Liability shares.
AGA™ may establish Responsibility and Accountability structures without determining Liability Sharing.
ADIT® may provide evidence and auditability.
VALIDOS™ may validate Sharing-relevant inputs.
OBIDENITY® may govern Subject identity, authority, provenance, and continuity.
VFM® may govern Value Flow and economic distribution.
AIG® and ASGA™ may govern AI and autonomous-system participation.
Those structures may inform Liability Sharing without becoming Liability Sharing themselves.
The canonical interoperability principle is:
Operational participation, Harm contribution, Responsibility distribution, Accountability distribution, and economic burden may inform Liability Sharing, but none determines a Liability share by itself.
Canonical Boundary
LSHRM begins when established Liability contains or develops legitimate multi-Subject Sharing relevance.
LSHRM governs:
Sharing Object, primary Liability association, participating Subjects, Subject roles, Sharing Basis, authority, Scope, Boundary, individual shares, unresolved shares, Sharing States, effective time, dependencies, changes, Transfer associations, performance, payment, multi-Relationship Sharing, network Sharing, conflicts, historical integrity, rationale, provenance, and Recourse relevance.
LSHRM does not independently govern:
initial Liability Determination, initial Liability Scope, initial Liability Allocation, complete Transfer governance, Recourse determination, Resolution, Discharge, or Finality.
LSHRM ends when the Sharing structure is sufficiently governed as a:
Governed Liability Sharing Structure
for continued LTRS governance.
Use Case 1 — Multi-Party Liability Sharing
Three Subjects participate in an established Liability structure.
The original LSAS Allocation remains preserved, but a later agreement establishes how a defined performance burden will be shared among them.
The shares are not equal.
LSHRM identifies:
the Sharing Object, three participating Subjects, their roles, Sharing Basis, individual shares, effective time, and the relationship between the Sharing structure and the original Liability Allocation.
One Subject later performs more than its governed share.
LSHRM does not automatically modify that Subject's substantive Liability share.
Instead, the excess performance is identified as potential Recourse relevance for LREIM.
Use Case 2 — Shared Economic Burden with Insurance
Two Subjects remain within an established Liability structure.
An insurer covers part of the economic consequence attributable to one Subject, while the remaining burden is shared between the two Subjects under a separate arrangement.
LSHRM distinguishes:
primary Liability, original Allocation, economic burden Sharing, insurance performance, the individual shared portions, and each Subject's current Sharing State.
The insurer's payment does not automatically make the insurer a primary Liability-bearing Subject.
The governing distinction remains:
Economic Burden Share ≠ Liability Share by default.
Canonical Closing Statement
Liability Sharing is not simply the presence of multiple Subjects.
It requires a defined object, participating parties, a legitimate basis, bounded shares, and continuity with the primary Liability from which the Sharing arose.
A Subject may pay more than its share.
Another may perform less.
Insurance may change the economic burden.
Contribution or Recourse may later rebalance the consequences.
None of those events should silently rewrite the primary Liability Allocation.
Initial Liability Allocation ≠ Subsequent Liability Sharing.
Govern the shares without losing the Liability structure from which they arose.