LSARM — Liability Scope & Allocation Reconciliation Module
LSARM — Liability Scope & Allocation Reconciliation Module
Reconciliation 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 & Allocation Reconciliation
Module ID:
LIGA-LSAS-LSARM-001
Origin ID:
OOF.CM.LIGA.08.05.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 Reconciliation Module (LSARM) governs how a Governed Liability Scope and Governed Liability Allocation are compared, reconciled, validated for structural consistency, and integrated into a coherent Governed Liability Scope & Allocation Structure.
LSARM determines whether Liability Allocation remains within the applicable Liability Scope, whether all materially relevant Scope portions are appropriately represented, whether any Liability has been omitted, duplicated, over-allocated, under-allocated, inconsistently distributed, or associated with the wrong Subject, Relationship, Basis, Object, obligation, consequence, or temporal boundary.
It preserves legitimate unresolved, unallocated, overlapping, uncertain, conditional, or disputed states rather than manufacturing artificial consistency.
LSARM does not redetermine Liability Attachment.
It does not independently redefine Liability Scope or perform a new Allocation.
It governs the transition:
Governed Liability Scope + Governed Liability Allocation → Scope–Allocation Comparison → Coverage & Consistency Assessment → Gap / Overlap / Conflict Identification → Reconciliation → Governed Liability Scope
& Allocation Structure
Its foundational distinction is:
Allocation Consistency ≠ Allocation Completeness by force.
Operational Role
The operational role of LSARM is:
to ensure that the governed Liability Scope and the resulting Liability Allocation remain structurally consistent before Liability enters ongoing State & Change governance.
LSCBM establishes what Liability covers.
LALIM identifies what requires Allocation.
LALDM performs the distribution.
LSARM determines whether those results still fit together.
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 LSARM governs:
Liability Scope & Allocation Reconciliation
Its principal inputs are:
Governed Liability Scope
and:
Governed Liability Allocation
Its principal output is:
Governed Liability Scope & Allocation Structure
Its downstream handoff is:
Governed Liability Scope & Allocation Structure → LSCS — Liability State & Change Standard
Central Operational Question
Does the Governed Liability Allocation remain consistent with the Governed Liability Scope, with every material portion, Subject, Relationship, Basis, boundary, obligation, and unresolved state represented without unexplained omission, duplication, contradiction, or overreach?
Reconciliation Object
Every Reconciliation should identify the specific:
Governed Liability Scope, Governed Liability Allocation, Liability Determination, Liability Subject structure, Liability Relationship structure, Liability Object,
and Liability Basis
being reconciled.
Scope–Allocation Association
The Allocation being reconciled should derive from the applicable Governed Liability Scope.
Therefore:
Allocation without Scope Association ≠ Reconciled Liability Allocation.
Reconciliation Identity
Each material Reconciliation should possess a stable identity allowing later systems to distinguish:
the Scope assessed, the Allocation assessed, the reconciliation state, the applicable time, and subsequent revisions.
Reconciliation Preconditions
Before Reconciliation proceeds, LSARM should confirm that:
the Governed Liability Scope is identifiable, the Governed Liability Allocation is identifiable, the underlying Liability Determination is identifiable, material Subjects and Relationships are represented, and Scope and Allocation are sufficiently traceable.
Scope Coverage Assessment
LSARM should determine whether all materially relevant portions of the Governed Liability Scope are represented in the Allocation structure.
A Scope portion may be:
Allocated, Not Requiring Allocation, Unallocated, Pending, Unknown, Uncertain, Disputed, or otherwise explicitly governed.
No material Scope portion should disappear merely because distribution was incomplete.
Allocation Boundary Assessment
Every Allocation should be checked against the applicable Scope Boundary.
An Allocation should not extend beyond the Liability Scope unless a legitimate upstream governance change has occurred.
Therefore:
Allocation Beyond Scope ≠ Valid Scope Expansion.
In-Scope Allocation
An Allocation is in-scope when the allocated Liability remains within the applicable Governed Liability Scope and its relevant dimensions.
Out-of-Scope Allocation
Where an Allocation concerns Liability outside the established Scope, the inconsistency should be explicit.
It should not be normalized merely because the Allocation has already been recorded or performed.
Therefore:
Recorded Allocation ≠ In-Scope Allocation by default.
Partial Scope–Allocation Alignment
A Scope portion may be only partly represented by Allocation.
LSARM should identify the represented and unrepresented portions separately.
Therefore:
Partial Allocation Coverage ≠ Complete Reconciliation.
Unallocated Scope
A governed Scope portion may remain unallocated.
LSARM should preserve the unallocated portion and its state.
Therefore:
Unallocated Scope ≠ Absent Liability.
Allocation Without Scope
An Allocation may appear in the record without a corresponding valid Scope basis.
LSARM should identify this as a reconciliation defect unless a legitimate Scope change is established.
Therefore:
Allocated Matter ≠ In-Scope Liability by default.
Scope Without Allocation
A Scope portion may legitimately require no distribution where one Subject or Relationship bears it entirely.
Alternatively, it may represent an Allocation gap.
LSARM should distinguish these cases.
Therefore:
Scope Without Multi-Party Distribution ≠ Allocation Defect by default.
Scope Completeness and Allocation Completeness
Scope completeness and Allocation completeness are separate states.
A complete Scope may have incomplete Allocation.
A complete Allocation cannot legitimately compensate for an incomplete Scope.
Therefore:
Scope Completeness ≠ Allocation Completeness.
Subject Reconciliation
LSARM should verify that each Allocation is associated with the correct Liability Subject.
Therefore:
Correct Allocation Amount + Wrong Subject ≠ Reconciled Allocation.
Relationship Reconciliation
The correct Subject is insufficient if the Allocation is associated with the wrong Liability Relationship.
Therefore:
Correct Subject + Wrong Relationship ≠ Reconciled Allocation.
Basis Reconciliation
LSARM should preserve the Liability Basis under which each relevant Scope and Allocation exists.
Therefore:
Allocation under Basis A ≠ Allocation under Basis B.
Object Reconciliation
The allocated Liability should remain associated with the correct Governed Liability Object.
An Allocation concerning one Object should not silently migrate to another.
Scope-Portion Reconciliation
Where Scope contains multiple portions, each Allocation should remain associated with the correct portion.
Therefore:
Correct Total Allocation ≠ Correct Scope-Portion Allocation by default.
Obligation Reconciliation
Where Liability contains different obligations, LSARM should verify that Allocation remains associated with the correct obligation.
A correct monetary distribution does not reconcile an incorrectly assigned performance obligation.
Consequence Reconciliation
Where Scope contains several consequences, Allocation should remain consequence-specific where required.
Therefore:
Correct Aggregate Allocation ≠ Correct Consequence Allocation by default.
Temporal Reconciliation
LSARM should verify that Allocation applies to the correct temporal Scope.
Therefore:
Correct Subject Allocation at T1 ≠ Correct Allocation at T2 by default.
Quantitative Reconciliation
Where quantitative Scope and Allocation exist, LSARM should assess whether distributed amounts, percentages, units, or other quantities reconcile with the governed allocable extent.
Qualitative Reconciliation
Where Liability is qualitative, LSARM should reconcile obligations, performance requirements, restrictions, repair duties, or other non-numerical Allocations against the applicable Scope.
Multi-Dimensional Reconciliation
Reconciliation may require simultaneous consistency across:
Subject, Relationship, Basis, Object, Scope portion, obligation, consequence, time, quantity, and other material dimensions.
Therefore:
Aggregate Consistency ≠ Multi-Dimensional Consistency by default.
Over-Allocation Detection
LSARM should identify where distributed Liability exceeds the governed allocable Scope without legitimate justification.
Potential Over-Allocation should remain explicit until resolved.
Under-Allocation Detection
LSARM should identify where a Scope portion requiring distribution remains incompletely allocated.
The unallocated portion should remain visible.
Duplicate Allocation Detection
The same underlying Liability portion should not be counted more than once merely because it appears in multiple records.
Therefore:
Duplicate Allocation Record ≠ Additional Liability.
Legitimate Allocation Overlap
Some Liability Relationships may legitimately overlap.
LSARM should distinguish legitimate overlap from duplicate Allocation.
Therefore:
Allocation Overlap ≠ Allocation Duplication by default.
Scope Overlap
Different Scope portions may overlap.
LSARM should determine whether the resulting Allocations preserve that overlap correctly or inadvertently double-count it.
Allocation Gap
An Allocation Gap exists where a Scope portion requiring Allocation lacks a sufficient Allocation state.
A gap should be represented rather than hidden.
Scope Gap
A Scope Gap exists where Allocation reveals a materially relevant Liability matter that was not sufficiently scoped.
This should trigger upstream review rather than automatic Scope expansion.
Therefore:
Allocation Discovery ≠ Automatic Scope Expansion.
Reconciliation Conflict
A Reconciliation Conflict exists where Scope and Allocation cannot both be treated as correct under the current governed structure.
The conflict should be explicit.
No Forced Reconciliation
LSARM must not alter valid Scope or Allocation merely to make records appear consistent.
Therefore:
Administrative Consistency ≠ Governed Reconciliation.
Reconciliation by Correction
Where inconsistency results from an identifiable error, the affected Scope or Allocation may require correction through the appropriate governance space.
LSARM identifies the defect and routes it.
It does not silently rewrite upstream states.
Reconciliation by Reassessment
Where the inconsistency results from changed circumstances or new governed information rather than error, reassessment may be required.
Therefore:
Reconciliation Correction ≠ Reconciliation Reassessment.
Reconciliation by Explicit Unresolved State
Where a conflict cannot yet be resolved, LSARM may preserve it as:
Pending, Unknown, Uncertain, Disputed, or another explicit unresolved state.
Therefore:
Unresolved Reconciliation ≠ Failed Governance.
Explicit uncertainty may be more legitimate than artificial resolution.
Pending Reconciliation
A Reconciliation may remain Pending where a required upstream or external process has not yet completed.
Unknown Reconciliation
A Reconciliation may remain Unknown where sufficient governed information is unavailable.
Therefore:
Unknown Reconciliation ≠ Reconciled State.
Uncertain Reconciliation
Where Scope and Allocation can only be reconciled with material uncertainty, that uncertainty should remain visible.
Disputed Reconciliation
Where competing governed positions exist, LSARM should preserve the dispute and the positions to which it relates.
Therefore:
Disputed Reconciliation ≠ Authority to Select a Preferred Structure.
Allocation Method Reconciliation
LSARM should verify that the Allocation Method applied by LALDM is consistent with the structure identified by LALIM and with the applicable Scope.
Method Deviation
Where the applied Allocation Method differs from the identified or authorized method, the deviation should be explicit and justified.
Therefore:
Distribution Result ≠ Method Compliance.
Allocation Unit Reconciliation
LSARM should verify that the Allocation Unit corresponds to the governed Scope and Allocation Object.
A percentage, monetary amount, obligation, or other unit should not be substituted for another without legitimate transformation.
Allocation Sum Reconciliation
Where the Allocation Method requires reconciliation to a defined total, LSARM should verify the total.
It should not impose a 100% requirement where the applicable structure does not require one.
Therefore:
Reconciliation ≠ Mandatory 100% Allocation by default.
Residual Reconciliation
Any residual portion should be explicitly:
allocated, unallocated, excluded, or otherwise governed.
Residuals should not disappear through rounding or aggregation.
Rounding Reconciliation
Where quantitative Allocation uses rounding, LSARM should verify that rounding does not materially distort the governed Scope or create unexplained residuals.
Network Reconciliation
A Liability Network may contain multiple local Scopes and Allocations.
LSARM should preserve the relationship between:
local reconciliation, and:
network-wide reconciliation.
Local Reconciliation
A locally reconciled Liability Relationship does not establish that the complete Liability Network is reconciled.
Therefore:
Local Reconciliation ≠ Liability Network Reconciliation.
Network-Wide Reconciliation
Where network-wide consistency is required, LSARM should assess whether local Scope and Allocation structures interact without:
unexplained duplication, contradiction, gaps, or structural collapse.
Cross-Relationship Consistency
Different Liability Relationships may legitimately produce different Allocations.
Difference alone is not inconsistency.
Therefore:
Different Allocations ≠ Reconciliation Conflict by default.
Cross-Basis Consistency
Liability under different Bases may possess different Scope and Allocation structures.
LSARM should preserve those distinctions rather than forcing one universal outcome.
Primary and Secondary Structure Reconciliation
LSARM should distinguish primary Liability Allocation from secondary structures such as:
insurance, indemnification, Transfer, contribution, reimbursement, or Recourse.
Therefore:
Secondary Economic Distribution ≠ Primary Liability Allocation.
Paying Party Reconciliation
A payment by a different party should not automatically change the underlying Liability Allocation.
Therefore:
Paying Party ≠ Liability-Bearing Party.
Insurance Reconciliation
Insurance performance may coexist with the underlying Liability Allocation.
LSARM should not reconcile them as though they were the same governance object.
Therefore:
Insurance Distribution ≠ Liability Allocation.
Indemnification Reconciliation
An indemnification relationship may redistribute economic consequences downstream.
It does not automatically alter primary Liability Scope or Allocation.
Recourse Reconciliation
Potential or established Recourse should remain separate from primary Allocation.
Therefore:
Recourse Structure ≠ Primary Allocation Structure.
Harm Reconciliation Boundary
Harm states may inform Scope.
They do not need to equal Liability Allocation.
Therefore:
Harm Distribution ≠ Liability Allocation.
LSARM should not force alignment between them merely because both concern the same occurrence.
Causation Reconciliation Boundary
Causal contribution and Liability Allocation may differ legitimately.
Therefore:
Causal Distribution ≠ Liability Distribution by default.
Responsibility Reconciliation Boundary
Responsibility distribution and Liability Allocation may differ.
Therefore:
Responsibility Distribution ≠ Liability Allocation.
Accountability Reconciliation Boundary
Accountability attribution and Liability Allocation remain separate governance objects.
Therefore:
Accountability Attribution ≠ Liability Allocation.
Fault Reconciliation Boundary
Fault distribution should not be used as an automatic reconciliation target for Liability Allocation.
Therefore:
Fault Distribution ≠ Liability Allocation by default.
Claim Reconciliation Boundary
A Claim may assert a Scope or Allocation different from the governed Liability structure.
LSARM reconciles governed Scope and Allocation, not the Claim against its preferred outcome.
Therefore:
Claimed Scope & Allocation ≠ Governed Scope & Allocation.
Payment Reconciliation Boundary
Payment records may be relevant downstream evidence but should not become the reconciliation target for substantive Liability Allocation.
Therefore:
Payment Total ≠ Liability Allocation Total by default.
Settlement Reconciliation Boundary
A settlement may intentionally differ from the substantive Liability Scope or Allocation.
Therefore:
Settlement Structure ≠ Liability Scope & Allocation Structure by default.
Authority Reconciliation
Where different authorities produce different Scope or Allocation states, LSARM should preserve:
authority identity, applicable domain, time, status, and relationship between the states.
It should not merge authority-specific results without a legitimate governance basis.
Automated Reconciliation
AI or automated systems may support reconciliation where appropriately governed.
Automated reconciliation should preserve:
system identity, methodology, input versions, Scope state, Allocation state, authority, uncertainty, and traceability.
Therefore:
Automated Reconciliation ≠ Authoritative Reconciliation by default.
Reconciliation Traceability
Every material reconciliation outcome should remain traceable to:
the Governed Liability Determination State, Governed Liability Scope, Governed Liability Allocation, relevant Subjects, Relationships, Bases, Scope portions, Allocation Method, authority, and material inputs.
Reconciliation Rationale
The reason Scope and Allocation are considered consistent, inconsistent, partially reconciled, or unresolved should be reconstructable.
Therefore:
Reconciliation State ≠ Reconciliation Rationale.
Reconciliation Sufficiency
A reconciliation is sufficient when:
the relevant Scope is explicit, the Allocation is explicit, material dimensions align, gaps are represented, overlap and duplication are distinguished, conflicts are visible, unresolved states are preserved, and the resulting structure can enter Liability State & Change governance without reconstructing LSAS from raw inputs.
Reconciliation Completeness
Reconciliation is complete when every materially relevant Scope and Allocation relationship has an explicit reconciliation state.
This does not require every unresolved Liability question to be finally settled.
Therefore:
Reconciliation Completeness ≠ Liability Finality.
Reconciliation State
A reconciliation may be represented as:
Reconciled
Partially Reconciled
Pending
Unknown
Uncertain
Disputed
Inconsistent
or another explicitly governed state where necessary.
Reconciliation Change
A previously reconciled structure may require change where:
Scope changes, Allocation changes, the underlying Determination changes, a conflict is resolved, new information emerges, or an earlier error is corrected.
Reconciliation Correction
An erroneous reconciliation may be corrected.
Earlier materially relevant states should remain preserved.
Therefore:
Reconciliation Correction ≠ Historical Erasure.
Reconciliation Reassessment
A correct earlier reconciliation may require reassessment because the governed circumstances changed.
Therefore:
Reconciliation Reassessment ≠ Reconciliation Correction.
Reconciliation Versioning
Material reconciliation changes should remain versioned or otherwise historically traceable.
The system should preserve:
previous state, current state, reason for change, time, authority, and affected Scope and Allocation versions.
Current Reconciled Structure
The current Scope & Allocation Structure should remain distinguishable from its historical states.
Therefore:
Current Reconciled Structure ≠ Complete Reconciliation History.
Re-Entry to Allocation Distribution
Where reconciliation identifies an error in the actual distribution, the matter should return to LALDM.
LSARM should not silently redistribute Liability.
Re-Entry to Allocation Identification
Where the problem lies in the identified Allocation structure, participants, method, or dependencies, the matter should return to LALIM.
Re-Entry to Scope Boundary
Where Allocation reveals that the Scope Boundary is defective, the matter should return to LSCBM.
LSARM must not enlarge or narrow Scope merely to make Allocation fit.
Therefore:
Reconciliation Adjustment ≠ Scope Correction.
Re-Entry to Scope Identification
Where a materially relevant Scope component was never identified, the matter should return to LSCIM.
Re-Entry to Liability Determination
Where the reconciliation problem originates in Liability Attachment or Determination, the matter should return to LDS.
LSARM must not repair an invalid Determination through Scope or Allocation manipulation.
Earlier Lifecycle Re-Entry
Where the problem originates earlier in LIGA™, governance should return to the earliest materially affected governance space.
The governing principle remains:
Re-enter the earliest materially affected governance space.
Historical Integrity
Re-entry, correction, reassessment, or reconciliation change must not rewrite earlier governed history.
Therefore:
Reconciliation Change ≠ Historical Rewrite.
Governed Liability Scope & Allocation Structure
The principal output of LSARM is:
Governed Liability Scope & Allocation Structure
It integrates the reconciled state of:
Liability Determination reference, Liability Scope, Scope boundaries, included Scope, excluded Scope, partial Scope, unresolved Scope, Allocation Objects, Liability Subjects, Liability Relationships, Liability Bases, allocated portions, unallocated portions, Allocation Methods, Allocation layers, dependencies, overlap, residuals, conflicts, uncertainty, authority, rationale, time, provenance, and historical state.
Meaning of the Output
A Governed Liability Scope & Allocation Structure means that established Liability has been sufficiently:
bounded, distributed where necessary, reconciled, and preserved for ongoing Liability State & Change governance.
It does not mean Liability has been:
transferred, paid, settled, resolved, discharged, or finalized.
Therefore:
Reconciled Liability ≠ Resolved Liability.
Downstream Handoff
LSARM hands the:
Governed Liability Scope & Allocation Structure
to:
LSCS — Liability State & Change Standard
The next LIGA™ governance question becomes:
What is the current governed state of Liability, and how may that state legitimately change?
The architecture boundary is:
LDS determines whether Liability attaches.
LSAS determines and reconciles its Scope and Allocation.
LSCS governs its ongoing state and change.
Minimum Implementation Framework
A conforming implementation of LSARM must provide exactly the following eight capabilities:
Scope–Allocation Association & Reconciliation Object Governance
Capability to associate the correct Governed Liability Scope, Governed Liability Allocation, Liability Determination, Subjects, Relationships, Objects, Bases, and versions within one explicit Reconciliation Object.
Coverage, Boundary & Multi-Dimensional Consistency Governance
Capability to verify Scope coverage and Allocation consistency across Subject, Relationship, Basis, Object, Scope portion, obligation, consequence, temporal, quantitative, qualitative, and other materially relevant dimensions.
Gap, Over-Allocation, Under-Allocation, Overlap & Duplication Governance
Capability to identify Scope gaps, Allocation gaps, out-of-Scope Allocation, Over-Allocation, Under-Allocation, legitimate overlap, duplicate Allocation, residuals, and unexplained omissions.
Network, Layer & Secondary-Structure Reconciliation Governance
Capability to reconcile local and network-wide Liability structures while preserving distinctions between primary Allocation and Insurance, Indemnification, Transfer, Recourse, Payment, and other secondary structures.
Unresolved, Conflict & Authority-Specific Reconciliation Governance
Capability to preserve Pending, Unknown, Uncertain, Disputed, Inconsistent, conflicting, and authority-specific Scope and Allocation states without manufacturing artificial consistency.
Reconciliation Rationale, Traceability & Sufficiency Governance
Capability to maintain explicit reconciliation rationale, methodology, provenance, authority, temporal state, reconstruction paths, and sufficiency assessment.
Reconciliation Change, Correction, Reassessment, Versioning & Re-Entry
Capability to govern reconciliation changes, corrections, reassessments, version transitions, historical integrity, and targeted re-entry to the earliest materially affected governance space.
Liability State & Change Handoff Governance
Capability to produce a Governed Liability Scope & Allocation Structure sufficiently coherent, bounded, reconciled, traceable, and historically preserved for Liability State & Change governance.
Governance Logic
The canonical LSARM governance logic is:
Governed Liability Scope + Governed Liability Allocation
↓
Confirm Reconciliation Object
↓
Associate Scope & Allocation
↓
Assess Scope Coverage
↓
Assess Allocation Boundary Compliance
↓
Reconcile Subject / Relationship / Basis / Object
↓
Reconcile Scope Portions / Obligations / Consequences / Time
↓
Assess Quantitative & Qualitative Consistency
↓
Identify Gaps / Over-Allocation / Under-Allocation
↓
Distinguish Overlap from Duplication
↓
Assess Network & Layer Consistency
↓
Preserve Unknown / Uncertain / Disputed / Conflicting States
↓
Determine Reconciliation State
↓
Preserve Rationale / Authority / Traceability / History
↓
Governed Liability Scope & Allocation Structure
↓
Handoff to Liability State & Change Governance
Governance Outputs
LSARM may produce:
Reconciliation Identity
Scope–Allocation Association Record
Scope Coverage State
Allocation Boundary Compliance State
Subject Reconciliation State
Relationship Reconciliation State
Basis Reconciliation State
Object Reconciliation State
Scope-Portion Reconciliation State
Obligation Reconciliation State
Consequence Reconciliation State
Temporal Reconciliation State
Quantitative Reconciliation State
Qualitative Reconciliation State
Allocation Gap Record
Scope Gap Record
Over-Allocation Record
Under-Allocation Record
Allocation Overlap Record
Allocation Duplication Record
Residual Reconciliation Record
Network Reconciliation State
Layer Reconciliation State
Secondary-Structure Boundary Record
Pending Reconciliation State
Unknown Reconciliation State
Uncertain Reconciliation State
Disputed Reconciliation State
Inconsistent Reconciliation State
Authority-Specific Reconciliation Record
Reconciliation Rationale
Reconciliation Change Record
Historical Reconciliation Record
The principal output is:
Governed Liability Scope & Allocation Structure
Critical Distinctions
LSARM preserves the following distinctions:
Allocation Consistency ≠ Allocation Completeness by force Allocation without Scope Association ≠ Reconciled Liability Allocation Allocation Beyond Scope ≠ Valid Scope Expansion Recorded Allocation ≠ In-Scope Allocation by default Partial Allocation Coverage ≠ Complete Reconciliation Unallocated Scope ≠ Absent Liability Allocated Matter ≠ In-Scope Liability by default Scope Without Multi-Party Distribution ≠ Allocation Defect by default Scope Completeness ≠ Allocation Completeness Correct Allocation Amount + Wrong Subject ≠ Reconciled Allocation Correct Subject + Wrong Relationship ≠ Reconciled Allocation Allocation under Basis A ≠ Allocation under Basis B Correct Total Allocation ≠ Correct Scope-Portion Allocation by default Correct Aggregate Allocation ≠ Correct Consequence Allocation by default Correct Subject Allocation at T1 ≠ Correct Allocation at T2 by default Aggregate Consistency ≠ Multi-Dimensional Consistency by default Duplicate Allocation Record ≠ Additional Liability Allocation Overlap ≠ Allocation Duplication by default Allocation Discovery ≠ Automatic Scope Expansion Administrative Consistency ≠ Governed Reconciliation Reconciliation Correction ≠ Reconciliation Reassessment Unresolved Reconciliation ≠ Failed Governance Unknown Reconciliation ≠ Reconciled State Disputed Reconciliation ≠ Authority to Select a Preferred Structure Distribution Result ≠ Method Compliance Reconciliation ≠ Mandatory 100% Allocation by default Local Reconciliation ≠ Liability Network Reconciliation Different Allocations ≠ Reconciliation Conflict by default Secondary Economic Distribution ≠ Primary Liability Allocation Paying Party ≠ Liability-Bearing Party Insurance Distribution ≠ Liability Allocation Recourse Structure ≠ Primary Allocation Structure Harm Distribution ≠ Liability Allocation Causal Distribution ≠ Liability Distribution by default Responsibility Distribution ≠ Liability Allocation Accountability Attribution ≠ Liability Allocation Fault Distribution ≠ Liability Allocation by default Claimed Scope & Allocation ≠ Governed Scope & Allocation Payment Total ≠ Liability Allocation Total by default Settlement Structure ≠ Liability Scope & Allocation Structure by default Automated Reconciliation ≠ Authoritative Reconciliation by default Reconciliation State ≠ Reconciliation Rationale Reconciliation Completeness ≠ Liability Finality Reconciliation Correction ≠ Historical Erasure Reconciliation Reassessment ≠ Reconciliation Correction Current Reconciled Structure ≠ Complete Reconciliation History Reconciliation Adjustment ≠ Scope Correction Reconciliation Change ≠ Historical Rewrite Reconciled Liability ≠ Resolved Liability
Cross-Architecture Boundary
LSARM may reconcile Liability Scope and Allocation using governed inputs originating from other OOF® architectures where those inputs are relevant.
HAGA™ governs Harm.
ORA™ governs Operational Reality.
AGA™ governs Responsibility, Accountability, Authority, and Attribution.
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.
LSARM does not reconcile these external governance objects as though they were Liability.
It reconciles only their legitimate relationship to the governed Liability Scope and Allocation.
The canonical interoperability principle is:
External governed states may inform Scope & Allocation reconciliation without becoming Liability Scope, Liability Allocation, or transferring governance ownership of their original domains to LIGA™.
Canonical Boundary
LSARM begins with:
Governed Liability Scope
and:
Governed Liability Allocation
and governs their reconciliation.
LSARM governs:
Scope–Allocation Association, Coverage, Boundary Compliance, Subject Consistency, Relationship Consistency, Basis Consistency, Object Consistency, Scope-Portion Consistency, Obligation Consistency, Consequence Consistency, Temporal Consistency, Quantitative and Qualitative Consistency, Gaps, Over-Allocation, Under-Allocation, Overlap, Duplication, Residuals, Network Reconciliation, Layer Reconciliation, Unresolved States, Conflicts, Authority-specific states, Rationale, Traceability, Change, Correction, Reassessment, Versioning, Historical Integrity, and downstream handoff.
LSARM does not govern:
initial Liability Attachment, new Scope Identification, new Scope Boundary determination, new Allocation Identification, new Allocation Distribution, Transfer, Recourse, Resolution, Discharge, or Finality.
LSARM ends when a:
Governed Liability Scope & Allocation Structure
is sufficiently coherent and traceable for Liability State & Change governance.
Use Case 1 — Multi-Party Industrial Liability Reconciliation
A Governed Liability Scope contains equipment repair, a defined production interruption period, and a partially included operational loss.
LALDM distributes relevant portions between an operator and a maintenance provider.
LSARM compares the resulting Allocation against the Scope.
It identifies that the equipment repair Allocation is consistent, the production interruption is fully represented, but part of the operational-loss Scope remains unallocated.
The unallocated portion remains explicit rather than being silently assigned.
Insurance payments are kept outside the primary Allocation reconciliation.
The result is a Governed Liability Scope & Allocation Structure ready for Liability State & Change governance.
Use Case 2 — Autonomous System Liability Network
Reconciliation
An autonomous system event produces several scoped Liability Relationships involving an operator, technology provider, and infrastructure provider.
Different Liability portions are distributed through individual, shared, and conditional Allocation structures.
LSARM reconciles the local Allocations against their respective Scopes and then checks the wider Liability Network for duplication, gaps, incompatible relationships, and out-of-Scope Allocation.
A disputed downstream portion remains explicitly unresolved rather than being forced into the network distribution.
The final Governed Liability Scope & Allocation Structure preserves each Subject, Relationship, Basis, Scope, Allocation, unresolved state, and historical link for subsequent LSCS governance.
Canonical Closing Statement
Scope and Allocation are not complete merely because each exists separately.
They must still fit together.
Every Allocation must remain within the Liability it distributes.
Every material Scope portion must remain visible.
Legitimate overlap must remain distinguishable from duplication.
Unallocated Liability must not disappear.
And reconciliation must never manufacture certainty merely to make the structure look complete.
LSARM converts governed Scope and governed Allocation into one coherent Liability structure without rewriting either to force consistency.
Scope defines the extent. Allocation distributes it. Reconciliation proves that the two still belong together.
Reconcile before Liability moves into State & Change governance.