LCHAM — Liability Change Assessment Module
LCHAM — Liability Change Assessment Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability State & Change Standard (LSCS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Change Assessment
Module ID: LIGA-LSCS-LCHAM-001
Origin ID: OOF.CM.LIGA.09.04.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 24 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 Change Assessment Module (LCHAM) governs how an Identified Liability Change is evaluated to determine its legitimate effect on an established Liability structure.
LCHAM determines whether the identified change affects the current Liability State, an upstream Liability governance structure, a downstream Liability process, multiple Liability Relationships, or no governed Liability component at all.
It assesses materiality, relevance, affected structure, dependency, propagation, temporal effect, authority, uncertainty, and required governance response.
LCHAM does not assume that every identified change changes Liability.
It may determine that the existing Liability structure remains valid.
Where change is established, LCHAM determines what is affected and where the matter must proceed for legitimate governance.
It governs the transition:
Identified Liability Change → Change Validity → Liability Relevance Assessment → Affected Structure Assessment → Change Effect Assessment → Re-Entry / State / Downstream Routing Determination → Assessed
Liability Change
Its foundational distinction is:
Identified Liability Change ≠ Determined Liability Change Effect.
Operational Role
The operational role of LCHAM is:
to determine what legitimate effect an identified change has on the governed Liability structure and what governance action must follow.
LCHIM identifies and bounds the change.
LCHAM assesses its effect.
LCHAM prevents a change from silently rewriting Liability merely because the change appears relevant.
Position in the LSCS Internal Flow
The internal LSCS progression is:
Liability State Identification → Liability State Transition → Liability Change Identification → Liability Change Assessment → Liability State History LCHAM governs:
Liability Change Assessment
Its principal input is:
Identified Liability Change
Its principal output is:
Assessed Liability Change
Its downstream outcomes may include:
No Liability Change
Liability State Update
Targeted Upstream Re-Entry
Liability Transfer & Recourse Routing
Liability Resolution & Discharge Routing
or another explicitly governed continuation.
Its handoff within LSCS is:
Assessed Liability Change → LSTHM — Liability State History Module
Central Operational Question
What legitimate effect does this identified change have on the governed Liability structure, which components are materially affected, and what governance action must follow?
Assessment Object
Every Change Assessment should identify the exact Identified Liability Change being evaluated.
The Assessment Object should remain linked to:
the Change Identity, Change Source, Change Object, Change Boundary, affected Liability structure, temporal context, and supporting governed inputs.
Assessment Baseline
LCHAM should identify the governed Liability structure against which the change is assessed.
The baseline may include:
Liability Determination, Scope, Allocation, current State, Subjects, Relationships, Objects, Bases, Conditions, Connections, obligations, and dependencies.
Change Validity
Before assessing effect, LCHAM should determine whether the identified change remains sufficiently supported to justify substantive assessment.
A detected or reported change may later prove:
valid, incorrect, duplicated, superseded, misclassified, unverifiable, or irrelevant.
Valid Change
A Valid Change is sufficiently established as an actual change in the relevant governed input or Liability structure.
Validity does not establish Liability effect.
Therefore:
Valid Change ≠ Liability Change Effect.
Invalid Change
Where the reported change did not occur, was incorrectly identified, or rests on an invalid comparison, LCHAM may determine that no Liability Change Assessment effect follows.
The invalid Change record should remain reconstructable.
Duplicate Change
Where the same underlying change appears through multiple records, LCHAM should avoid applying the effect multiple times.
Therefore:
Duplicate Change Records ≠ Multiple Liability Effects.
Superseded Change Input
Where later governed information supersedes an earlier Change input, both records should remain historically traceable.
The currently applicable input should be explicit.
Liability Relevance Assessment
A valid change must still be assessed for Liability relevance.
LCHAM asks whether the change materially affects any governed Liability component.
Therefore:
Valid External Change ≠ Liability-Relevant Change by default.
No Liability Effect
LCHAM may determine that an identified change has no material effect on Liability.
This is a legitimate governance outcome.
Therefore:
Change Assessment ≠ Required Liability Modification.
State-Relevant Effect
A change may affect only the current Liability State while leaving the upstream Liability structure valid.
In that case, LCHAM should identify the required State governance without unnecessarily reopening earlier lifecycle spaces.
Structural Liability Effect
A change may materially affect:
Liability Object, Basis, Relationships, Conditions, Connection, Determination, Scope, Allocation, or another upstream structure.
Such changes require targeted re-entry.
Downstream Liability Effect
A change may not require upstream reassessment but may create conditions for:
Transfer, Sharing, Recourse, Resolution, Satisfaction, Settlement, Discharge, or another downstream process.
LCHAM should identify the appropriate route.
Multi-Directional Effect
One change may require more than one governance response.
For example, a change may:
alter the current State, require Scope reassessment, and create Recourse relevance.
These effects should remain separately represented.
Materiality Assessment
LCHAM determines whether the identified change is materially significant to the governed Liability.
Materiality should be assessed against the actual Liability structure rather than the apparent size of the external event.
Material Change
A change is materially Liability-relevant where it legitimately affects or requires reassessment of a governed Liability component.
Non-Material Change
A change may be real but not materially affect Liability.
Therefore:
Real Change ≠ Material Liability Change.
Quantitative Materiality
Magnitude may be relevant where Liability depends upon measurable quantities, thresholds, amounts, duration, or other quantitative variables.
Quantitative significance should not automatically replace qualitative assessment.
Qualitative Materiality
A change may be material because it alters:
Subject identity, Relationship structure, authority, Basis, Condition, Connection, Scope category, Allocation logic, or another structural element even where its quantitative magnitude is small.
Cumulative Materiality
Multiple individually limited changes may collectively become material.
Therefore:
Individually Non-Material Changes ≠ Collectively Non-Material by default.
Change Effect Boundary
LCHAM should establish how far the legitimate effect of the change extends.
The effect boundary may be narrower than the Change Object itself.
Local Effect
A change may legitimately affect only one Liability component.
Therefore:
Local Liability Effect ≠ Complete Liability Effect.
Subject-Specific Effect
A change affecting Subject A should not automatically alter Subject B's Liability.
Therefore:
Subject A Change Effect ≠ Subject B Change Effect by default.
Relationship-Specific Effect
A change affecting one Liability Relationship should not automatically modify another.
Therefore:
Relationship A Change Effect ≠ Relationship B Change Effect by default.
Scope-Specific Effect
A change may affect only a defined Scope portion.
The unaffected Scope should remain governed under its existing structure.
Allocation-Specific Effect
A change may affect one allocated portion without requiring complete reallocation.
Obligation-Specific Effect
A change may alter one obligation while leaving other obligations unchanged.
State-Specific Effect
A change may affect only one Liability State component.
Therefore:
State-Specific Change ≠ Complete Liability Change.
Liability Network Effect
A change may affect several Relationships within a Liability Network.
Network relevance should be established rather than assumed.
Therefore:
Local Change ≠ Network-Wide Liability Effect by default.
Effect Propagation
Where a local change may legitimately affect another Liability component, LCHAM should assess the propagation path.
Propagation requires a governed relationship.
Propagation Basis
A valid propagation basis may arise from:
dependency, shared Scope, Allocation relationship, Relationship structure, obligation linkage, transfer structure, or another governed connection.
No Automatic Propagation
Temporal proximity, shared event origin, or technical association alone does not establish propagation.
Therefore:
Related Liability Components ≠ Automatic Shared Change Effect.
Propagation Boundary
Where propagation is established, LCHAM should determine where the effect stops.
A propagation path should not become an unlimited Liability expansion mechanism.
Change Effect on Liability State
Where the change legitimately affects the current State, LCHAM should identify:
the affected State Object, the nature of the effect, the applicable effective time, and whether State Transition governance is required.
Change Effect on Liability Context
Where the Liability Context itself is materially affected, LCHAM should route governance to LCS.
Change Effect on Liability Object
Where the Liability Object requires reassessment, governance should return to LOS.
Change Effect on Liability Basis
Where the change affects the basis under which Liability may exist, governance should return to LBS.
Change Effect on Liability Relationships
Where Subjects or Liability Relationships materially change, governance should return to LRS.
Change Effect on Liability Conditions
Where applicable Liability Conditions materially change, governance should return to LCOS.
Change Effect on Liability Connection
Where the Liability-Relevant Connection requires reassessment, governance should return to LCNS.
Change Effect on Liability Determination
Where the change materially affects whether Liability attaches, governance should return to LDS.
Therefore:
Change Assessment ≠ Liability Redetermination.
Change Effect on Liability Scope
Where the extent of established Liability requires reassessment, governance should return to LSAS.
Change Effect on Liability Allocation
Where distribution of Liability requires reassessment, governance should return to LSAS.
Therefore:
Change Assessment ≠ Liability Reallocation.
Earliest Materially Affected Governance Space
Where multiple upstream spaces are affected, LCHAM follows the rule:
Re-enter the earliest materially affected governance space.
Later affected structures should then be reconsidered through the legitimate lifecycle sequence where necessary.
Targeted Reassessment
Re-entry should be proportionate to the actual change.
The canonical principle is:
Reassess what materially changed. Preserve what remains valid.
No Universal Lifecycle Restart
A material change does not automatically require reconstruction of the entire Liability lifecycle.
Therefore:
Liability Change ≠ Complete Lifecycle Restart by default.
Re-Entry and Origin
Upstream re-entry does not automatically create a new Liability Origin.
Therefore:
Lifecycle Re-Entry ≠ New Liability Origin by default.
Re-Entry and History
Reassessment may modify the current Liability structure.
It must not erase the structure that previously governed.
The canonical rule is:
Re-entry must not rewrite history.
Change Effect on Determination vs State
LCHAM should distinguish whether new information changes:
the current operative State, or:
the underlying Liability Determination.
These are materially different outcomes.
Therefore:
Liability State Change ≠ Liability Determination Change.
Change Effect on Scope vs State
A change in the current operative condition does not necessarily change Liability Scope.
Therefore:
Liability State Change ≠ Liability Scope Change.
Change Effect on Allocation vs State
A Liability State change does not automatically redistribute Liability.
Therefore:
Liability State Change ≠ Liability Allocation Change.
Change Effect on Relationship vs Allocation
A changed Relationship may create Allocation relevance without automatically changing existing Allocation.
Therefore:
Relationship Change ≠ Liability Reallocation by default.
Change Effect on Harm
A Harm change may become a Liability-relevant input.
LCHAM assesses only the Liability consequence.
Therefore:
Harm Change ≠ Liability Change Effect by default.
Change Effect on Responsibility
A change in Responsibility may affect Liability analysis where relevant.
It does not automatically alter Liability.
Therefore:
Responsibility Change ≠ Liability Change Effect by default.
Change Effect on Accountability
Accountability or attribution change may become relevant to Liability.
It remains a separate governance object.
Therefore:
Accountability Change ≠ Liability Change Effect by default.
Change Effect on Claims
A Claim change may be relevant to Liability administration or evidence.
It does not automatically modify substantive Liability.
Therefore:
Claim Change ≠ Liability Change Effect by default.
Change Effect on Payment
Payment may affect obligation performance or Resolution readiness.
It does not automatically determine Liability State, Discharge, or Finality.
Therefore:
Payment ≠ Liability Change Outcome by default.
Change Effect on Insurance
Insurance performance may change who pays or recovers economic value without changing the underlying primary Liability.
Therefore:
Insurance Performance ≠ Primary Liability Change by default.
Change Effect on Settlement
Settlement may create downstream Resolution relevance.
It does not automatically rewrite historical Liability.
Therefore:
Settlement ≠ Historical Liability Rewrite.
Transfer & Recourse Relevance
Where an assessed change creates:
Transfer, Sharing, Succession, Contribution, Indemnification, Insurance-related recourse, or another secondary Liability Relationship, LCHAM should route the relevant structure to:
LTRS — Liability Transfer & Recourse Standard
Transfer Does Not Rewrite Primary Liability
A downstream transfer or recourse effect should not silently replace the original Liability Relationship.
Therefore:
Transfer of Liability Consequence ≠ Erasure of Primary Liability.
Resolution & Discharge Relevance
Where an assessed change creates conditions for:
performance, satisfaction, settlement, discharge, extinguishment, or another Resolution process, LCHAM should route the relevant structure to:
LRDS — Liability Resolution & Discharge Standard
Resolution Trigger vs Resolution
A change may create Resolution eligibility without establishing Resolution.
Therefore:
Resolution-Relevant Change ≠ Liability Resolution.
Finality Boundary
LCHAM does not determine Liability Finality.
Therefore:
Assessed Liability Change ≠ Liability Finality.
Finality remains governed by LCFS.
Temporal Effect Assessment
LCHAM should determine when the assessed Liability effect becomes applicable.
This may differ from:
Change Occurrence Time, Change Discovery Time, Change Assessment Time, and Change Recording Time.
Change Effective Time
Change Effective Time identifies when the assessed change legitimately affects the governed Liability.
Therefore:
Change Occurrence Time ≠ Liability Change Effective Time by default.
Retrospective Effect
An assessed change may legitimately affect an earlier Liability period.
The governance record should preserve both the earlier represented state and the later assessment.
Therefore:
Retrospective Liability Effect ≠ Historical Erasure.
Prospective Effect
A change may be assessed now but become effective later.
Therefore:
Assessed Future Effect ≠ Current Liability State by default.
Change Authority
Where an assessed Liability effect requires authority, LCHAM should identify:
the applicable authority, the authority scope, the affected Liability structure, and the effective boundary of the authority.
Authority Limitation
Authority over one Change effect does not automatically establish authority over the complete Liability lifecycle.
Therefore:
Change Authority ≠ Universal Liability Authority.
Conflicting Authority
Where different authorities produce incompatible effects, the conflict should remain explicit until legitimately resolved.
LCHAM should not silently merge incompatible authority states.
Evidence Sufficiency
The assessment should use evidence sufficient for the effect being established.
Evidence quantity alone does not establish assessment sufficiency.
Evidence vs Assessment
Evidence supports Change Assessment.
It does not determine the Liability effect by itself.
Therefore:
Evidence of Change ≠ Assessed Liability Effect.
Unknown Effect
Where the Liability effect cannot yet be determined, the assessment should remain Unknown.
Therefore:
Unknown Liability Effect ≠ No Liability Effect.
Uncertain Effect
Where several effects remain materially plausible, uncertainty should remain explicit.
Therefore:
Uncertain Liability Effect ≠ Authority to Select a Preferred Effect.
Disputed Effect
Where materially competing governed positions exist concerning the effect of a change, the dispute should remain represented.
Therefore:
Disputed Liability Effect ≠ Determined Liability Effect.
Partial Assessment
LCHAM may determine the effect of some Change components while leaving others unresolved.
Therefore:
Partial Change Assessment ≠ Complete Change Assessment.
Assessment Rationale
Every material Change Assessment should preserve why the identified effect was reached.
A result without rationale is insufficient for reconstructable governance.
Therefore:
Assessment Outcome ≠ Assessment Rationale.
Assessment Provenance
LCHAM should preserve sufficient provenance to trace:
the Identified Liability Change, baseline, inputs, evidence, authority, methodology, affected structure, effect determination, effective time, and routing outcome.
Assessment Traceability
A qualified reviewer should be able to reconstruct:
Identified Liability Change → Assessment Basis → Affected Structure → Effect Analysis → Governance Route →
Assessed Liability Change
without rebuilding the matter from raw records.
Assessment Consistency
Equivalent Change conditions should be assessed consistently where materially equivalent governance conditions apply.
Different results should remain explainable where relevant conditions differ.
Assessment Correction
Where a Change Assessment was incorrectly performed or recorded, it may require correction.
The earlier assessment should remain historically reconstructable.
Therefore:
Assessment Correction ≠ Historical Erasure.
Assessment Reassessment
A previously legitimate Change Assessment may later require reassessment because new governed information or circumstances emerge.
Therefore:
Assessment Reassessment ≠ Assessment Correction.
Change Assessment Versioning
Materially changed assessments should be versioned or otherwise historically distinguishable.
The current assessment should not erase prior governed assessments.
No Silent Liability Rewrite
No Change Assessment should silently overwrite:
Liability Determination, Scope, Allocation, State, Subject, Relationship, or historical record.
Every material effect should proceed through the governance space that owns that effect.
Assessed Liability Change
The principal output of LCHAM is:
Assessed Liability Change
It should identify, where applicable:
Change Identity, Assessment Identity, assessment baseline, Change validity, Liability relevance, materiality, affected Liability components, effect boundary, affected Subjects, affected Relationships, affected Objects, affected Bases, affected Conditions, affected Connections, Determination relevance, Scope relevance, Allocation relevance, State relevance, obligation relevance, propagation effects, network effects, effective time, authority, evidence sufficiency, uncertainty, conflict, re-entry requirement, downstream routing, rationale, provenance, and historical relationship.
Assessment Outcome States
An Assessed Liability Change may produce one or more outcomes such as:
No Material Liability Effect
Current State Remains Valid
Liability State Change Required
Upstream Reassessment Required
Scope Reassessment Required
Allocation Reassessment Required
Liability Determination Reassessment Required
Transfer & Recourse Governance Required
Resolution & Discharge Governance Required
Further Information Required
Effect Unknown
Effect Uncertain
Effect Disputed
or another explicitly governed outcome.
Multiple Assessment Outcomes
One Change may produce several simultaneous outcomes.
For example:
one Liability Relationship may remain unchanged, another may require Scope reassessment, and a third may require Recourse governance.
Therefore:
One Identified Change ≠ One Universal Liability Effect.
Meaning of the Output
An Assessed Liability Change means that the identified change has been evaluated sufficiently to determine its legitimate Liability relevance, affected governance structure, and required next governance action.
It does not mean that every required upstream or downstream governance action has already been completed.
Therefore:
Assessed Liability Change ≠ Completed Liability Lifecycle Change.
Handoff to Liability State History
LCHAM hands the:
Assessed Liability Change
together with its relevant State effects, re-entry decisions, routing decisions, rationale, authority, and temporal information to:
LSTHM — Liability State History Module
The next governance requirement is to preserve how the Liability changed without losing the states and assessments that preceded the current structure.
The boundary is explicit:
LCHIM identifies the Change.
LCHAM assesses its Liability effect.
LSTHM preserves the governed history of Liability State and Change.
Minimum Implementation Framework
A conforming implementation of LCHAM must provide exactly the following eight capabilities:
Change Validity, Baseline & Liability Relevance Assessment
Capability to validate the Identified Liability Change, establish the applicable Liability baseline, and determine whether the Change has material Liability relevance.
Materiality, Effect Boundary & Affected Structure Assessment
Capability to determine quantitative, qualitative, cumulative, local, partial, structural, State-specific, Relationship-specific, and network-level effects without expanding the Change beyond its legitimate boundary.
Liability State, Determination, Scope, Allocation & Obligation Effect Assessment
Capability to distinguish effects on current State from effects requiring reassessment of Liability Determination, Scope, Allocation, obligations, or other upstream Liability structures.
Propagation, Dependency, Multi-Relationship & Network Effect Assessment
Capability to determine whether and how a legitimate Change effect propagates across dependent Liability components, Relationships, Subjects, or Liability Networks while preventing automatic propagation.
Temporal, Authority, Evidence & Uncertainty Governance
Capability to establish Change Effective Time, authority requirements and boundaries, evidence sufficiency, and Unknown, Uncertain, Disputed, or Partial Change effects.
Targeted Re-Entry & Lifecycle Preservation Governance
Capability to identify the earliest materially affected LIGA™ governance space, route targeted reassessment, preserve unaffected governance, maintain Origin continuity, and prevent historical rewriting.
Downstream Transfer, Recourse, Resolution & Discharge Routing Governance
Capability to identify when an Assessed Liability Change requires LTRS or LRDS governance without treating routing as completion of those downstream processes.
Liability State History Handoff Governance
Capability to produce an Assessed Liability Change sufficiently explicit, bounded, temporally situated, traceable, and historically connected for preservation within Liability State History.
Governance Logic
The canonical LCHAM governance logic is:
Identified Liability Change
↓
Validate Change
↓
Establish Liability Baseline
↓
Assess Liability Relevance
↓
Assess Materiality
↓
Identify Affected Liability Components
↓
Establish Effect Boundary
↓
Assess State Effect
↓
Assess Determination / Scope / Allocation / Obligation Effect
↓
Assess Dependencies & Propagation
↓
Assess Network Effect
↓
Determine Effective Time
↓
Assess Authority & Evidence Sufficiency
↓
Preserve Unknown / Uncertain / Disputed Effects
↓
Determine Earliest Materially Affected Governance Space
↓
Determine Targeted Re-Entry
↓
Determine Downstream Routing
↓
Preserve Rationale / Provenance / Prior Structure
↓
Assessed Liability Change
↓
Handoff to Liability State History
Governance Outputs
LCHAM may produce:
Change Validity State
Liability Relevance Assessment
Materiality Assessment
No Material Liability Effect
Affected Liability Structure
Effect Boundary
Subject Effect Record
Relationship Effect Record
Object Effect Record
Basis Effect Record
Condition Effect Record
Connection Effect Record
Determination Reassessment Requirement
Scope Reassessment Requirement
Allocation Reassessment Requirement
State Change Requirement
Obligation Effect Record
Propagation Assessment
Network Effect Assessment
Change Effective Time
Authority Assessment
Evidence Sufficiency State
Unknown Effect Record
Uncertain Effect Record
Disputed Effect Record
Partial Assessment Record
Targeted Re-Entry Route
Transfer & Recourse Routing Requirement
Resolution & Discharge Routing Requirement
Assessment Rationale
Assessment Provenance Record
The principal output is:
Assessed Liability Change
Critical Distinctions
LCHAM preserves the following distinctions:
Identified Liability Change ≠ Determined Liability Change Effect Valid Change ≠ Liability Change Effect Duplicate Change Records ≠ Multiple Liability Effects Valid External Change ≠ Liability-Relevant Change by default Change Assessment ≠ Required Liability Modification Real Change ≠ Material Liability Change Individually Non-Material Changes ≠ Collectively Non-Material by default Local Liability Effect ≠ Complete Liability Effect Subject A Change Effect ≠ Subject B Change Effect by default Relationship A Change Effect ≠ Relationship B Change Effect by default State-Specific Change ≠ Complete Liability Change Local Change ≠ Network-Wide Liability Effect by default Related Liability Components ≠ Automatic Shared Change Effect Change Assessment ≠ Liability Redetermination Change Assessment ≠ Liability Reallocation Liability Change ≠ Complete Lifecycle Restart by default Lifecycle Re-Entry ≠ New Liability Origin by default Re-entry ≠ Historical Rewrite Liability State Change ≠ Liability Determination Change Liability State Change ≠ Liability Scope Change Liability State Change ≠ Liability Allocation Change Relationship Change ≠ Liability Reallocation by default Harm Change ≠ Liability Change Effect by default Responsibility Change ≠ Liability Change Effect by default Accountability Change ≠ Liability Change Effect by default Claim Change ≠ Liability Change Effect by default Payment ≠ Liability Change Outcome by default Insurance Performance ≠ Primary Liability Change by default Settlement ≠ Historical Liability Rewrite Transfer of Liability Consequence ≠ Erasure of Primary Liability Resolution-Relevant Change ≠ Liability Resolution Assessed Liability Change ≠ Liability Finality Change Occurrence Time ≠ Liability Change Effective Time by default Retrospective Liability Effect ≠ Historical Erasure Assessed Future Effect ≠ Current Liability State by default Change Authority ≠ Universal Liability Authority Evidence of Change ≠ Assessed Liability Effect Unknown Liability Effect ≠ No Liability Effect Uncertain Liability Effect ≠ Authority to Select a Preferred Effect Disputed Liability Effect ≠ Determined Liability Effect Partial Change Assessment ≠ Complete Change Assessment Assessment Outcome ≠ Assessment Rationale Assessment Correction ≠ Historical Erasure Assessment Reassessment ≠ Assessment Correction One Identified Change ≠ One Universal Liability Effect Assessed Liability Change ≠ Completed Liability Lifecycle Change
Cross-Architecture Boundary
LCHAM may assess Liability relevance arising from governed changes in other OOF® architectures.
ORA™ governs Operational Reality.
HAGA™ governs Harm.
AGA™ governs Responsibility and Accountability.
ADIT® governs auditability and evidence.
VALIDOS™ governs validation.
OBIDENITY® governs Origin-bound identity, ownership, authority, permission, provenance, transfer, and continuity.
AIG® and ASGA™ govern AI and autonomous-system behavior and operation.
VFM® governs Value Flow.
PGA™ governs Prediction.
SIMULOS® governs Simulation.
Changes in those domains may become relevant inputs to LCHAM.
LCHAM does not take governance ownership of those external changes.
It assesses only their legitimate effect on the governed Liability structure.
The canonical interoperability principle is:
An external governed change may affect Liability without becoming Liability, and its Liability effect must be assessed separately from the change itself.
Canonical Boundary
LCHAM begins with an:
Identified Liability Change
and governs assessment of that Change's legitimate effect on established Liability.
LCHAM governs:
Change validity, Liability relevance, materiality, effect boundary, affected Liability structure, State effects, Determination relevance, Scope relevance, Allocation relevance, obligation effects, dependencies, propagation, network effects, effective time, authority, evidence sufficiency, Unknown effects, Uncertain effects, Disputed effects, Partial assessments, targeted re-entry, downstream routing, assessment rationale, provenance, correction, reassessment, versioning, and historical preservation requirements.
LCHAM does not independently perform:
Liability redetermination, Scope reconstruction, Liability reallocation, Transfer, Recourse, Resolution, Discharge, or Finality.
Those effects are routed to the governance spaces that own them.
LCHAM ends when an:
Assessed Liability Change
is sufficiently explicit and traceable for legitimate lifecycle continuation and historical preservation.
Use Case 1 — Industrial Liability Change Assessment
An industrial Liability structure contains an Active repair obligation and an allocated loss component.
New technical information shows that an equipment dependency changed before the current Liability State was recorded.
LCHIM has already identified the change and its potentially affected Scope and obligation.
LCHAM assesses the change and determines that the repair obligation's current State requires reassessment, while the underlying Liability Determination remains valid.
It also determines that one Scope component may require reassessment under LSAS.
The remaining Liability structure is unaffected.
The result therefore does not restart the complete lifecycle.
It applies the principle:
Reassess what materially changed. Preserve what remains valid.
Use Case 2 — Autonomous System Liability Change
Assessment
An autonomous system involved in an established Liability structure is deactivated after a major operational change.
LCHIM identifies the deactivation and related operational changes as potentially Liability-relevant.
LCHAM assesses their actual effect.
It determines that system deactivation does not eliminate the established Liability, but one ongoing obligation is no longer operationally applicable and another remains Active.
A separate secondary Relationship now creates potential Recourse relevance.
LCHAM therefore preserves the unaffected Liability, routes the affected State for appropriate transition governance, and routes the secondary structure toward LTRS.
The assessment prevents the shortcut:
Operational Termination ≠ Liability Termination.
Canonical Closing Statement
Identifying a change is not enough.
The change must be assessed against the Liability structure that already exists.
Some changes alter Liability.
Some alter only one part of it.
Some require upstream reassessment.
Some create downstream Transfer, Recourse, or Resolution relevance.
And some change nothing material at all.
LCHAM determines that difference without allowing new information to silently rewrite governed history.
Reassess what materially changed. Preserve what remains valid.
A Liability Change becomes governable when its effect, boundary, timing, and required governance route are made explicit.