Liability Scope & Allocation Standard (LSAS)
Liability Scope & Allocation Standard (LSAS)
Architecture: LIGA™ — Liability Governance Architecture
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Parent Standard
Governed Space: Liability Scope & Allocation
Standard ID: LIGA-LSAS-001
Origin ID: OOF.PS.LIGA.08.00.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 & Allocation Standard (LSAS) governs how established Liability is bounded in extent and distributed across relevant Liability Subjects and Liability Relationships after Liability has been determined to attach.
LSAS determines what an established Liability applies to, what it does not apply to, how far that Liability extends within the governed Liability Object and applicable Liability Basis, and how the resulting Liability structure is allocated where more than one Liability Subject or Liability Relationship participates.
It transforms a Governed Liability Determination State into an explicit Governed Liability Scope & Allocation Structure suitable for ongoing Liability State & Change governance.
LSAS does not determine whether Liability initially attaches.
It begins only after a sufficient Liability Determination exists.
Operational Role
The operational role of LSAS is to answer two separate but connected governance questions:
What is the extent of the established Liability?
and:
How is that established Liability distributed across the relevant Liability structure?
These questions must remain separate from the earlier question:
Does Liability exist?
The canonical distinction is:
Liability Determination → Liability Scope → Liability Allocation These are not interchangeable governance operations.
Core Question
For what and to what extent does established Liability apply, and how is that Liability distributed where multiple Liability relationships exist?
Position in the LIGA™ Governance Flow
The canonical LIGA™ Governance Flow is:
Liability Context → Liability Object → Liability Basis → Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Scope & Allocation → Liability State & Change → Liability Transfer & Recourse → Liability Resolution & Discharge → Liability Continuity & Finality LSAS governs the eighth governance space:
Liability Scope & Allocation
Its principal input is:
Governed Liability Determination State
Its principal output is:
Governed Liability Scope & Allocation Structure
The downstream handoff is:
Governed Liability Scope & Allocation Structure → Liability State & Change Governance
Determination Before Scope
LSAS must not establish Liability merely by defining its potential extent.
The existence of:
Harm, loss, damage, cost, an obligation, a Claim, a payment, or a measurable consequence does not itself establish the scope of Liability unless Liability has first been governed through LDS.
Therefore:
Potential Liability Scope ≠ Established Liability Scope.
Liability Scope
Liability Scope defines the governed extent of an established Liability.
Scope asks:
What does this Liability actually cover?
The answer may depend upon the applicable:
Liability Determination, Liability Basis, Liability Object, Subject, Relationship, Conditions, Connection, time, and other governed boundaries.
Scope Object
Every Liability Scope should remain associated with the Liability Determination from which it derives.
Scope must not become detached from its Determination origin.
Therefore:
Liability Scope without Determination Reference ≠ Fully Governed Liability Scope.
Scope Boundary
LSAS should establish explicit boundaries around the extent of Liability.
A Scope Boundary may distinguish:
included matters, excluded matters, partially included matters, unresolved matters, and matters requiring separate determination.
The purpose is to prevent Attached Liability from expanding automatically beyond what the governed Determination supports.
Included Scope
Included Scope identifies matters falling within the established Liability.
An included matter should possess a sufficient relationship to the applicable Determination and Liability Basis.
Excluded Scope
Excluded Scope identifies matters that fall outside the established Liability.
Exclusion from one Liability Scope does not necessarily mean the matter cannot fall within another Liability Determination.
Therefore:
Excluded from Scope A ≠ Excluded from all Liability.
Partial Scope
A matter may fall only partly within an established Liability.
LSAS should preserve partial inclusion without forcing the entire matter into or out of scope.
Therefore:
Partial Scope ≠ Complete Scope.
Unresolved Scope
A material scope question may remain:
Pending, Unknown, Uncertain, or Disputed.
LSAS should preserve that state explicitly rather than manufacture a boundary.
Scope Dimensions
Liability Scope may require governance across several dimensions.
Depending on the applicable Liability structure, these may include:
subject, object, relationship, consequence, obligation, activity, time, location, value, quantity, category, or another materially relevant dimension.
LSAS does not impose one universal scope model.
Subject Scope
Liability may apply differently to different Subjects.
Therefore:
Attached Liability involving multiple Subjects ≠ Identical Liability Scope for every Subject.
Relationship Scope
A Subject may bear Liability through one Liability Relationship without the same Liability extending through another Relationship.
Therefore:
Subject Liability ≠ Universal Relationship Scope.
Object Scope
The Liability Scope should preserve which part of the Governed Liability Object is covered by the established Liability.
Where several Objects exist, their scopes should remain distinguishable.
Basis Scope
Scope should remain associated with the Liability Basis under which Attachment was established.
A Liability attached under one Basis should not automatically acquire the scope of another Basis.
Therefore:
Attachment under Basis A ≠ Scope under Basis B.
Temporal Scope
Liability may apply only within a defined period or across specific lifecycle moments.
LSAS should preserve:
scope start, scope end where known, relevant historical periods, and unresolved temporal boundaries.
Geographic or Jurisdiction-Relevant Scope
Where location or jurisdiction is materially relevant, LSAS may represent the applicable governed scope boundaries.
It does not itself determine jurisdiction-specific law.
Consequence Scope
Where Liability relates to consequences, LSAS should identify which consequences fall within the established Liability structure.
The existence of a consequence does not automatically place it inside the Liability Scope.
Therefore:
Consequence ≠ In-Scope Consequence by default.
Harm Scope
Where governed Harm from HAGA™ is relevant, LSAS may determine which Harm states fall within the established Liability Scope.
HAGA™ retains governance of Harm itself.
Therefore:
Harm Scope ≠ Liability Scope by default.
Loss and Damage Scope
Loss or damage may be relevant to Liability Scope where the applicable Basis requires it.
Their existence or measurement does not independently establish that they fall within Liability.
Therefore:
Measured Loss ≠ In-Scope Liability Loss by default.
Obligation Scope
Where Liability produces or relates to obligations, LSAS may establish which obligations fall within the governed Liability Scope.
The existence of an obligation does not by itself determine the complete Liability structure.
Quantitative Scope
Where the applicable methodology permits quantitative representation, Scope may include:
amount, quantity, percentage, duration, units, or another measurable extent.
Quantification should remain traceable to the applicable Liability Determination and scope methodology.
Qualitative Scope
Not all Liability Scope is monetary or numerical.
Scope may concern:
performance, repair, restoration, correction, restriction, responsibility for an object or process, or another non-quantitative extent.
Therefore:
Liability Scope ≠ Monetary Amount by default.
Scope Limitation
A Liability Scope may contain explicit limitations.
Limitations should preserve:
their origin, applicability, effect, time, and relationship to the Liability Basis.
Scope Exception
An applicable exception may remove or modify part of an otherwise established Scope.
Exception governance should not be used to silently rewrite the original Liability Determination.
Scope Uncertainty
Where the extent of Liability remains uncertain, the uncertainty should remain explicit.
Therefore:
Attached Liability ≠ Fully Known Liability Scope.
Liability may be established before its complete extent is known.
Scope Change
Liability Scope may change when:
new governed information appears, the underlying state changes, the Determination changes, a relevant consequence develops, a scope boundary is corrected, or another legitimate governance event occurs.
Scope change should remain traceable.
Scope Correction
An incorrect Scope may be corrected.
Correction should preserve the earlier Scope state and the reason for change.
Therefore:
Scope Correction ≠ Historical Erasure.
Scope Reassessment
Scope may be reassessed because circumstances or governed inputs changed.
Therefore:
Scope Reassessment ≠ Scope Correction.
Scope History
The current Liability Scope may differ from earlier Scope states.
Therefore:
Current Liability Scope ≠ Complete Liability Scope History.
From Scope to Allocation
Scope establishes the extent of Liability.
Allocation governs how that established Liability is distributed.
The canonical sequence is:
Attached Liability → Liability Scope → Liability Allocation Therefore:
Liability Scope ≠ Liability Allocation.
Liability Allocation
Liability Allocation governs the distribution of established Liability across relevant Liability Subjects or Liability Relationships.
Allocation should operate only upon sufficiently established Liability and sufficiently governed Scope.
Allocation Object
Every Allocation should identify what governed Liability is being allocated.
The Allocation Object should remain traceable to:
the Liability Determination, Liability Scope, Subject structure, Relationship structure, and applicable Liability Basis.
Allocation Subject
LSAS should explicitly identify each Subject participating in the Allocation structure.
Participation in the same incident does not automatically justify participation in the same Allocation.
Therefore:
Event Participant ≠ Allocation Subject by default.
Allocation Relationship
Allocation should preserve the Liability Relationship through which the allocated Liability exists.
Therefore:
Allocation to Subject ≠ Allocation across every Relationship of that Subject.
Allocation Basis
The reason for distributing Liability in a particular manner should be explicit.
Allocation should not arise merely from convenience, ability to pay, visibility, insurance status, or institutional power.
Allocation Method
Where Liability must be distributed, the applicable Allocation Method should be explicit.
Depending on the governed structure, Allocation may be:
individual, shared, proportional, several, layered, conditional, sequential, or another legitimate form.
LSAS does not impose one universal Allocation method.
Individual Allocation
Individual Allocation assigns a governed portion or responsibility to a particular Liability Subject or Relationship.
The Allocation should remain bounded to the relevant Scope.
Shared Allocation
More than one Subject may participate in the same governed Liability Scope.
Shared Allocation should preserve the distinct relationships and basis for each Subject's participation.
Therefore:
Shared Liability ≠ Identical Liability.
Proportional Allocation
Where the applicable methodology permits proportional Allocation, LSAS may represent the governed distribution through percentages, fractions, units, or another proportional structure.
The proportion should be derived through an explicit method.
Therefore:
Percentage Allocation ≠ Liability Determination.
Non-Proportional Allocation
Liability may be allocated through structures that are not proportional.
LSAS should therefore not assume that every multi-party Liability structure can or should sum to a simple percentage distribution.
Layered Allocation
A Liability Network may contain multiple layers.
For example:
primary Liability, secondary Liability, conditional Liability, or another structurally distinct Liability relationship.
LSAS should preserve those layers.
It should not collapse them into one flat distribution.
Primary Liability and Allocation
Primary Liability may be scoped and allocated before later Transfer or Recourse governance occurs.
Therefore:
Primary Liability Allocation ≠ Final Economic Burden.
A different Subject may ultimately pay or recover part of the Liability downstream.
Paying Party
The Subject who ultimately performs payment or another obligation may differ from the Subject to whom Liability was allocated.
Therefore:
Liability-Bearing Party ≠ Paying Party.
This distinction must remain visible.
Insurance
Insurance may affect downstream payment, transfer, sharing, or recourse structures.
It should not automatically rewrite the underlying Liability Allocation.
Therefore:
Insurance Coverage ≠ Liability Allocation by default.
Indemnification
An indemnification relationship may affect downstream economic distribution without necessarily changing the original Liability Allocation.
Therefore:
Indemnification ≠ Original Liability Allocation.
Recourse
Recourse belongs primarily to LTRS.
LSAS may preserve Allocation information required for later Recourse governance but should not perform Recourse itself.
Therefore:
Liability Allocation ≠ Recourse Allocation.
Allocation Network
A complex matter may create a network of distinct Allocations rather than one distribution.
For example:
one Liability Determination may generate several scoped Liability Relationships, each of which may contain separate Allocation structures.
Therefore:
One Event ≠ One Allocation Structure.
Local Allocation
An Allocation concerning one Liability Relationship should not be treated as the Allocation for the entire Liability Network.
Therefore:
Local Liability Allocation ≠ Liability Network Allocation.
Allocation Completeness
An Allocation is complete when all materially necessary portions of the governed Scope have been assigned or explicitly represented as unresolved.
Completeness does not require artificial allocation of unknown portions.
Unallocated Liability
Part of an established Liability Scope may remain unallocated.
This may occur because Allocation is:
Pending, Unknown, Uncertain, Disputed, or dependent upon another governance process.
Therefore:
Unallocated Liability ≠ Nonexistent Liability.
Over-Allocation
LSAS should prevent the same Liability portion from being allocated more than intended unless the applicable Liability structure explicitly permits overlapping obligations.
Therefore:
Multiple Allocations ≠ Multiple Independent Liability Amounts by default.
Under-Allocation
Where the governed Scope exceeds the total represented Allocation, the unallocated portion should remain visible.
It should not disappear merely because current Allocation is incomplete.
Allocation Reconciliation
Where several Allocation records overlap, conflict, or interact, LSAS should reconcile them against the governed Liability Scope.
Reconciliation should preserve the distinction between:
scope, allocation, transfer, payment, and recourse.
Allocation Conflict
Different governed processes may produce conflicting Allocation structures.
The conflict should remain explicit.
Therefore:
Allocation Conflict ≠ Authority to Average the Results.
Allocation Uncertainty
Where Allocation cannot be established precisely, uncertainty should remain represented.
Therefore:
Attached and Scoped Liability ≠ Fully Allocated Liability.
Allocation Change
Allocation may change when:
Scope changes, a Determination changes, a Subject or Relationship state changes, an Allocation error is corrected, or another legitimate governance event occurs.
Changes should remain traceable.
Allocation Correction
An incorrect Allocation may be corrected without deleting the earlier governed state.
Therefore:
Allocation Correction ≠ Historical Erasure.
Allocation Reassessment
Allocation may be reassessed after new or changed governed information.
Therefore:
Allocation Reassessment ≠ Allocation Correction.
Allocation History
The current Allocation should remain distinguishable from prior Allocation states.
Therefore:
Current Liability Allocation ≠ Complete Liability Allocation History.
Determination Change
If the underlying Governed Liability Determination State changes materially, Scope and Allocation may require reassessment.
LSAS should not silently preserve a Scope or Allocation that depends upon a superseded Determination.
Determination Re-Entry
Where LSAS reveals that the problem lies in Liability Determination rather than Scope or Allocation, the matter should return to LDS.
LSAS must not repair an Attachment defect by manipulating Scope.
Therefore:
Scope Adjustment ≠ Substitute for Determination Correction.
Earlier Lifecycle Re-Entry
Where a Scope or Allocation problem originates further upstream, governance should return to the earliest materially affected governance space.
The governing rule remains:
Re-enter the earliest materially affected governance space.
Scope and Allocation Authority
Where Scope or Allocation is established by a particular:
authority, institution, methodology, contractual process, human decision-maker, or automated system, that governance origin should remain identifiable.
External Authority Scope & Allocation
A court, regulator, arbitrator, insurer, contractual authority, or another competent institution may establish legally operative Scope or Allocation.
LSAS can represent that state without replacing the authority that produced it.
Therefore:
LIGA™ Scope & Allocation Governance ≠ Jurisdiction-Specific Adjudication.
Automated Scope & Allocation
AI or automated systems may support Scope or Allocation governance where appropriately authorized.
Their outputs should preserve:
methodology, input states, system identity, authority, uncertainty, and traceability.
Therefore:
Automated Allocation ≠ Authoritative Allocation by default.
No Harm-Severity Shortcut
Greater Harm does not automatically establish greater Liability Scope.
Therefore:
Harm Severity ≠ Liability Scope by default.
The applicable Liability Basis and governed Determination remain necessary.
No Fault-Percentage Shortcut
Where fault is represented proportionally, the fault percentage should not automatically become Liability Allocation.
Therefore:
Fault Percentage ≠ Liability Allocation by default.
No Responsibility Shortcut
Operational or organizational responsibility should not automatically become Liability Allocation.
Therefore:
Responsibility Distribution ≠ Liability Allocation.
No Accountability Shortcut
Accountability attribution should not automatically determine Liability distribution.
Therefore:
Accountability Allocation ≠ Liability Allocation.
No Causation 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 Payment Shortcut
Payment does not automatically establish the underlying Liability Allocation.
Therefore:
Payment Distribution ≠ Liability Allocation.
No Claim-Amount Shortcut
The amount or scope requested in a Claim does not establish Liability Scope.
Therefore:
Claimed Amount ≠ Liability Scope.
No Settlement Shortcut
A settlement amount should not automatically be interpreted as the underlying Liability Scope or Allocation.
Therefore:
Settlement Distribution ≠ Liability Allocation by default.
No Insurance-Limit Shortcut
An insurance limit does not define the underlying Liability Scope.
Therefore:
Insurance Limit ≠ Liability Scope.
No Ability-to-Pay Shortcut
A Subject's financial capacity does not establish the extent of its Liability.
Therefore:
Ability to Pay ≠ Liability Scope or Allocation.
Scope & Allocation Traceability
Every material Scope and Allocation state should remain traceable to:
the Governed Liability Determination State, applicable Liability Basis, Subject and Relationship structure, Scope methodology, Allocation methodology, material inputs, and relevant authority.
Historical Integrity
Corrections, reassessments, and later states should preserve earlier materially relevant Scope and Allocation records.
Therefore:
Current Scope & Allocation ≠ Complete Scope & Allocation History.
Governed Liability Scope & Allocation Structure
The principal output of LSAS is:
Governed Liability Scope & Allocation Structure
It should identify, where applicable:
the governing Liability Determination, Scope identity, Scope boundaries, included and excluded matters, partial or unresolved Scope, relevant Subjects, relevant Relationships, Allocation identities, Allocation method, allocated portions, unallocated portions, conflicts, uncertainty, authority, time, and historical state.
Meaning of the Output
A Governed Liability Scope & Allocation Structure means that established Liability has been sufficiently bounded and, where necessary, distributed for ongoing Liability governance.
It does not mean Liability has been:
paid, transferred, resolved, discharged, or finalized.
Therefore:
Scoped & Allocated Liability ≠ Resolved Liability.
Handoff to Liability State & Change
LSAS hands the:
Governed Liability Scope & Allocation Structure
to:
LSCS — Liability State & Change Standard
The next governance question becomes:
What is the current governed state of Liability, and how may that state legitimately change?
The boundary is:
LDS determines whether Liability exists.
LSAS determines its extent and distribution.
LSCS governs its ongoing state and change.
Governance Requirements
A conforming implementation of LSAS should ensure that:
Liability Scope is derived from an established Governed Liability Determination State.
Scope remains associated with the applicable Subject, Relationship, Object, Basis, and Determination.
Scope boundaries distinguish included, excluded, partial, and unresolved matters where relevant.
Quantitative and qualitative Scope remain distinguishable where necessary.
Liability Scope remains separate from Harm, loss, damage, Claim amount, insurance limits, and payment.
Allocation occurs only after sufficiently governed Liability Scope exists.
Allocation identifies the Liability Subject and Relationship to which each allocated portion applies.
Multi-Subject and multi-Relationship structures remain distinguishable.
Allocation methodology is explicit where distribution is required.
Unallocated portions remain visible.
Overlap, duplication, conflict, and under-allocation are detectable.
Primary Liability remains distinguishable from Transfer, Insurance, Indemnification, Payment, and Recourse.
Scope and Allocation uncertainty remain explicit.
Scope and Allocation changes remain traceable.
Corrections do not erase historical states.
Reassessment remains distinguishable from correction.
External authority states preserve their authority boundaries.
Scope or Allocation defects do not silently rewrite Liability Determination.
Re-entry occurs at the earliest materially affected governance space.
The resulting Scope & Allocation Structure is sufficiently governed for ongoing Liability State & Change
governance.
Governance Logic
The canonical LSAS governance logic is:
Governed Liability Determination State
↓
Identify Established Liability
↓
Identify Scope Object
↓
Establish Scope Boundaries
↓
Identify Included / Excluded / Partial / Unresolved Scope
↓
Establish Relevant Scope Dimensions
↓
Assess Scope Limitations / Exceptions / Uncertainty
↓
Governed Liability Scope
↓
Identify Allocation Requirement
↓
Identify Allocation Subjects & Relationships
↓
Establish Allocation Method
↓
Allocate Governed Liability Scope
↓
Identify Unallocated / Overlapping / Conflicting Portions
↓
Reconcile Scope & Allocation
↓
Preserve Authority / Time / Traceability / History
↓
Governed Liability Scope & Allocation Structure
↓
Handoff to Liability State & Change
Governance Outputs
LSAS may produce:
Liability Scope Identity
Liability Scope Boundary
Included Liability Scope
Excluded Liability Scope
Partial Liability Scope
Unresolved Liability Scope
Subject-Specific Liability Scope
Relationship-Specific Liability Scope
Object-Specific Liability Scope
Basis-Specific Liability Scope
Temporal Liability Scope
Quantitative Liability Scope
Qualitative Liability Scope
Scope Limitation Record
Scope Exception Record
Scope Uncertainty State
Liability Allocation Identity
Allocation Subject Record
Allocation Relationship Record
Allocation Basis Record
Allocation Method Record
Individual Allocation
Shared Allocation
Proportional Allocation
Non-Proportional Allocation
Layered Allocation
Unallocated Liability State
Allocation Conflict State
Allocation Uncertainty State
Allocation Reconciliation Record
Scope Change Record
Allocation Change Record
Historical Scope & Allocation Record
The principal output is:
Governed Liability Scope & Allocation Structure
Critical Distinctions
LSAS preserves the following distinctions:
Liability Determination ≠ Liability Scope Liability Scope ≠ Liability Allocation Potential Liability Scope ≠ Established Liability Scope Liability Scope without Determination Reference ≠ Fully Governed Liability Scope Excluded from Scope A ≠ Excluded from all Liability Partial Scope ≠ Complete Scope Attached Liability involving multiple Subjects ≠ Identical Liability Scope for every Subject Subject Liability ≠ Universal Relationship Scope Attachment under Basis A ≠ Scope under Basis B Consequence ≠ In-Scope Consequence by default Harm Scope ≠ Liability Scope by default Measured Loss ≠ In-Scope Liability Loss by default Liability Scope ≠ Monetary Amount by default Attached Liability ≠ Fully Known Liability Scope Scope Correction ≠ Historical Erasure Scope Reassessment ≠ Scope Correction Current Liability Scope ≠ Complete Liability Scope History Event Participant ≠ Allocation Subject by default Allocation to Subject ≠ Allocation across every Relationship of that Subject Shared Liability ≠ Identical Liability Percentage Allocation ≠ Liability Determination Primary Liability Allocation ≠ Final Economic Burden Liability-Bearing Party ≠ Paying Party Insurance Coverage ≠ Liability Allocation by default Indemnification ≠ Original Liability Allocation Liability Allocation ≠ Recourse Allocation One Event ≠ One Allocation Structure Local Liability Allocation ≠ Liability Network Allocation Unallocated Liability ≠ Nonexistent Liability Multiple Allocations ≠ Multiple Independent Liability Amounts by default Allocation Conflict ≠ Authority to Average the Results Attached and Scoped Liability ≠ Fully Allocated Liability Allocation Correction ≠ Historical Erasure Allocation Reassessment ≠ Allocation Correction Current Liability Allocation ≠ Complete Liability Allocation History Scope Adjustment ≠ Substitute for Determination Correction LIGA™ Scope & Allocation Governance ≠ Jurisdiction-Specific Adjudication Automated Allocation ≠ Authoritative Allocation by default Harm Severity ≠ Liability Scope by default Fault Percentage ≠ Liability Allocation by default Responsibility Distribution ≠ Liability Allocation Accountability Allocation ≠ Liability Allocation Causal Contribution ≠ Liability Allocation by default Payment Distribution ≠ Liability Allocation Claimed Amount ≠ Liability Scope Settlement Distribution ≠ Liability Allocation by default Insurance Limit ≠ Liability Scope Ability to Pay ≠ Liability Scope or Allocation Current Scope & Allocation ≠ Complete Scope & Allocation History Scoped & Allocated Liability ≠ Resolved Liability
Cross-Architecture Boundary
LSAS may rely on governed states originating from other OOF® architectures without taking governance ownership of those states.
HAGA™ governs Harm and its lifecycle. LSAS governs only whether and to what extent governed Harm or consequences fall within established Liability Scope.
ORA™ governs Operational Reality. Operational contribution does not automatically become Liability Allocation.
AGA™ governs Responsibility, Accountability, Authority, and Attribution. Responsibility or Accountability distribution does not automatically become Liability Allocation.
ADIT® governs evidence and auditability. Evidence may support Scope or Allocation without becoming Scope or Allocation.
VALIDOS™ governs validation.
OBIDENITY® governs identity and origin-bound structures.
AIG® and ASGA™ govern AI and autonomous-system governance states.
PGA™ governs Prediction.
SIMULOS® governs Simulation.
VFM® governs Value Flow. Value movement or economic burden does not automatically establish Liability Allocation.
The canonical interoperability principle is:
A governed external state may inform Liability Scope or Allocation without becoming Liability Scope or Allocation and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LSAS begins when a sufficiently governed:
Governed Liability Determination State
exists.
It governs:
Liability Scope Identification, Scope Boundary, included and excluded Scope, partial and unresolved Scope, Scope dimensions, Scope limitations, Scope exceptions, Scope uncertainty, Scope change, Allocation Identification, Allocation Subjects, Allocation Relationships, Allocation Basis, Allocation Method, individual and shared Allocation, proportional and non-proportional Allocation, layered Allocation, unallocated Liability, Allocation conflict, Allocation uncertainty, Allocation reconciliation, historical integrity, and downstream handoff.
LSAS does not determine:
whether Liability initially attaches, the underlying Harm, Operational Reality, Responsibility, Accountability, evidence validity, Claims, payment, insurance coverage, indemnification, Recourse, Liability Resolution, Discharge, or Finality.
LSAS ends when the:
Governed Liability Scope & Allocation Structure
is sufficiently explicit for Liability State & Change governance.
Canonical Principle
The governing principle of LSAS is:
Attachment establishes that Liability exists. Scope establishes what that Liability covers. Allocation establishes how that Liability is distributed.
These governance operations must remain distinct.
A system that collapses them cannot reliably distinguish:
whether Liability exists, how far it extends, and who bears which part of it.
Closing Statement
A Liability Determination answers whether Liability attaches.
It does not answer every question that follows from that Attachment.
Established Liability must still be bounded.
Its included and excluded extent must be identifiable.
Where several Subjects or Relationships participate, its distribution must be governed without confusing Liability with Harm, causation, responsibility, payment, insurance, or economic burden.
LSAS establishes that structure.
It converts Attached Liability into a governed Scope and, where necessary, an explicit Allocation without reopening the underlying Attachment Determination.
Attachment establishes Liability. Scope establishes its extent. Allocation establishes its distribution.
Determine Liability first. Then govern how far it extends and where it belongs.
Nahald
Liability Scope & Allocation Standard (LSAS)
Architecture:
LIGA™ — Liability Governance Architecture
Category:
Governance & Enforcement
Subcategory:
Liability Governance
Canonical Definition:
The Liability Scope & Allocation Standard (LSAS) governs how established Liability is bounded in extent and distributed across relevant Liability Subjects and Liability Relationships after Liability has been determined to attach.
Governed Space:
Liability Scope & Allocation
LSAS governs what an established Liability applies to, what falls outside its boundaries, how far that Liability extends, and how it is distributed where multiple Liability Subjects or Liability Relationships participate. It preserves the critical separation between determining that Liability exists and determining its extent and distribution.
Attachment establishes Liability. Scope establishes its extent. Allocation establishes its distribution.
→ View Standard