LSCBM — Liability Scope Boundary Module
LSCBM — Liability Scope Boundary 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 Boundary
Module ID: LIGA-LSAS-LSCBM-001
Origin ID: OOF.CM.LIGA.08.02.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 Boundary Module (LSCBM) governs how the extent of established Liability is explicitly bounded after the relevant Scope components and dimensions have been identified.
LSCBM determines which identified Scope components fall within the established Liability, which fall outside it, which are only partly included, and which remain unresolved.
It converts the Identified Liability Scope Structure into a Governed Liability Scope while preserving the applicable Liability Determination, Subject, Relationship, Object, Basis, temporal context, limitations, exceptions, uncertainty, and historical state.
LSCBM does not determine whether Liability initially attaches.
It does not allocate Liability among Subjects or Relationships.
It governs the transition:
Identified Liability Scope Structure → Boundary Criteria → Component Boundary Assessment → Inclusion / Exclusion / Partial / Unresolved Classification → Boundary Integrity → Governed Liability Scope Its foundational distinction is:
Attached Liability ≠ Unlimited Liability.
Operational Role
The operational role of LSCBM is:
to establish where an existing Liability begins, where it ends, what it includes, what it excludes, and what remains unresolved.
LSCIM identifies what must be scoped.
LSCBM draws the governed boundary.
The module prevents established Liability from expanding automatically to every consequence, cost, Harm, obligation, loss, Claim, or related matter surrounding the same event.
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 LSCBM governs:
Liability Scope Boundary
Its principal input is:
Identified Liability Scope Structure
Its principal output is:
Governed Liability Scope
Its handoff is:
Governed Liability Scope → LALIM — Liability Allocation Identification Module
Central Operational Question
Which identified Scope components fall within, outside, partly within, or remain unresolved in relation to the established Liability, and where must the governed Liability boundary be drawn?
Boundary Preconditions
Before Scope Boundary governance proceeds, LSCBM should confirm that:
the applicable Liability Determination is identifiable, the relevant Subject is identifiable, the relevant Liability Relationship is identifiable, the Liability Object is identifiable, the applicable Liability Basis is identifiable, and the relevant Scope components have been sufficiently identified.
A Scope Boundary should not be created independently of this structure.
Boundary Object
Every Scope Boundary should relate to a defined Liability Scope inquiry.
The Boundary Object should remain traceable to:
the Governed Liability Determination State, the Liability Subject, the Liability Relationship, the Liability Object, the Liability Basis, and the relevant Scope dimensions.
Boundary Criteria
LSCBM should identify the criteria used to establish Scope boundaries.
Boundary criteria may arise from:
the applicable Liability Basis, the governed Determination, relevant Conditions, Liability Relationships, governed Connections, applicable authority, or another legitimate methodological source.
Boundary criteria should be explicit enough to permit reconstruction.
Criterion Applicability
A valid boundary criterion does not automatically apply to every Liability Scope inquiry.
Therefore:
Valid Boundary Criterion ≠ Applicable Boundary Criterion by default.
Applicability should be established for the specific governed Scope.
No Outcome-Driven Boundary
Boundary criteria should not be selected or changed merely to produce a preferred Scope.
Therefore:
Desired Scope Outcome ≠ Scope Boundary Criterion.
Component Boundary Assessment
Each materially relevant Scope component should be assessed against the applicable boundary criteria.
The result should identify whether the component is:
Included
Excluded
Partially Included
or:
Unresolved
where a complete boundary cannot yet be established.
Included Scope
An Included Scope component falls within the established Liability under the applicable governed structure.
Its inclusion should remain traceable to the relevant boundary criteria.
Therefore:
Related Matter ≠ Included Liability Scope by default.
Excluded Scope
An Excluded Scope component falls outside the established Liability within the defined Scope inquiry.
Exclusion should remain bounded to the applicable:
Determination, Subject, Relationship, Object, Basis, and Scope.
Therefore:
Excluded from One Liability Scope ≠ Excluded from All Liability.
Partially Included Scope
A Scope component may be only partly included.
The included and excluded portions should be distinguishable where materially necessary.
Therefore:
Partial Inclusion ≠ Complete Inclusion.
Unresolved Scope
Where a Scope boundary cannot yet be sufficiently established, the component should remain unresolved.
Unresolved states may include:
Pending
Unknown
Uncertain
Disputed
LSCBM should not force unresolved components into Included or Excluded states merely to complete the Scope.
Pending Scope
A Scope component is Pending where a material dependency must be resolved before its boundary can be completed.
Therefore:
Pending Scope ≠ Excluded Scope.
Unknown Scope
Unknown means the available governed structure cannot establish whether the component falls within Liability Scope.
Therefore:
Unknown Scope ≠ Excluded Scope.
Uncertain Scope
Uncertain means the component can be assessed only with material unresolved uncertainty.
Therefore:
Uncertain Scope ≠ Included or Excluded Scope by default.
Disputed Scope
Disputed means materially competing governed positions exist concerning the boundary.
The dispute should remain visible.
Therefore:
Disputed Scope ≠ Authority to Select a Preferred Boundary.
Subject Boundary
Scope boundaries should remain Subject-specific where necessary.
A consequence may fall within the Liability Scope of Subject A while falling outside the Liability Scope of Subject B.
Therefore:
Shared Consequence ≠ Shared Liability Scope.
Relationship Boundary
A Scope component may fall within Liability through one Relationship but not another.
Therefore:
In-Scope under Relationship A ≠ In-Scope under Relationship B.
Object Boundary
The Liability Scope should remain bounded to the relevant Governed Liability Object.
A related but distinct Object should not be included merely because it is operationally connected.
Basis Boundary
A Scope component may be included under one Liability Basis and excluded under another.
Therefore:
In-Scope under Basis A ≠ In-Scope under Basis B.
Temporal Boundary
LSCBM should establish temporal boundaries where time materially affects Scope.
These may include:
Scope start, Scope end, covered period, excluded period, continuing period, or unresolved temporal extent.
Retrospective Scope
A later Scope determination may establish that Liability covered an earlier period.
The system should distinguish:
when Scope was determined, from:
the period to which that Scope applies.
Therefore:
Scope Determination Time ≠ Scope-Effective Time by default.
Continuing Scope
Some Liability may continue across time.
Where the end boundary is not yet established, LSCBM should represent the Scope as continuing rather than inventing an artificial endpoint.
Geographic Boundary
Where location materially affects Liability Scope, the relevant geographic or jurisdiction-relevant boundary should be explicit.
LSCBM represents the governed boundary without independently determining jurisdiction-specific law.
Activity Boundary
Where Liability applies only to particular activities, operations, services, transactions, or conduct, those boundaries should remain explicit.
Asset and Resource Boundary
Where Liability relates to specific assets, systems, property, data, infrastructure, or resources, the Scope should distinguish covered from non-covered objects.
Consequence Boundary
Not every consequence associated with an occurrence necessarily falls within Liability Scope.
Each materially distinct consequence should be assessed under the applicable boundary criteria.
Therefore:
Occurrence Consequence ≠ Liability Scope Consequence by default.
Harm Boundary
Where governed Harm is relevant, LSCBM determines only whether the relevant Harm state or consequence falls within the established Liability Scope.
HAGA™ continues to govern Harm itself.
Therefore:
Established Harm ≠ In-Scope Liability Harm by default.
Loss Boundary
A measured or documented loss may still fall outside the Liability Scope.
Therefore:
Established Loss ≠ In-Scope Liability Loss by default.
Damage Boundary
Damage associated with an event does not automatically fall within every resulting Liability Relationship.
Therefore:
Established Damage ≠ In-Scope Liability Damage by default.
Cost Boundary
Costs may be:
Included, Excluded, Partially Included, or Unresolved.
The fact that a cost was incurred does not establish its Liability Scope status.
Therefore:
Incurred Cost ≠ In-Scope Liability Cost by default.
Obligation Boundary
Where Liability involves performance or another obligation, LSCBM should determine the boundary of that obligation.
The boundary may concern:
what must be performed, to what extent, for what period, for which Object, or under which Relationship.
Quantitative Boundary
Where Scope has a quantitative dimension, LSCBM may establish the covered extent.
This may concern:
amount, quantity, percentage, units, duration, or another measurable dimension.
Quantification should remain traceable to the governing Scope criteria.
Qualitative Boundary
Scope may also require qualitative boundary governance.
Examples may include:
types of repair, categories of restoration, classes of obligation, permitted or prohibited activities, or defined performance states.
Multi-Dimensional Boundary
A Scope boundary may depend on several dimensions simultaneously.
For example:
Subject + Relationship + Basis + Consequence + Time
may collectively define whether a matter is included.
Therefore:
Scope Boundary ≠ Single-Dimension Decision by default.
Boundary Interaction
Where several Scope dimensions interact, LSCBM should preserve those interactions rather than evaluate each dimension as completely independent.
A temporal limitation may affect a consequence boundary.
A Basis limitation may affect an obligation boundary.
A Relationship boundary may affect a Subject-specific Scope.
Boundary Limitation
A Scope may contain explicit limitations.
A limitation narrows or conditions an otherwise applicable Scope.
The limitation should remain traceable to its governed source.
Boundary Exception
An applicable exception may remove or modify a portion of otherwise included Scope.
Therefore:
Scope Exception ≠ Absence of Liability.
The Liability may remain established while its Scope is narrowed.
Limitation vs Exclusion
A limitation constrains Scope.
An exclusion places a defined matter outside Scope.
These should remain distinguishable.
Therefore:
Scope Limitation ≠ Scope Exclusion.
Exception vs Exclusion
An exception may alter the application of an otherwise relevant boundary rule.
An exclusion represents the resulting outside-Scope state.
Therefore:
Scope Exception ≠ Scope Exclusion by default.
Boundary Dependency
A Scope Boundary may depend on another governed state.
Where dependency exists, it should be explicit.
A boundary should not be represented as final where a material dependency remains unresolved.
Boundary Overlap
Different Scope components may overlap.
LSCBM should identify and govern overlap so that the same matter is not unintentionally represented multiple times within Scope.
Therefore:
Scope Overlap ≠ Additional Liability Scope by default.
Boundary Duplication
Duplicate representations should not expand Scope.
Therefore:
Duplicate Scope Records ≠ Multiple Liability Scope.
Boundary Conflict
Where two governed boundary assessments conflict, LSCBM should preserve the conflict until legitimately resolved.
Therefore:
Conflicting Scope Boundaries ≠ Authority to Average Boundaries.
Boundary Hierarchy
Where boundary criteria possess a legitimate hierarchy, that hierarchy should be explicit.
LSCBM should not invent hierarchy merely to resolve conflicting criteria.
Boundary Priority
Where one boundary rule legitimately takes precedence over another, the source and reason for priority should remain traceable.
Therefore:
Boundary Priority ≠ Evaluator Preference.
Scope Expansion
An established Scope may later expand where a legitimate governance change supports additional inclusion.
Expansion should be explicit and traceable.
Therefore:
Scope Expansion ≠ Original Scope Rewrite.
Scope Contraction
An established Scope may later contract where a legitimate governance change supports exclusion or reduction.
Earlier Scope states should remain reconstructable.
Therefore:
Scope Contraction ≠ Historical Erasure.
Scope Change Trigger
Scope reassessment may be triggered by:
new governed information, changed consequences, changed Liability Determination, changed Basis applicability, changed Relationship state, resolved uncertainty, correction, or another materially relevant governance event.
Scope Correction
A Scope Boundary may be corrected where the earlier boundary was incorrectly established or represented.
Therefore:
Scope Correction ≠ Scope Reassessment.
Correction addresses error.
Reassessment addresses materially changed governance circumstances or information.
Scope Version Continuity
Material Scope changes should remain historically traceable.
The current Scope should not silently replace earlier governed states.
Therefore:
Current Liability Scope ≠ Complete Liability Scope History.
Boundary Provenance
Each material Scope Boundary should preserve sufficient provenance to identify:
its source, criteria, relevant Determination, authority where applicable, time, and material supporting governed inputs.
Boundary Traceability
A qualified reviewer should be able to trace an Included, Excluded, Partial, or Unresolved Scope state back to the relevant:
Liability Determination, Subject, Relationship, Object, Basis, Scope component, and boundary criteria.
Boundary Explainability
The reason a component falls inside or outside Liability Scope should be explainable through the governed structure.
Therefore:
Boundary Label ≠ Boundary Rationale.
Boundary Sufficiency
A Scope Boundary is sufficiently governed when:
the Scope Object is explicit, the relevant Subject and Relationship are known, the applicable Basis is explicit, the Scope component is identifiable, the applicable criteria are known, the resulting Scope state is explicit, material uncertainty or dispute is preserved, and the result is traceable.
Scope Completeness
A Governed Liability Scope is complete when all materially relevant identified components possess an explicit boundary state or an explicit unresolved state.
Completeness does not require all components to be finally resolved.
Therefore:
Scope Completeness ≠ Universal Boundary Finality.
Scope and Liability Determination
LSCBM must not reopen the Attachment Determination merely because a Scope is narrow.
Likewise, broad consequences should not be used to broaden the underlying Attachment.
Therefore:
Scope Boundary ≠ Liability Attachment Determination.
Scope and Allocation
LSCBM determines what Liability covers.
It does not determine how the established Scope is distributed among Subjects or Relationships.
Therefore:
Governed Liability Scope ≠ Liability Allocation.
Scope and Payment
Payment does not define Scope.
Therefore:
Paid Matter ≠ In-Scope Matter by default.
A payment may occur for reasons distinct from the substantive Liability Scope.
Scope and Claims
A Claim may define what a claimant seeks.
It does not define the governed Liability Scope.
Therefore:
Claim Boundary ≠ Liability Scope Boundary.
Scope and Settlement
A settlement may define negotiated obligations.
It should not automatically be treated as the substantive Liability Scope.
Therefore:
Settlement Boundary ≠ Liability Scope Boundary by default.
Scope and Insurance
Insurance coverage boundaries may differ from underlying Liability boundaries.
Therefore:
Insurance Coverage Boundary ≠ Liability Scope Boundary.
Scope and Responsibility
The extent of operational responsibility does not automatically establish the extent of Liability.
Therefore:
Responsibility Boundary ≠ Liability Scope Boundary.
Scope and Accountability
Accountability structures do not automatically define Liability boundaries.
Therefore:
Accountability Boundary ≠ Liability Scope Boundary.
Scope and Causation
A causal chain may extend further than the Liability Scope or may be governed differently.
Therefore:
Causal Boundary ≠ Liability Scope Boundary by default.
Scope and Harm
Harm may continue beyond the extent of a particular Liability Scope.
Likewise, a Liability Scope may include obligations not reducible to Harm.
Therefore:
Harm Boundary ≠ Liability Scope Boundary.
Scope and Economic Burden
The ultimate economic burden may differ from the substantive Liability Scope because of:
insurance, indemnification, transfer, recourse, payment, or other downstream structures.
Therefore:
Economic Burden Boundary ≠ Liability Scope Boundary.
Multi-Subject Boundary Governance
Where several Subjects have Attached Liability, each Subject's Scope should be bounded independently where materially necessary.
The existence of shared consequences does not require identical boundaries.
Multi-Relationship Boundary Governance
A Subject participating in multiple Liability Relationships may possess different Scope boundaries under each Relationship.
Therefore:
One Subject ≠ One Universal Liability Scope.
Multi-Basis Boundary Governance
Where Liability attaches under several Bases, Scope should remain Basis-specific where necessary.
Different Bases may produce overlapping, narrower, broader, or otherwise different Scope structures.
Liability Network Boundary Governance
A Liability Network may contain several Governed Liability Scopes.
LSCBM should preserve both:
local Scope boundaries, and their relationship to the wider network.
Therefore:
Local Liability Scope ≠ Complete Liability Network Scope.
Network Overlap
Different Liability Relationships may contain overlapping Scope.
Overlap does not automatically mean duplicate Liability or duplicate economic burden.
The overlap should remain explicit for later Allocation and Reconciliation governance.
Re-Entry to Scope Identification
Where boundary governance reveals that a materially necessary Scope component was not identified, LSCBM should return the matter to LSCIM.
Therefore:
Missing Scope Component ≠ Boundary Exclusion.
Re-Entry to Liability Determination
Where boundary governance reveals a defect in the underlying Liability Determination, the matter should return to LDS.
LSCBM must not compensate for an invalid Attachment Determination by manipulating Scope.
Earlier Lifecycle Re-Entry
Where the defect originates in an earlier LIGA™ governance space, the matter should return to the earliest materially affected governance space.
The governing rule remains:
Re-enter the earliest materially affected governance space.
Historical Integrity
Scope Boundary history should preserve materially relevant prior states.
A later boundary may supersede an earlier one without deleting it.
Therefore:
Superseded Scope Boundary ≠ Deleted Scope Boundary.
Governed Liability Scope
The principal output of LSCBM is:
Governed Liability Scope
It should identify, where applicable:
Scope identity, Determination reference, Subject, Relationship, Object, Basis, included components, excluded components, partially included components, unresolved components, temporal boundaries, quantitative boundaries, qualitative boundaries, limitations, exceptions, uncertainty, disputes, authority, time, and provenance.
Meaning of the Output
A Governed Liability Scope means the extent of established Liability has been sufficiently bounded for Allocation governance.
It does not mean the Liability has already been distributed among Subjects or Relationships.
Therefore:
Governed Liability Scope ≠ Governed Liability Allocation.
Handoff to Liability Allocation Identification
LSCBM hands the:
Governed Liability Scope
to:
LALIM — Liability Allocation Identification Module
The next governance question becomes:
Does this Governed Liability Scope require Allocation, and which Subjects, Relationships, portions, layers, or other Liability structures must participate in that Allocation?
The boundary is explicit:
LSCIM identifies what must be scoped.
LSCBM establishes the Scope boundary.
LALIM identifies what must be allocated.
Minimum Implementation Framework
A conforming implementation of LSCBM must provide exactly the following eight capabilities:
Scope Boundary Object & Criterion Governance
Capability to establish the Scope Boundary Object, associate it with the relevant Liability Determination, Subject, Relationship, Object, and Basis, and identify applicable boundary criteria.
Inclusion, Exclusion, Partial & Unresolved Boundary Governance
Capability to classify identified Scope components as Included, Excluded, Partially Included, Pending, Unknown, Uncertain, Disputed, or another legitimately defined Scope state.
Multi-Dimensional Scope Boundary Governance
Capability to establish Subject, Relationship, Object, Basis, temporal, geographic, activity, consequence, obligation, quantitative, qualitative, and other materially relevant Scope boundaries.
Limitation, Exception, Dependency & Priority Governance
Capability to govern Scope limitations, exceptions, dependencies, legitimate criterion hierarchy, and boundary priority without outcome-driven manipulation.
Overlap, Duplication, Conflict & Network Boundary Governance
Capability to identify and preserve overlapping, duplicate, conflicting, multi-Subject, multi-Relationship, multi-Basis, and Liability Network Scope structures.
Boundary Traceability, Explainability & Sufficiency Governance
Capability to ensure every material Scope state remains traceable, explainable, sufficiently governed, and reconstructable from the applicable Liability structure.
Scope Change, Correction, Reassessment & Re-Entry Governance
Capability to govern Scope expansion, contraction, correction, reassessment, historical states, and targeted lifecycle reentry without historical erasure.
Allocation Identification Handoff Governance
Capability to produce a Governed Liability Scope sufficiently explicit, bounded, traceable, and historically coherent for Liability Allocation Identification.
Governance Logic
The canonical LSCBM governance logic is:
Identified Liability Scope Structure
↓
Confirm Scope Boundary Object
↓
Identify Applicable Boundary Criteria
↓
Assess Criterion Applicability
↓
Assess Each Scope Component
↓
Determine Included / Excluded / Partial / Unresolved State
↓
Establish Multi-Dimensional Boundaries
↓
Apply Legitimate Limitations / Exceptions
↓
Preserve Dependencies / Overlaps / Conflicts
↓
Assess Boundary Traceability
↓
Assess Boundary Sufficiency
↓
Preserve Change & Historical State
↓
Governed Liability Scope
↓
Handoff to Liability Allocation Identification
Governance Outputs
LSCBM may produce:
Liability Scope Identity
Scope Boundary Identity
Boundary Criterion Set
Criterion Applicability State
Included Scope Component Set
Excluded Scope Component Set
Partially Included Scope Component Set
Pending Scope State
Unknown Scope State
Uncertain Scope State
Disputed Scope State
Subject Scope Boundary
Relationship Scope Boundary
Object Scope Boundary
Basis Scope Boundary
Temporal Scope Boundary
Geographic Scope Boundary
Activity Scope Boundary
Asset / Resource Scope Boundary
Consequence Scope Boundary
Harm-Relevant Liability Scope Boundary
Loss Scope Boundary
Damage Scope Boundary
Cost Scope Boundary
Obligation Scope Boundary
Quantitative Scope Boundary
Qualitative Scope Boundary
Scope Limitation Record
Scope Exception Record
Boundary Dependency Record
Boundary Overlap Record
Boundary Conflict Record
Scope Change Record
Historical Scope Boundary Record
The principal output is:
Governed Liability Scope
Critical Distinctions
LSCBM preserves the following distinctions:
Attached Liability ≠ Unlimited Liability Valid Boundary Criterion ≠ Applicable Boundary Criterion by default Desired Scope Outcome ≠ Scope Boundary Criterion Related Matter ≠ Included Liability Scope by default Excluded from One Liability Scope ≠ Excluded from All Liability Partial Inclusion ≠ Complete Inclusion Pending Scope ≠ Excluded Scope Unknown Scope ≠ Excluded Scope Uncertain Scope ≠ Included or Excluded Scope by default Disputed Scope ≠ Authority to Select a Preferred Boundary Shared Consequence ≠ Shared Liability Scope In-Scope under Relationship A ≠ In-Scope under Relationship B In-Scope under Basis A ≠ In-Scope under Basis B Scope Determination Time ≠ Scope-Effective Time by default Occurrence Consequence ≠ Liability Scope Consequence by default Established Harm ≠ In-Scope Liability Harm by default Established Loss ≠ In-Scope Liability Loss by default Established Damage ≠ In-Scope Liability Damage by default Incurred Cost ≠ In-Scope Liability Cost by default Scope Boundary ≠ Single-Dimension Decision by default Scope Exception ≠ Absence of Liability Scope Limitation ≠ Scope Exclusion Scope Exception ≠ Scope Exclusion by default Scope Overlap ≠ Additional Liability Scope by default Duplicate Scope Records ≠ Multiple Liability Scope Conflicting Scope Boundaries ≠ Authority to Average Boundaries Boundary Priority ≠ Evaluator Preference Scope Expansion ≠ Original Scope Rewrite Scope Contraction ≠ Historical Erasure Scope Correction ≠ Scope Reassessment Current Liability Scope ≠ Complete Liability Scope History Boundary Label ≠ Boundary Rationale Scope Completeness ≠ Universal Boundary Finality Scope Boundary ≠ Liability Attachment Determination Governed Liability Scope ≠ Liability Allocation Paid Matter ≠ In-Scope Matter by default Claim Boundary ≠ Liability Scope Boundary Settlement Boundary ≠ Liability Scope Boundary by default Insurance Coverage Boundary ≠ Liability Scope Boundary Responsibility Boundary ≠ Liability Scope Boundary Accountability Boundary ≠ Liability Scope Boundary Causal Boundary ≠ Liability Scope Boundary by default Harm Boundary ≠ Liability Scope Boundary Economic Burden Boundary ≠ Liability Scope Boundary One Subject ≠ One Universal Liability Scope Local Liability Scope ≠ Complete Liability Network Scope Missing Scope Component ≠ Boundary Exclusion Superseded Scope Boundary ≠ Deleted Scope Boundary Governed Liability Scope ≠ Governed Liability Allocation
Cross-Architecture Boundary
LSCBM may use governed states originating from other OOF® architectures where those states are relevant to Liability Scope Boundary governance.
For example:
HAGA™ governs Harm boundaries and states.
ORA™ governs Operational Reality.
AGA™ governs Responsibility and Accountability.
ADIT® governs evidence and auditability.
VALIDOS™ governs validation.
VFM® governs Value Flow.
OBIDENITY® governs identity and origin-bound structures.
AIG® and ASGA™ govern AI and autonomous-system states.
PGA™ governs Prediction.
SIMULOS® governs Simulation.
LSCBM does not redefine the boundaries of those external governance objects.
It determines only whether and to what extent those governed objects or their consequences fall within an established Liability Scope.
The canonical interoperability principle is:
An external governance boundary may inform a Liability Scope Boundary without becoming that Liability Scope Boundary and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LSCBM begins with an:
Identified Liability Scope Structure
and governs the explicit boundaries of established Liability.
LSCBM governs:
Boundary Object, Boundary Criteria, Criterion Applicability, Inclusion, Exclusion, Partial Inclusion, Unresolved Scope, Subject Boundaries, Relationship Boundaries, Object Boundaries, Basis Boundaries, Temporal Boundaries, Location Boundaries, Activity Boundaries, Consequence Boundaries, Obligation Boundaries, Quantitative and Qualitative Boundaries, Limitations, Exceptions, Dependencies, Overlap, Duplication, Conflict, Priority, Scope Change, Correction, Reassessment, Traceability, Historical Integrity, and Allocation Identification handoff.
LSCBM does not govern:
initial Liability Attachment, Scope component identification as its primary function, Liability Allocation, Liability State & Change, Transfer, Recourse, Resolution, Discharge, or Finality.
LSCBM ends when a:
Governed Liability Scope
is sufficiently explicit and bounded for Liability Allocation Identification.
Use Case 1 — Industrial Incident Scope Boundary
LDS establishes Attached Liability for an industrial operator.
LSCIM identifies equipment damage, production interruption, repair obligations, operational losses, and relevant Harm states as Scope-relevant components.
LSCBM evaluates those components against the applicable Liability Basis and Scope criteria.
It may determine that:
equipment repair is Included, a defined portion of production interruption is Included, an unrelated downstream commercial loss is Excluded, one continuing Harm-related consequence is Partially Included, and another claimed cost remains Disputed.
The resulting Governed Liability Scope establishes the extent of the operator's Liability without yet determining how that Scope should be allocated among any additional Liability Relationships.
Use Case 2 — Autonomous System Scope Boundary
An autonomous system deployment produces an Attached Liability Determination involving a service provider.
LSCIM identifies several potential Scope components, including system restoration, operational interruption, downstream damage, corrective action, and continuing effects.
LSCBM establishes the governed boundary for each component.
It preserves different temporal boundaries, distinguishes direct and unrelated consequences, records unresolved components, and prevents insurance coverage limits or claimed amounts from defining the Liability Scope.
The result is a Governed Liability Scope ready for Allocation Identification.
Canonical Closing Statement
Established Liability requires a boundary.
Without that boundary, Attachment can be mistaken for unlimited responsibility for every consequence surrounding the same event.
LSCBM prevents that expansion.
It establishes what falls within Liability, what falls outside it, what is only partly included, and what remains unresolved while preserving the applicable Subject, Relationship, Object, Basis, time, limitations, uncertainty, and history.
It does not allocate Liability.
It makes Allocation possible by first establishing what Liability actually covers.
Attachment establishes Liability. Boundary establishes its governed extent.
Draw the Scope boundary before distributing the Liability within it.