LSCIM — Liability Scope Identification Module
LSCIM — Liability Scope 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 Scope Identification
Module ID: LIGA-LSAS-LSCIM-001
Origin ID: OOF.CM.LIGA.08.01.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 Scope Identification Module (LSCIM) governs how the scope-relevant components of an established Liability are identified, associated, distinguished, structured, and prepared for explicit Liability Scope Boundary governance.
LSCIM begins with a Governed Liability Determination State and identifies what must be examined when determining the extent of that established Liability.
It identifies the relevant Liability Subject, Liability Relationship, Liability Object, Liability Basis, consequences, obligations, temporal dimensions, quantitative or qualitative dimensions, and other materially relevant scope components without determining their final inclusion, exclusion, or extent.
LSCIM does not establish whether Liability exists.
It does not establish final Liability Scope boundaries.
It does not allocate Liability.
It governs the transition:
Governed Liability Determination State → Scope Object Identification → Scope-Relevant Component Identification → Scope Dimension Identification → Scope Association → Identified Liability Scope Structure Its foundational distinction is:
Liability Attachment ≠ Liability Scope.
Operational Role
The operational role of LSCIM is:
to identify exactly what must be scoped after Liability has been determined to attach.
Before Liability Scope can be bounded, the system must know:
what Liability Determination is being scoped, which Subject and Relationship are involved, which Liability Object is relevant, which Basis governs the Liability, which consequences or obligations may require scope assessment, which dimensions may limit or extend Scope, and which matters require explicit boundary determination.
LSCIM creates that structure.
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 LSCIM governs:
Liability Scope Identification
Its principal input is:
Governed Liability Determination State
Its principal output is:
Identified Liability Scope Structure
Its handoff is:
Identified Liability Scope Structure → LSCBM — Liability Scope Boundary Module
Central Operational Question
What components, dimensions, relationships, consequences, obligations, and boundaries must be examined to determine the extent of this established Liability?
Scope Identification Begins After Determination
LSCIM operates only after Liability has been sufficiently determined.
It must not infer Liability merely because scope-relevant consequences exist.
Therefore:
Scope-Relevant Matter ≠ Established Liability.
The applicable Governed Liability Determination State remains the starting point.
Scope Identification Object
Every Scope Identification process should identify the specific Liability Determination whose Scope is being examined.
The Scope Identification Object should remain associated with:
Determination identity, Attachment State, Liability Subject, Liability Relationship, Liability Object, Liability Basis, and relevant Determination Scope.
Determination Reference
The applicable Governed Liability Determination State should remain explicitly referenced.
LSCIM must not construct Scope from disconnected facts.
Therefore:
Liability Scope Identification without Determination Reference ≠ Governed Scope Identification.
Attachment State
LSCIM should preserve the applicable Attachment State.
Where Liability is:
Attached, Partially Determined, Pending, Unknown, Uncertain, or Disputed, the Scope Identification process should respect that state.
It must not convert an unresolved Determination into established Liability merely by identifying possible Scope.
Liability Subject Identification
LSCIM should identify the Subject to whom or to which the established Liability applies.
Where several Subjects exist, each materially distinct Liability Scope inquiry should remain distinguishable.
Therefore:
One Event ≠ One Subject Scope.
Liability Relationship Identification
The relevant Liability Relationship should be identified.
A Subject may participate in several Relationships while Liability attaches only through one or some of them.
Therefore:
Subject Identity ≠ Liability Relationship Identity.
Liability Object Identification
The governed Liability Object associated with the Determination should remain explicit.
Scope Identification should determine which aspects of that Object require Scope governance.
It should not silently extend Scope to unrelated Objects.
Liability Basis Identification
The applicable Liability Basis should remain associated with Scope Identification.
The Basis may materially affect what types of matters can fall within Liability Scope.
Therefore:
Scope under Basis A ≠ Scope under Basis B by default.
Scope-Relevant Matter
A Scope-Relevant Matter is any governed matter that may require explicit inclusion, exclusion, limitation, or extent determination within the established Liability.
Identification does not determine whether that matter ultimately falls inside the Liability Scope.
Therefore:
Scope-Relevant Matter ≠ In-Scope Matter.
Scope-Relevant Consequences
Where consequences are relevant, LSCIM should identify those requiring Scope assessment.
These may include governed:
Harm, loss, damage, cost, operational consequence, value consequence, or another materially relevant result.
Their identification does not establish inclusion.
Therefore:
Consequence Identification ≠ Liability Scope Inclusion.
Harm-Relevant Scope Components
Where HAGA™ provides governed Harm states relevant to Liability, LSCIM may identify them as Scope-relevant components.
HAGA™ continues to govern Harm.
LSCIM governs only whether the Harm state requires Liability Scope assessment.
Therefore:
Governed Harm ≠ In-Scope Liability Harm by default.
Loss and Damage Components
Loss or damage may require Scope assessment where relevant to the applicable Liability Basis.
LSCIM should identify them without presuming that all measured loss or damage falls within Liability.
Therefore:
Measured Loss ≠ Established Liability Scope.
Obligation Components
Where established Liability may involve obligations, LSCIM should identify the potentially relevant obligations.
These may involve:
payment, performance, repair, restoration, correction, replacement, restriction, or another governed requirement.
Identification does not determine final obligation Scope.
Quantitative Scope Dimensions
Where Liability may have measurable extent, LSCIM should identify the relevant quantitative dimensions.
These may include:
amount, quantity, percentage, duration, units, frequency, or another measurable dimension.
Therefore:
Identified Quantity ≠ Governed Liability Amount.
Qualitative Scope Dimensions
Liability may also contain qualitative dimensions.
These may concern:
type of obligation, category of consequence, required performance, restriction, repair requirement, restoration state, or another non-numerical extent.
Therefore:
Liability Scope ≠ Monetary Scope by default.
Temporal Scope Dimension
LSCIM should identify whether time materially affects Liability Scope.
Relevant temporal dimensions may include:
scope start, scope end, duration, period of applicability, historical period, continuing consequence, or another relevant temporal boundary.
Location Dimension
Where location materially affects Liability Scope, LSCIM should identify the relevant geographic, operational, organizational, or jurisdiction-relevant location dimension.
Identification does not itself determine jurisdiction-specific law.
Activity Dimension
Liability Scope may depend on a particular activity, operation, transaction, conduct, service, or process.
Where relevant, the activity dimension should be identified explicitly.
Asset or Resource Dimension
Where Liability concerns specific assets, resources, infrastructure, data, property, systems, or other governed objects, LSCIM should identify the relevant dimension.
Relationship Dimension
Scope may differ across Liability Relationships.
Where the same Subject participates through several relationships, LSCIM should identify which Relationship each Scope-relevant matter concerns.
Subject Dimension
Scope may differ between Subjects even where they participate in the same occurrence.
Therefore:
Shared Occurrence ≠ Shared Liability Scope.
Basis Dimension
Where multiple Liability Bases exist, LSCIM should distinguish Scope-relevant matters by Basis.
Therefore:
One Matter under Multiple Bases ≠ One Universal Liability Scope.
Consequence Dimension
Different consequences may require separate Scope assessment.
One consequence may fall within established Liability while another does not.
LSCIM should preserve this possibility before boundary governance.
Obligation Dimension
Different obligations may possess different Scope boundaries.
For example, a Liability may involve a repair obligation without necessarily including every related economic consequence.
LSCIM identifies the relevant obligation dimensions without determining their final boundaries.
Multi-Dimensional Scope
A Liability Scope may depend on several dimensions simultaneously.
For example:
Subject + Relationship + Basis + Consequence + Time.
LSCIM should preserve these combinations where materially necessary.
Therefore:
Liability Scope ≠ Single-Dimension Boundary by default.
Scope Component Identity
Each materially distinct Scope component should be identifiable.
A component identity should permit later boundary governance to determine whether that component is:
included, excluded, partially included, or unresolved.
Scope Component Association
Each Scope component should remain associated with the relevant:
Determination, Subject, Relationship, Object, Basis, and applicable Scope dimension.
This prevents components from being detached from the Liability structure that made them relevant.
Scope Component Distinction
Similar Scope components should remain distinguishable where they represent materially different matters.
Therefore:
Similar Consequence ≠ Same Scope Component by default.
Scope Component Dependency
Some Scope components may depend upon others.
For example:
a cost may depend upon a repair obligation, a continuing loss may depend upon a continuing Harm state, or a temporal extent may depend upon an operational state.
Dependencies should be identified where materially relevant.
Scope Component Overlap
Two identified Scope components may overlap.
LSCIM should identify potential overlap so later Scope Boundary governance does not double-count or incorrectly merge them.
Therefore:
Overlapping Scope Components ≠ Independent Scope Components by default.
Scope Component Duplication
Duplicate representations of the same underlying Scope-relevant matter should be detectable.
Therefore:
Multiple Records ≠ Multiple Liability Scope Components.
Scope Component Conflict
Different sources may describe the same potential Scope differently.
LSCIM should preserve material conflict for boundary governance rather than selecting an unsupported interpretation.
Unknown Scope Component
A materially relevant Scope component may be known to exist while its characteristics remain unknown.
Therefore:
Unknown Scope Detail ≠ Absent Scope Component.
Uncertain Scope Component
Where the relevance or characteristics of a component remain uncertain, the uncertainty should remain explicit.
Therefore:
Uncertain Scope Component ≠ Included Scope Component.
Disputed Scope Component
A Scope component may be disputed.
LSCIM should preserve the dispute without deciding the final boundary.
Therefore:
Disputed Scope Component ≠ Excluded Scope Component by default.
Potential Scope Inclusion
LSCIM may identify matters potentially relevant to Scope.
It must not classify them prematurely as included.
That determination belongs to LSCBM.
Therefore:
Potential Scope Inclusion ≠ Governed Scope Inclusion.
Potential Scope Exclusion
Likewise, an apparently remote or limited matter should not be treated as excluded before Scope Boundary governance.
Therefore:
Potential Exclusion ≠ Governed Exclusion.
Scope Identification Completeness
Scope Identification is complete when all materially relevant components and dimensions necessary for boundary governance have been identified or explicitly represented as unresolved.
Completeness does not require every imaginable consequence to be catalogued.
Therefore:
Scope Identification Completeness ≠ Information Exhaustiveness.
Scope Identification Sufficiency
A Scope Identification Structure is sufficient when the next module can determine boundaries without reconstructing the underlying Liability Determination from raw information.
Sufficiency requires enough structure to know:
what is being scoped, for whom, through which Relationship, under which Basis, and across which material dimensions.
Scope Identification and Claims
A Claim may identify alleged amounts, losses, consequences, or requested remedies.
These may become Scope-relevant inputs.
They do not define the Liability Scope.
Therefore:
Claimed Scope ≠ Governed Liability Scope.
Scope Identification and Payment
Existing payment may be relevant context but does not define the Scope of Liability.
Therefore:
Paid Amount ≠ Liability Scope.
Scope Identification and Settlement
A settlement may identify a negotiated amount or obligation.
It should not automatically be interpreted as the substantive Liability Scope.
Therefore:
Settlement Amount ≠ Liability Scope by default.
Scope Identification and Insurance
Insurance coverage, limits, deductibles, or exclusions may be relevant to later economic governance.
They do not define the underlying Liability Scope.
Therefore:
Insurance Limit ≠ Liability Scope.
Scope Identification and Ability to Pay
The financial capacity of a Subject is not a Scope dimension unless a legitimate applicable methodology expressly makes it relevant.
Therefore:
Ability to Pay ≠ Liability Scope.
Scope Identification and Harm Severity
The severity of Harm may be relevant to Scope but does not automatically define it.
Therefore:
Harm Severity ≠ Liability Scope.
Scope Identification and Causation
Operational causation may identify consequences requiring Scope assessment.
It does not establish their inclusion in Liability Scope.
Therefore:
Causal Connection ≠ Scope Inclusion.
Scope Identification and Responsibility
Responsibility may identify relationships or obligations relevant to Scope.
It does not itself define Liability Scope.
Therefore:
Responsibility Scope ≠ Liability Scope.
Scope Identification and Accountability
Accountability structures may provide relevant governed context.
They do not automatically become Liability Scope.
Therefore:
Accountability Scope ≠ Liability Scope.
Multi-Subject Scope Identification
Where several Subjects have Attached Liability, LSCIM should establish separate or explicitly linked Scope Identification structures.
It should not presume that every Subject's Liability covers the same consequences.
Multi-Relationship Scope Identification
Where a Subject has Liability through multiple Relationships, each materially distinct Relationship should remain identifiable.
Therefore:
One Subject ≠ One Universal Scope Inquiry.
Multi-Basis Scope Identification
Where Liability attaches under multiple Bases, the relevant Scope components should remain Basis-specific where necessary.
This prevents Scope from one Basis being silently transferred to another.
Liability Network Scope Identification
A Liability Network may contain several distinct Scope inquiries.
LSCIM should preserve the network relationship while maintaining the identity of each local Scope structure.
Therefore:
Local Scope Inquiry ≠ Complete Liability Network Scope.
Scope Identification Change
New information may reveal additional Scope-relevant components or show that an identified component is no longer relevant.
Changes should remain traceable.
Scope Identification Correction
An incorrectly identified Scope component may be corrected.
The correction should preserve the material historical state where relevant.
Therefore:
Scope Identification Correction ≠ Historical Erasure.
Scope Identification Reassessment
A change in the underlying Liability Determination or relevant operational reality may require Scope Identification reassessment.
Therefore:
Scope Identification Reassessment ≠ Scope Identification Correction.
Determination Change
Where the Governed Liability Determination State changes materially, LSCIM should assess whether the existing Scope Identification Structure remains valid.
It should not silently carry forward components that depend upon a superseded Determination.
Re-Entry
If Scope Identification reveals that the problem originates in Liability Determination or an earlier LIGA™ governance space, the matter should re-enter the earliest materially affected space.
LSCIM must not repair upstream defects by expanding or narrowing the Scope inquiry.
The governing principle is:
Re-enter the earliest materially affected governance space.
Historical Integrity
Material earlier Scope Identification states should remain reconstructable where they informed later Scope or Allocation decisions.
Therefore:
Current Scope Identification ≠ Complete Scope Identification History.
Scope Identification Record
A governed Scope Identification record should preserve, where applicable:
Scope Identification identity, Determination reference, Attachment State, Liability Subject, Liability Relationship, Liability Object, Liability Basis, Scope-relevant matters, Scope dimensions, consequences, obligations, temporal dimensions, quantitative dimensions, qualitative dimensions, dependencies, overlaps, uncertainties, disputes, time, and provenance.
Identified Liability Scope Structure
The principal output of LSCIM is:
Identified Liability Scope Structure
It represents the organized set of materially relevant components and dimensions that require explicit Scope Boundary governance.
It does not establish final Scope.
Therefore:
Identified Liability Scope Structure ≠ Governed Liability Scope.
Handoff to Liability Scope Boundary Governance
LSCIM hands the:
Identified Liability Scope Structure
to:
LSCBM — Liability Scope Boundary Module
The next governance question becomes:
Which identified Scope components fall within, outside, partly within, or remain unresolved in relation to the established Liability?
The boundary is explicit:
LSCIM identifies what must be scoped.
LSCBM determines the governed Scope boundaries.
Minimum Implementation Framework
A conforming implementation of LSCIM must provide exactly the following eight capabilities:
Scope Identification Object & Determination Association
Capability to establish the specific Liability Determination being scoped and preserve its Attachment State, Determination identity, and relevant governed references.
Subject, Relationship, Object & Basis Identification
Capability to identify and associate the Liability Subject, Liability Relationship, Governed Liability Object, and Liability Basis relevant to the Scope inquiry.
Scope-Relevant Matter Identification
Capability to identify consequences, Harm states, losses, damages, obligations, activities, assets, resources, and other materially relevant matters requiring Scope assessment without presuming inclusion.
Scope Dimension Identification
Capability to identify materially relevant quantitative, qualitative, temporal, location, Subject, Relationship, Object, Basis, consequence, obligation, and other applicable Scope dimensions.
Scope Component Identity, Association & Dependency Governance
Capability to maintain distinct identities, associations, dependencies, overlaps, duplicates, and relationships among Scope-relevant components.
Unknown, Uncertain, Disputed & Incomplete Scope Identification Governance
Capability to preserve unresolved Scope-relevant components without converting uncertainty or missing information into inclusion or exclusion.
Scope Identification Change, Correction, Reassessment & Re-Entry
Capability to govern material changes, corrections, reassessments, historical states, and targeted upstream re-entry without historical erasure.
Scope Boundary Handoff Governance
Capability to produce an Identified Liability Scope Structure sufficiently complete, bounded, and traceable for Liability Scope Boundary governance.
Governance Logic
The canonical LSCIM governance logic is:
Governed Liability Determination State
↓
Confirm Determination Reference
↓
Identify Scope Inquiry
↓
Identify Liability Subject
↓
Identify Liability Relationship
↓
Identify Liability Object
↓
Identify Liability Basis
↓
Identify Scope-Relevant Matters
↓
Identify Consequences & Obligations
↓
Identify Scope Dimensions
↓
Identify Dependencies / Overlaps / Duplicates
↓
Preserve Unknown / Uncertain / Disputed Components
↓
Assess Identification Completeness & Sufficiency
↓
Identified Liability Scope Structure
↓
Handoff to Liability Scope Boundary Governance
Governance Outputs
LSCIM may produce:
Scope Identification Identity
Scope Determination Reference
Scope Subject Association
Scope Relationship Association
Scope Object Association
Scope Basis Association
Scope-Relevant Matter Set
Scope-Relevant Consequence Set
Scope-Relevant Harm Association
Scope-Relevant Loss Association
Scope-Relevant Damage Association
Scope-Relevant Obligation Set
Quantitative Scope Dimension Set
Qualitative Scope Dimension Set
Temporal Scope Dimension
Location Scope Dimension
Activity Scope Dimension
Asset / Resource Scope Dimension
Subject Scope Dimension
Relationship Scope Dimension
Basis Scope Dimension
Consequence Scope Dimension
Obligation Scope Dimension
Scope Component Dependency Record
Scope Component Overlap Record
Scope Component Duplicate Record
Scope Component Conflict Record
Unknown Scope Component State
Uncertain Scope Component State
Disputed Scope Component State
Scope Identification Sufficiency State
The principal output is:
Identified Liability Scope Structure
Critical Distinctions
LSCIM preserves the following distinctions:
Liability Attachment ≠ Liability Scope Scope-Relevant Matter ≠ Established Liability Liability Scope Identification without Determination Reference ≠ Governed Scope Identification One Event ≠ One Subject Scope Subject Identity ≠ Liability Relationship Identity Scope under Basis A ≠ Scope under Basis B by default Scope-Relevant Matter ≠ In-Scope Matter Consequence Identification ≠ Liability Scope Inclusion Governed Harm ≠ In-Scope Liability Harm by default Measured Loss ≠ Established Liability Scope Identified Quantity ≠ Governed Liability Amount Liability Scope ≠ Monetary Scope by default Shared Occurrence ≠ Shared Liability Scope One Matter under Multiple Bases ≠ One Universal Liability Scope Liability Scope ≠ Single-Dimension Boundary by default Similar Consequence ≠ Same Scope Component by default Overlapping Scope Components ≠ Independent Scope Components by default Multiple Records ≠ Multiple Liability Scope Components Unknown Scope Detail ≠ Absent Scope Component Uncertain Scope Component ≠ Included Scope Component Disputed Scope Component ≠ Excluded Scope Component by default Potential Scope Inclusion ≠ Governed Scope Inclusion Potential Exclusion ≠ Governed Exclusion Scope Identification Completeness ≠ Information Exhaustiveness Claimed Scope ≠ Governed Liability Scope Paid Amount ≠ Liability Scope Settlement Amount ≠ Liability Scope by default Insurance Limit ≠ Liability Scope Ability to Pay ≠ Liability Scope Harm Severity ≠ Liability Scope Causal Connection ≠ Scope Inclusion Responsibility Scope ≠ Liability Scope Accountability Scope ≠ Liability Scope One Subject ≠ One Universal Scope Inquiry Local Scope Inquiry ≠ Complete Liability Network Scope Scope Identification Correction ≠ Historical Erasure Scope Identification Reassessment ≠ Scope Identification Correction Current Scope Identification ≠ Complete Scope Identification History Identified Liability Scope Structure ≠ Governed Liability Scope
Cross-Architecture Boundary
LSCIM may identify governed objects originating from other OOF® architectures where they are materially relevant to Liability Scope assessment.
For example:
HAGA™ may provide governed Harm states.
ORA™ may provide Operational Reality.
AGA™ may provide Responsibility or Accountability states.
ADIT® may provide evidence-associated structures.
VALIDOS™ may provide validation states.
VFM® may provide governed Value Flow states.
OBIDENITY® may provide identity and ownership structures.
AIG® and ASGA™ may provide AI or autonomous-system states.
PGA™ may provide Prediction states.
SIMULOS® may provide Simulation outputs.
LSCIM does not absorb these objects into Liability governance.
It identifies only their potential relevance to the extent of an already established Liability.
The canonical interoperability principle is:
An externally governed object may become a Liability Scope-relevant component without becoming Liability Scope itself and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LSCIM begins with a:
Governed Liability Determination State
and governs identification of the components and dimensions that require Liability Scope Boundary governance.
LSCIM governs:
Scope Identification Object, Determination Association, Subject Association, Relationship Association, Object Association, Basis Association, Scope-Relevant Matters, Consequences, Obligations, Scope Dimensions, component identity, component association, dependencies, overlaps, duplicates, conflicts, unknowns, uncertainty, disputes, identification sufficiency, change, correction, reassessment, historical integrity, and boundary handoff.
LSCIM does not govern:
initial Liability Attachment, final Scope inclusion, final Scope exclusion, Scope Boundary determination, Liability Allocation, Liability State & Change, Transfer, Recourse, Resolution, Discharge, or Finality.
LSCIM ends when an:
Identified Liability Scope Structure
is sufficiently complete and traceable for Liability Scope Boundary governance.
Use Case 1 — Multi-Party Industrial Liability Scope
Identification
LDS establishes Attached Liability for an industrial operator following an operational incident.
The Determination does not by itself establish which resulting consequences fall within that Liability.
LSCIM identifies the relevant Scope inquiry and associates it with the operator, applicable Liability Relationship, Liability Object, and Liability Basis.
It then identifies potentially relevant:
equipment damage, production interruption, repair obligations, operational losses, relevant Harm states, and temporal dimensions.
LSCIM does not determine that all of these matters fall within Liability.
It produces an Identified Liability Scope Structure for LSCBM to establish the actual Scope boundaries.
Use Case 2 — Autonomous System Liability Scope
Identification
A governed Liability Determination establishes Attached Liability within a Relationship involving an autonomous system deployment.
Several consequences and obligations may be relevant, including system damage, operational interruption, corrective actions, and downstream effects.
LSCIM identifies each materially distinct Scope-relevant component and associates it with the correct Subject, Relationship, Object, Basis, and temporal context.
It also preserves unresolved components and prevents technical causation, Harm severity, insurance coverage, or claimed amounts from becoming Scope automatically.
The result provides LSCBM with the complete structured set of matters requiring explicit Scope Boundary governance.
Canonical Closing Statement
Once Liability attaches, the next question is not immediately how much Liability exists or how it should be distributed.
The first requirement is to identify exactly what must be scoped.
LSCIM establishes that governed starting structure by identifying the Subjects, Relationships, Objects, Bases, consequences, obligations, dimensions, dependencies, and unresolved matters relevant to the extent of established Liability.
It does not decide the boundary.
It makes the boundary determinable.
Attachment establishes Liability. Scope Identification establishes what must now be bounded.
Identify the Scope before drawing its boundaries.