LALIM — Liability Allocation Identification Module
LALIM — Liability Allocation Identification Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Scope & Allocation Standard (LSAS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Allocation Identification
Module ID: LIGA-LSAS-LALIM-001
Origin ID: OOF.CM.LIGA.08.03.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 23 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 Allocation Identification Module (LALIM) governs how the need, object, participants, relationships, portions, dimensions, layers, dependencies, and applicable structure of Liability Allocation are identified after a Governed Liability Scope has been established.
LALIM determines what within the established Liability Scope requires Allocation, which Liability Subjects and Liability Relationships may participate in that Allocation, which portions or obligations must remain distinct, and which allocation structures or dependencies require explicit downstream distribution governance.
LALIM does not determine whether Liability exists.
It does not establish Liability Scope.
It does not perform the final distribution of Liability.
It governs the transition:
Governed Liability Scope → Allocation Requirement Identification → Allocation Object Identification → Allocation Participant & Relationship Identification → Allocation Structure Identification → Identified Liability Allocation
Structure
Its foundational distinction is:
Liability Scope ≠ Liability Allocation.
Operational Role
The operational role of LALIM is:
to identify what established Liability must be allocated, between whom or what, through which Liability Relationships, and under what allocation structure before distribution occurs.
LSCBM establishes what Liability covers.
LALIM identifies what within that governed Scope requires Allocation.
LALDM subsequently performs the governed distribution.
Position in the LSAS Internal Flow
The internal LSAS progression is:
Liability Scope Identification → Liability Scope Boundary → Liability Allocation Identification → Liability Allocation Distribution → Liability Scope & Allocation Reconciliation LALIM governs:
Liability Allocation Identification
Its principal input is:
Governed Liability Scope
Its principal output is:
Identified Liability Allocation Structure
Its handoff is:
Identified Liability Allocation Structure → LALDM — Liability Allocation Distribution Module
Central Operational Question
What within the Governed Liability Scope requires Allocation, among which Liability Subjects or Liability Relationships, and through what governed allocation structure must that distribution be performed?
Allocation Requirement
Not every Liability Scope requires multi-party Allocation.
Where Liability belongs entirely to one Subject through one relevant Liability Relationship, Allocation may be structurally simple.
Where multiple Subjects, Relationships, portions, layers, or obligations exist, explicit Allocation governance may be required.
Therefore:
Established Liability Scope ≠ Multi-Party Allocation Requirement by default.
Allocation Requirement Identification
LALIM should explicitly establish whether Allocation is:
Required, Not Required, Partially Required, Pending, Unknown, Uncertain, or Disputed.
The absence of a multi-party Allocation requirement should itself be representable.
Allocation Object
Where Allocation is required, LALIM should identify exactly what is being allocated.
The Allocation Object may concern:
a complete Liability Scope, a defined Scope portion, a specific obligation, a quantitative amount, a qualitative responsibility arising from Liability, a temporal segment, or another governed Liability component.
Allocation Object and Liability Scope
The Allocation Object must remain traceable to the Governed Liability Scope.
Therefore:
Allocation Object ≠ Liability Scope by default.
An Allocation Object may represent only part of the complete Liability Scope.
Allocation Unit
Where useful, LALIM should identify the unit in which Allocation will be governed.
The Allocation Unit may be:
monetary, quantitative, proportional, temporal, obligation-based, performance-based, categorical, or another legitimate governed unit.
Non-Quantitative Allocation
Allocation does not require a numerical division.
A Liability may be distributed through distinct obligations or performance responsibilities.
Therefore:
Liability Allocation ≠ Percentage Distribution by default.
Allocation Subject
LALIM should identify each Liability Subject potentially participating in the Allocation.
A Subject should not become an Allocation Subject merely because it participated in the underlying event.
Therefore:
Event Participant ≠ Allocation Subject by default.
Allocation Relationship
Each potential Allocation Subject should remain associated with the Liability Relationship through which the relevant Liability exists.
Therefore:
Subject Participation ≠ Allocation Relationship.
Attached Subject Requirement
A Subject should not ordinarily receive primary Liability Allocation where Liability has not been sufficiently established for that Subject or relevant Relationship.
Therefore:
Operational Involvement ≠ Allocable Liability.
Where an unresolved Determination exists, the Allocation structure should preserve that unresolved state.
Multi-Subject Allocation
Where multiple Subjects bear established Liability, LALIM should identify each Subject separately.
It should not assume:
equal allocation, proportional allocation, or any particular distribution.
Therefore:
Multiple Liable Subjects ≠ Equal Liability Allocation.
Multi-Relationship Allocation
One Subject may participate through several Liability Relationships.
Each materially distinct Relationship should remain identifiable where Allocation depends upon it.
Therefore:
One Subject ≠ One Allocation Relationship.
Multi-Basis Allocation
Where Liability exists under several Liability Bases, LALIM should determine whether Allocation must remain Basisspecific.
Therefore:
Multiple Liability Bases ≠ One Universal Allocation Structure.
Scope Portion Identification
A Governed Liability Scope may contain several portions requiring different Allocation treatment.
LALIM should identify materially distinct portions before distribution.
Included Scope and Allocation
Only governed in-Scope Liability should normally proceed into primary Allocation.
Excluded Scope should not be distributed as though it were established Liability.
Therefore:
Excluded Scope ≠ Allocable Liability.
Partial Scope and Allocation
Where a Scope component is only partially included, Allocation should concern only the governed included portion unless another legitimate structure applies.
Therefore:
Partially Included Scope ≠ Fully Allocable Scope.
Unresolved Scope and Allocation
Pending, Unknown, Uncertain, or Disputed Scope should not silently become allocated Liability.
LALIM should preserve the unresolved state.
Therefore:
Unresolved Scope ≠ Allocated Liability.
Allocation Dimension
Allocation may require governance across one or more dimensions.
These may include:
Subject, Relationship, Basis, Scope portion, obligation, consequence, time, quantity, value, performance, layer, or another materially relevant dimension.
Subject Dimension
The Subject dimension identifies which Liability Subjects may participate in the Allocation structure.
Relationship Dimension
The Relationship dimension identifies through which Liability Relationships each Allocation may exist.
Basis Dimension
The Basis dimension identifies whether Allocation differs according to the Liability Basis supporting the established Liability.
Scope Portion Dimension
Different parts of the Governed Liability Scope may require separate Allocation structures.
Therefore:
One Liability Scope ≠ One Allocation Object by default.
Obligation Dimension
Where Liability contains multiple obligations, LALIM should identify whether those obligations require separate Allocation.
For example, repair and payment obligations may require different participant structures.
Temporal Dimension
Allocation may vary across time.
LALIM should identify temporal segments where different Subjects or Relationships may participate during different periods.
Quantitative Dimension
Where Allocation is measurable, LALIM should identify the relevant quantitative basis without determining the final distributed values.
Qualitative Dimension
Where Liability is allocated through different categories of performance or obligation, LALIM should identify those qualitative dimensions.
Allocation Layer
Complex Liability structures may contain different Allocation layers.
These may include:
primary Liability, secondary Liability relationships, conditional Liability, or another structurally distinct layer.
LALIM should identify the layers without collapsing them.
Primary Allocation
Primary Allocation concerns the distribution of the underlying established Liability.
It should remain distinct from later Transfer or Recourse.
Therefore:
Primary Liability Allocation ≠ Final Economic Burden.
Secondary Liability Relationships
Secondary relationships may exist around the primary Liability structure.
Examples may include:
indemnification, insurance, contribution, reimbursement, or Recourse.
LALIM may identify their existence where necessary to preserve boundaries, but they should not be merged into primary Allocation.
Allocation and Transfer
Transfer may alter who subsequently bears or performs an obligation.
It does not automatically redefine the original Allocation.
Therefore:
Liability Transfer ≠ Primary Liability Allocation.
Allocation and Recourse
Recourse may create a secondary Liability Relationship after primary Liability has been established.
Therefore:
Primary Liability ≠ Recourse Liability.
Recourse governance belongs primarily to LTRS.
Allocation and Insurance
Insurance may affect who pays or reimburses an economic consequence.
It does not automatically identify who bears underlying Liability.
Therefore:
Insurance Coverage ≠ Liability Allocation.
Allocation and Indemnification
An indemnification arrangement may alter downstream economic relationships without changing the primary Liability Allocation.
Therefore:
Indemnification Structure ≠ Primary Liability Allocation.
Liability-Bearing Party and Paying Party
LALIM should preserve the distinction between:
the party to whom Liability is allocated, and:
the party that may ultimately make payment.
Therefore:
Liability-Bearing Party ≠ Paying Party.
Allocation Method Requirement
LALIM should identify what type of Allocation Method will be required downstream.
Possible structures may include:
individual, shared, proportional, non-proportional, layered, conditional, sequential, or composite Allocation.
LALIM identifies the applicable structure.
LALDM performs the distribution.
Individual Allocation Structure
An individual structure exists where a defined Liability Scope or portion is associated with one Liability Subject or Relationship.
Shared Allocation Structure
A shared structure exists where more than one Liability Subject or Relationship participates in the same governed Liability Scope or portion.
Shared does not mean equal.
Therefore:
Shared Allocation ≠ Equal Allocation.
Proportional Allocation Structure
A proportional structure may be identified where the applicable methodology requires distribution through percentages, fractions, ratios, units, or another proportional mechanism.
Identification does not determine the proportions.
Non-Proportional Allocation Structure
Some Liability structures cannot be meaningfully represented through percentages.
Different Subjects may bear distinct obligations rather than shares of one amount.
LALIM should preserve that structure.
Layered Allocation Structure
A layered Allocation structure may be required where different Liability Relationships operate at different levels or under different conditions.
Layers should remain distinct.
Conditional Allocation Structure
An Allocation may depend upon a future or unresolved governed condition.
LALIM should identify that dependency.
Therefore:
Conditional Allocation Requirement ≠ Final Allocation.
Sequential Allocation Structure
Some Allocation structures may require one governed allocation step before another.
Where legitimate, the sequence should be identified before distribution.
Composite Allocation Structure
A complex matter may combine:
individual, shared, proportional, non-proportional, layered, conditional, or sequential elements.
LALIM should preserve the composite structure without forcing it into a single model.
Allocation Dependency
An Allocation may depend upon:
another Scope portion, another Subject state, another Relationship, another Allocation, a temporal condition, or another governed dependency.
Material dependencies should be explicit.
Allocation Prerequisite
Where a prerequisite must be satisfied before distribution, LALIM should identify it.
Therefore:
Identified Allocation ≠ Allocation Readiness by default.
Allocation Readiness
An Allocation structure is ready for distribution when:
the Allocation Object is explicit, the relevant Scope is sufficiently governed, the relevant Subjects are identifiable, the relevant Relationships are identifiable, the Allocation dimensions are explicit, material dependencies are represented, and the applicable Allocation Method can be determined.
Allocation Uncertainty
Where it is uncertain whether a Subject, Relationship, Scope portion, or Allocation Method applies, the uncertainty should remain explicit.
Therefore:
Allocation Uncertainty ≠ Allocation Exclusion.
Allocation Unknown
Where required information is unavailable, the relevant Allocation element may remain Unknown.
Therefore:
Unknown Allocation Element ≠ Zero Allocation.
Allocation Dispute
Different governed positions may exist concerning:
who participates, what is allocable, which method applies, or which relationship governs.
LALIM should preserve the dispute.
Therefore:
Allocation Dispute ≠ Authority to Select a Preferred Distribution.
Allocation Overlap
Two identified Allocation Objects or participant structures may overlap.
The overlap should be identified before distribution.
Therefore:
Allocation Overlap ≠ Additional Liability.
Allocation Duplication
Duplicate records should not create duplicate allocable Liability.
Therefore:
Duplicate Allocation Records ≠ Multiple Liability Portions.
Allocation Conflict
Allocation structures may conflict.
For example, two methods may imply incompatible participant structures.
LALIM should preserve the conflict for resolution rather than silently combining them.
Allocation Network
Complex matters may contain several related Allocation structures.
LALIM should represent these as an Allocation Network where necessary.
Therefore:
One Liability Event ≠ One Allocation Structure.
Local Allocation Structure
An Allocation structure relating to one Liability Relationship may form only one part of a larger Liability Network.
Therefore:
Local Allocation Structure ≠ Complete Liability Network Allocation.
Network Dependency
One Allocation structure may depend upon or interact with another.
These relationships should remain explicit before distribution.
No Harm-Based Allocation Shortcut
The severity or distribution of Harm should not automatically determine Liability Allocation.
Therefore:
Harm Distribution ≠ Liability Allocation.
No Causation-Based Allocation Shortcut
Relative causal contribution should not automatically become Liability Allocation unless the applicable Liability methodology establishes that relationship.
Therefore:
Causal Contribution ≠ Liability Allocation by default.
No Responsibility-Based Allocation Shortcut
Operational or organizational responsibility should not automatically become Liability Allocation.
Therefore:
Responsibility Distribution ≠ Liability Allocation.
No Accountability-Based Allocation Shortcut
Accountability attribution does not automatically determine Liability distribution.
Therefore:
Accountability Attribution ≠ Liability Allocation.
No Fault-Based Allocation Shortcut
A fault percentage does not automatically become a Liability percentage.
Therefore:
Fault Percentage ≠ Liability Allocation by default.
No Payment-Based Allocation Shortcut
Existing payment does not necessarily represent underlying Liability Allocation.
Therefore:
Payment Distribution ≠ Liability Allocation.
No Claim-Based Allocation Shortcut
A Claim may identify a proposed distribution or amount.
It does not establish Allocation.
Therefore:
Claimed Allocation ≠ Governed Liability Allocation.
No Settlement-Based Allocation Shortcut
A negotiated settlement may distribute economic obligations without representing the underlying substantive Liability Allocation.
Therefore:
Settlement Distribution ≠ Liability Allocation by default.
No Insurance-Based Allocation Shortcut
Insurance limits or coverage shares do not automatically define Liability Allocation.
Therefore:
Insurance Share ≠ Liability Allocation.
No Ability-to-Pay Shortcut
Financial capacity should not be converted into Liability Allocation unless the applicable methodology legitimately requires it.
Therefore:
Ability to Pay ≠ Liability Allocation.
Allocation Authority
Where a particular authority, institution, methodology, or process governs Allocation, that authority structure should be identifiable before distribution.
LALIM does not create authority merely by identifying participants.
Automated Allocation Identification
AI or automated systems may assist with identifying Allocation structures where appropriately governed.
The system should preserve:
methodology, input state, scope reference, system identity, authority, uncertainty, and traceability.
Therefore:
Automated Allocation Identification ≠ Authoritative Allocation.
Allocation Identification Traceability
Each identified Allocation element should remain traceable to:
the Governed Liability Scope, the relevant Liability Determination, Subject, Relationship, Basis, Scope portion, and applicable Allocation requirement.
Allocation Identification Explainability
A qualified reviewer should be able to understand:
why Allocation is required, what must be allocated, who or what participates, which Relationships apply, which dimensions matter, and what Allocation structure is required.
Allocation Identification Sufficiency
An Identified Liability Allocation Structure is sufficient when LALDM can perform distribution without reconstructing the Scope or participant structure from raw information.
Allocation Identification Completeness
Identification is complete when all materially necessary:
Allocation Objects, Subjects, Relationships, Scope portions, dimensions, layers, dependencies, and unresolved elements are represented.
Completeness does not require final distribution.
Therefore:
Allocation Identification Completeness ≠ Completed Allocation.
Allocation Identification Change
An identified Allocation structure may change when:
Scope changes, the Liability Determination changes, Subjects or Relationships change, a dependency is resolved, new information becomes available, or an identification error is corrected.
Allocation Identification Correction
An incorrectly identified Allocation element may be corrected.
The prior materially relevant state should remain reconstructable.
Therefore:
Allocation Identification Correction ≠ Historical Erasure.
Allocation Identification Reassessment
Changed governed circumstances may require reassessment of the Allocation structure.
Therefore:
Allocation Identification Reassessment ≠ Allocation Identification Correction.
Re-Entry to Scope Boundary
Where LALIM reveals that the Governed Liability Scope is insufficient or incorrectly bounded, the matter should return to LSCBM.
LALIM must not repair Scope by manipulating Allocation.
Therefore:
Allocation Structure Adjustment ≠ Substitute for Scope Correction.
Re-Entry to Liability Determination
Where the issue originates in Liability Determination, the matter should return to LDS.
Allocation should not be used to compensate for an Attachment defect.
Earlier Lifecycle Re-Entry
Where the issue originates earlier in LIGA™, governance should return to the earliest materially affected governance space.
The governing principle remains:
Re-enter the earliest materially affected governance space.
Historical Integrity
Material earlier Allocation Identification states should remain reconstructable.
Therefore:
Current Allocation Structure ≠ Complete Allocation Structure History.
Identified Liability Allocation Structure
The principal output of LALIM is:
Identified Liability Allocation Structure
It should identify, where applicable:
Allocation requirement, Allocation Object, Allocation Unit, Liability Subjects, Liability Relationships, Liability Bases, Scope portions, Allocation dimensions, Allocation layers, Allocation Method requirement, dependencies, prerequisites, overlaps, conflicts, uncertainty, disputes, authority, and provenance.
Meaning of the Output
An Identified Liability Allocation Structure means the elements necessary for distribution have been sufficiently identified.
It does not mean distribution has occurred.
Therefore:
Identified Liability Allocation Structure ≠ Distributed Liability Allocation.
Handoff to Liability Allocation Distribution
LALIM hands the:
Identified Liability Allocation Structure
to:
LALDM — Liability Allocation Distribution Module
The next governance question becomes:
How must the identified Liability Scope or portions be distributed across the applicable Liability Subjects and Relationships under the governed Allocation structure?
The boundary is explicit:
LALIM identifies what must be allocated and through which structure.
LALDM performs the governed distribution.
Minimum Implementation Framework
A conforming implementation of LALIM must provide exactly the following eight capabilities:
Allocation Requirement & Object Identification
Capability to determine whether Allocation is required and identify the specific Governed Liability Scope, Scope portion, obligation, or other Liability component that constitutes the Allocation Object.
Allocation Subject, Relationship & Basis Identification
Capability to identify the Liability Subjects, Liability Relationships, and Liability Bases relevant to each Allocation inquiry without converting operational participation into allocable Liability.
Allocation Portion, Unit & Dimension Identification
Capability to identify the relevant Scope portions, quantitative or qualitative units, temporal dimensions, obligations, consequences, and other dimensions required for Allocation.
Allocation Structure & Method Identification
Capability to identify whether the required Allocation structure is individual, shared, proportional, non-proportional, layered, conditional, sequential, composite, or another legitimately governed form without performing the distribution.
Allocation Dependency, Layer & Network Governance
Capability to identify prerequisites, dependencies, primary and secondary layers, overlapping structures, and multiRelationship Allocation Networks while preserving boundaries with Transfer and Recourse.
Unknown, Uncertain, Disputed, Duplicate & Conflict Governance
Capability to preserve unresolved participant, Scope, method, dependency, overlap, duplication, and conflict states without forcing premature distribution.
Allocation Identification Change, Correction, Reassessment & Re-Entry
Capability to govern changes, corrections, reassessments, historical states, and targeted lifecycle re-entry without historical erasure.
Allocation Distribution Handoff Governance
Capability to produce an Identified Liability Allocation Structure sufficiently complete, traceable, and methodologically bounded for Liability Allocation Distribution.
Governance Logic
The canonical LALIM governance logic is:
Governed Liability Scope
↓
Determine Whether Allocation Is Required
↓
Identify Allocation Object
↓
Identify Scope Portion / Obligation / Unit
↓
Identify Allocation Subjects
↓
Identify Liability Relationships
↓
Identify Applicable Liability Bases
↓
Identify Allocation Dimensions
↓
Identify Allocation Layers
↓
Identify Required Allocation Structure / Method
↓
Identify Dependencies & Prerequisites
↓
Identify Overlap / Duplication / Conflict
↓
Preserve Unknown / Uncertain / Disputed Elements
↓
Assess Allocation Identification Sufficiency
↓
Identified Liability Allocation Structure
↓
Handoff to Liability Allocation Distribution
Governance Outputs
LALIM may produce:
Allocation Requirement State
Allocation Object Identity
Allocation Scope Reference
Allocation Unit
Allocation Subject Set
Allocation Relationship Set
Allocation Basis Set
Allocation Scope Portion Set
Allocation Obligation Set
Allocation Dimension Set
Allocation Temporal Dimension
Allocation Quantitative Dimension
Allocation Qualitative Dimension
Allocation Layer Structure
Individual Allocation Structure
Shared Allocation Structure
Proportional Allocation Structure
Non-Proportional Allocation Structure
Conditional Allocation Structure
Sequential Allocation Structure
Composite Allocation Structure
Allocation Dependency Record
Allocation Prerequisite Record
Allocation Network Structure
Allocation Overlap Record
Allocation Duplicate Record
Allocation Conflict Record
Unknown Allocation State
Uncertain Allocation State
Disputed Allocation State
Allocation Identification Sufficiency State
The principal output is:
Identified Liability Allocation Structure
Critical Distinctions
LALIM preserves the following distinctions:
Liability Scope ≠ Liability Allocation Established Liability Scope ≠ Multi-Party Allocation Requirement by default Allocation Object ≠ Liability Scope by default Liability Allocation ≠ Percentage Distribution by default Event Participant ≠ Allocation Subject by default Subject Participation ≠ Allocation Relationship Operational Involvement ≠ Allocable Liability Multiple Liable Subjects ≠ Equal Liability Allocation One Subject ≠ One Allocation Relationship Multiple Liability Bases ≠ One Universal Allocation Structure Excluded Scope ≠ Allocable Liability Partially Included Scope ≠ Fully Allocable Scope Unresolved Scope ≠ Allocated Liability One Liability Scope ≠ One Allocation Object by default Primary Liability Allocation ≠ Final Economic Burden Liability Transfer ≠ Primary Liability Allocation Primary Liability ≠ Recourse Liability Insurance Coverage ≠ Liability Allocation Indemnification Structure ≠ Primary Liability Allocation Liability-Bearing Party ≠ Paying Party Shared Allocation ≠ Equal Allocation Conditional Allocation Requirement ≠ Final Allocation Identified Allocation ≠ Allocation Readiness by default Allocation Uncertainty ≠ Allocation Exclusion Unknown Allocation Element ≠ Zero Allocation Allocation Dispute ≠ Authority to Select a Preferred Distribution Allocation Overlap ≠ Additional Liability Duplicate Allocation Records ≠ Multiple Liability Portions One Liability Event ≠ One Allocation Structure Local Allocation Structure ≠ Complete Liability Network Allocation Harm Distribution ≠ Liability Allocation Causal Contribution ≠ Liability Allocation by default Responsibility Distribution ≠ Liability Allocation Accountability Attribution ≠ Liability Allocation Fault Percentage ≠ Liability Allocation by default Payment Distribution ≠ Liability Allocation Claimed Allocation ≠ Governed Liability Allocation Settlement Distribution ≠ Liability Allocation by default Insurance Share ≠ Liability Allocation Ability to Pay ≠ Liability Allocation Automated Allocation Identification ≠ Authoritative Allocation Allocation Identification Completeness ≠ Completed Allocation Allocation Identification Correction ≠ Historical Erasure Allocation Identification Reassessment ≠ Allocation Identification Correction Allocation Structure Adjustment ≠ Substitute for Scope Correction Current Allocation Structure ≠ Complete Allocation Structure History Identified Liability Allocation Structure ≠ Distributed Liability Allocation
Cross-Architecture Boundary
LALIM may use governed states originating from other OOF® architectures where they are materially relevant to identifying the Liability Allocation structure.
For example:
HAGA™ may provide governed Harm states.
ORA™ may provide Operational Reality.
AGA™ may provide Responsibility and Accountability structures.
ADIT® may provide evidence and auditability structures.
VALIDOS™ may provide validation states.
VFM® may provide Value Flow structures.
OBIDENITY® may provide identity, ownership, authority, permission, provenance, and transfer states.
AIG® and ASGA™ may provide AI and autonomous-system governance states.
PGA™ may provide Prediction states.
SIMULOS® may provide Simulation outputs.
LALIM does not convert those external governance structures directly into Liability Allocation.
The canonical interoperability principle is:
An external governed structure may inform the identification of a Liability Allocation structure without becoming Liability Allocation and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LALIM begins with a:
Governed Liability Scope
and governs identification of the structure required for Liability Allocation.
LALIM governs:
Allocation Requirement, Allocation Object, Allocation Unit, Allocation Subjects, Allocation Relationships, Allocation Bases, Scope Portions, Allocation Dimensions, Allocation Layers, Allocation Method requirements, Dependencies, Prerequisites, Network structures, Overlap, Duplication, Conflict, Unknowns, Uncertainty, Disputes, Identification Sufficiency, Change, Correction, Reassessment, Historical Integrity, and Distribution handoff.
LALIM does not govern:
initial Liability Determination, Scope Identification, Scope Boundary establishment, final Liability distribution, Liability State & Change, Transfer, Recourse, Resolution, Discharge, or Finality.
LALIM ends when an:
Identified Liability Allocation Structure
is sufficiently explicit and traceable for Liability Allocation Distribution.
Use Case 1 — Multi-Party Industrial Allocation Identification
A Governed Liability Scope establishes that two Liability Subjects bear Liability relating to different portions of an industrial incident.
LALIM identifies:
the portions requiring Allocation, the relevant Subjects, their Liability Relationships, the applicable Bases, the relevant obligations, and whether the Allocation requires shared, individual, or another distribution structure.
It does not assign percentages or final obligations.
Insurance arrangements and potential Recourse are preserved as separate downstream structures rather than being treated as primary Allocation.
The result is an Identified Liability Allocation Structure ready for LALDM.
Use Case 2 — Autonomous System Allocation Identification
A Governed Liability Scope involves several established Liability Relationships surrounding an autonomous system deployment.
Different Scope portions concern system restoration, operational interruption, and corrective obligations.
LALIM identifies which portions require Allocation, which Subjects and Relationships participate, whether different obligations require separate Allocation structures, and whether any dependencies or unresolved elements remain.
It does not convert technical causation, responsibility, system control, insurance coverage, or financial capacity directly into Liability shares.
The resulting structure gives LALDM a governed basis for performing the actual Liability distribution.
Canonical Closing Statement
A governed Liability Scope establishes what Liability covers.
It does not by itself establish how that Liability should be distributed.
Before distribution occurs, the Allocation Object, participating Subjects, Liability Relationships, relevant Scope portions, dimensions, layers, dependencies, and applicable Allocation structure must be explicit.
LALIM establishes that structure without prematurely assigning Liability shares.
Scope establishes what Liability covers. Allocation Identification establishes what must be distributed and between whom.
Identify the Allocation structure before distributing the Liability.