LDCHM — Liability Discharge Module
LDCHM — Liability Discharge Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Resolution & Discharge Standard (LRDS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Discharge
Module ID: LIGA-LRDS-LDCHM-001
Origin ID: OOF.CM.LIGA.11.04.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 25 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 Discharge Module (LDCHM) governs whether, to what extent, and under what conditions an active Liability requirement may legitimately cease requiring continued performance or active governance through Discharge, Extinguishment, release, waiver, Satisfaction, Settlement effect, authoritative action, or another applicable Resolution mechanism.
LDCHM identifies the Discharge Object, affected Liability Relationship, relevant Subjects, Discharge Basis, authority, Scope, conditions, dependencies, effective time, remaining Liability, secondary Liability effects, and historical continuity necessary to establish a governed Discharge State.
It distinguishes Discharge from the events or mechanisms that may support it.
Payment, performance, Satisfaction, Settlement, release, waiver, or another Resolution-relevant event may support Discharge without automatically establishing it.
Its principal output is:
Governed Liability Discharge Structure
Its foundational distinction is:
Discharge ≠ Historical Erasure.
Operational Role
The operational role of LDCHM is:
to determine whether an identified active Liability requirement has legitimately ceased requiring continued performance or active governance, while preserving unresolved Liability, related Liability Relationships, secondary effects, and the complete historical path through which Discharge was reached.
Position in the LRDS Internal Flow
The internal LRDS progression is:
Liability Resolution Initiation → Liability Satisfaction → Liability Settlement → Liability Discharge → Liability
Resolution Verification
LDCHM governs:
Liability Discharge
Its relevant inputs may include:
Governed Liability Resolution Initiation Structure
Governed Liability Satisfaction Structure
Governed Liability Settlement Structure
and other applicable governed Resolution inputs.
Its principal output is:
Governed Liability Discharge Structure
The output proceeds to:
LRVFM — Liability Resolution Verification Module
Central Operational Question
Has the defined active Liability requirement legitimately ceased requiring continued performance or active governance, for which Subject and Relationship, within what Scope, on what Basis, under what conditions and authority, and what Liability remains active?
Discharge Object
Every Discharge assessment requires an explicit Discharge Object.
The Discharge Object is the Liability requirement whose active status is being assessed for termination.
It may concern:
a complete Liability Relationship, part of a Liability Relationship, a monetary requirement, a performance requirement, a Settlement requirement, a transferred requirement, a shared Liability component, a Recourse requirement, or another bounded Liability requirement.
Discharge Object vs Liability Object
The Discharge Object is not necessarily identical to the original Liability Object.
Therefore:
Discharge Object ≠ Liability Object by default.
Discharge Object vs Resolution Object
A Resolution Object may contain several independently dischargeable requirements.
Therefore:
Discharge Object ≠ Resolution Object by default.
Discharge Object Identity
The Discharge Object should retain sufficient identity to remain traceable to:
its Liability Origin, Liability Relationship, Scope, Allocation, State, and applicable Resolution history.
Discharge Basis
Every governed Discharge should possess an identifiable Basis.
Possible Discharge Bases may include:
completed Satisfaction, Settlement effect, release, waiver, Extinguishment, authoritative action, expiration or another applicable terminating condition, or another legitimate Resolution mechanism.
Liability Basis vs Discharge Basis
The Basis under which Liability originally arose and the Basis under which an active requirement is later discharged may differ.
Therefore:
Liability Basis ≠ Discharge Basis.
Resolution Basis vs Discharge Basis
A Resolution pathway may contain multiple mechanisms before Discharge occurs.
Therefore:
Resolution Basis ≠ Discharge Basis by default.
Discharge Trigger
A Discharge Trigger is an event or governed condition that creates a legitimate reason to assess whether an active Liability requirement should cease.
The Trigger does not itself establish Discharge.
Therefore:
Discharge Trigger ≠ Liability Discharge.
Discharge-Relevant Event
Payment, performance, Settlement completion, release, waiver, authoritative action, or another event may be Dischargerelevant.
Therefore:
Discharge-Relevant Event ≠ Liability Discharge.
Discharge Subject
LDCHM should identify the Subject whose active Liability requirement is proposed to be discharged.
Performing Subject vs Discharged Subject
The Subject whose performance supported Discharge may differ from the Subject whose Liability is being discharged.
Therefore:
Performing Subject ≠ Discharged Subject by default.
Paying Subject vs Discharged Subject
A third party may pay an amount associated with another Subject's Liability.
Therefore:
Paying Subject ≠ Discharged Subject by default.
Benefiting Subject
Where relevant, the Subject benefiting from Discharge should remain identifiable.
Multi-Subject Discharge
One Resolution mechanism may affect multiple Subjects differently.
Therefore:
One Discharge Event ≠ Uniform Discharge Across Subjects.
Discharge Relationship
Every Discharge should remain associated with the specific Liability Relationship to which it applies.
Relationship-Specific Discharge
Discharge of one Liability Relationship should not automatically discharge another.
Therefore:
Discharge of Relationship A ≠ Discharge of Relationship B.
Primary Liability Discharge
A primary Liability Relationship may be discharged while secondary Relationships remain active.
Recourse Liability Discharge
A Recourse Liability may possess its own Discharge state.
Therefore:
Primary Liability Discharge ≠ Recourse Liability Discharge.
Shared Liability Discharge
Where Liability is shared among multiple Subjects, one Subject may be discharged while others remain active.
Therefore:
Subject-Specific Discharge ≠ Shared Liability Discharge.
Network Discharge
A Liability Network may contain discharged and active Relationships simultaneously.
Therefore:
Local Discharge ≠ Liability Network Discharge.
Discharge Scope
LDCHM should establish exactly how much of the active Liability requirement is discharged.
The Scope may be:
complete, partial, conditional, Subject-specific, Relationship-specific, requirement-specific, or otherwise bounded.
Complete Discharge
Complete Discharge means that the complete defined Discharge Object no longer requires continued active performance or governance.
It does not automatically establish Finality.
Therefore:
Complete Discharge ≠ Liability Finality.
Partial Discharge
Partial Discharge ends only part of the active Liability requirement.
The remaining portion should remain explicit.
Therefore:
Partial Discharge ≠ Complete Liability Resolution.
Remaining Active Liability
Any portion outside the Discharge Scope should remain represented as active Liability.
Therefore:
Discharge of One Requirement ≠ Elimination of Remaining Liability.
Conditional Discharge
Discharge may depend upon continuing or future conditions.
Therefore:
Conditional Discharge ≠ Unconditional Discharge.
Discharge Conditions
Discharge Conditions may concern:
payment, performance, Settlement completion, verification, authority, timing, release, waiver, another Liability Relationship, or another applicable requirement.
Condition State
A Discharge Condition may be:
Satisfied, Unsatisfied, Partially Satisfied, Pending, Unknown, Uncertain, or Disputed.
Condition Failure
Failure of a required condition may prevent, suspend, reverse, or otherwise affect Discharge depending on the governed structure.
Discharge Dependency
A Discharge may depend upon another:
performance, payment, Subject, Relationship, Settlement, verification, authority, or governed state.
Dependencies should remain explicit.
Dependency vs Discharge
A dependency existing does not mean that the dependency has been fulfilled.
Therefore:
Discharge Dependency ≠ Discharge Completion.
Discharge Authority
Where Discharge requires authority, LDCHM should identify:
the authority, source, Scope, affected Subject, affected Relationship, and limitations.
Authority Scope
Authority to discharge one requirement should not automatically extend to another.
Therefore:
Local Discharge Authority ≠ Universal Liability Discharge Authority.
Authority to Release
Authority to issue a release should remain distinguishable from authority to discharge unrelated Liability.
Satisfaction and Discharge
Satisfaction may support Discharge.
It does not automatically establish Discharge.
Therefore:
Satisfaction ≠ Discharge by default.
Complete Satisfaction and Discharge
Even complete Satisfaction should be assessed against applicable Discharge requirements.
Therefore:
Complete Satisfaction ≠ Discharge by default.
Payment and Discharge
Payment may satisfy a monetary requirement without automatically discharging the complete Liability Relationship.
Therefore:
Payment ≠ Discharge by default.
Full Payment
Full payment of a monetary requirement may support Discharge of that requirement.
It does not automatically discharge non-monetary or secondary Liability.
Therefore:
Full Payment ≠ Complete Liability Discharge by default.
Partial Payment
Partial payment may support only partial Satisfaction and cannot by itself establish complete Discharge.
Therefore:
Partial Payment ≠ Complete Discharge.
Performance and Discharge
Performance may support Discharge where the applicable requirement has been fulfilled.
Performance itself remains distinct from Discharge.
Therefore:
Performance ≠ Discharge by default.
Settlement and Discharge
Settlement may establish conditions under which Liability may later be discharged.
Therefore:
Settlement ≠ Discharge by default.
Settlement Agreement vs Discharge
The existence of a Settlement agreement does not establish that its requirements have been performed.
Therefore:
Settlement Agreement ≠ Liability Discharge.
Settlement Performance vs Discharge
Performance of Settlement requirements may support Discharge.
It should still be assessed against the applicable Discharge structure.
Therefore:
Settlement Performance ≠ Discharge by default.
Settlement Completion vs Discharge
Settlement Completion may create a Discharge Basis.
It does not automatically establish Discharge beyond the applicable Settlement Scope.
Therefore:
Settlement Completion ≠ Universal Liability Discharge.
Release
A release may support Discharge of a defined Liability requirement.
Its Scope and authority should remain explicit.
Release Scope
A release should identify:
released Subject, releasing Subject, released requirement, affected Relationship, Scope, conditions, and effective time.
Local Release
A release affecting one requirement or Subject should not automatically extend across the Liability Network.
Therefore:
Local Release ≠ Network-Wide Release.
Release vs Historical Liability
Release may end an active requirement without erasing that the Liability Relationship previously existed.
Therefore:
Release ≠ Liability History Erasure.
Waiver
A waiver may affect the ability or requirement to pursue or enforce a defined Liability-related matter where applicable.
Its exact Scope should remain explicit.
Waiver vs Discharge
A waiver may support Discharge but should not automatically be equated with complete Discharge.
Therefore:
Waiver ≠ Complete Liability Discharge by default.
Waiver vs Erasure
Waiver does not erase historical Liability information.
Therefore:
Waiver ≠ Liability Erasure.
Extinguishment
Extinguishment represents a governed state in which an applicable active Liability requirement ceases under an established Basis.
Extinguishment vs Discharge
Extinguishment may be a Discharge mechanism or related terminal state within the Resolution structure.
Its meaning should remain explicit.
Extinguishment vs Finality
Extinguishment of an active requirement does not automatically establish lifecycle Finality.
Therefore:
Liability Extinguishment ≠ Liability Finality by default.
Discharge State
LDCHM may represent Discharge States such as:
Not Discharged, Discharge Pending, Partially Discharged, Conditionally Discharged, Discharged, Extinguished, Release-Dependent, Waiver-Dependent, Pending Verification, Unknown, Uncertain, Disputed, Reversed, Superseded, or another explicitly governed state.
These are methodological governance states, not universal legal classifications.
Pending Discharge
A Discharge may remain Pending while required conditions, authority, performance, or verification remain incomplete.
Unknown Discharge
Where available information cannot establish whether Discharge occurred, the state should remain Unknown.
Therefore:
Unknown Discharge ≠ No Discharge by assumption.
Uncertain Discharge
Where multiple materially plausible interpretations exist, uncertainty should remain explicit.
Therefore:
Uncertain Discharge ≠ Authority to Select a Preferred Discharge State.
Disputed Discharge
Subjects may dispute whether Discharge occurred or what it covers.
Therefore:
Disputed Discharge ≠ Governed Discharge.
Discharge Effective Time
LDCHM should identify when Discharge becomes effective.
Payment Time vs Discharge Time
Payment may occur before Discharge becomes effective.
Therefore:
Payment Time ≠ Discharge Effective Time by default.
Satisfaction Time vs Discharge Time
Satisfaction and Discharge may occur at different times.
Therefore:
Satisfaction Effective Time ≠ Discharge Effective Time by default.
Settlement Time vs Discharge Time
Settlement Formation, Settlement Performance, and Discharge may occur at different times.
Therefore:
Settlement Effective Time ≠ Discharge Effective Time by default.
Recording Time vs Discharge Time
A Discharge may be recorded after becoming effective.
Therefore:
Discharge Recording Time ≠ Discharge Effective Time by default.
Retrospective Discharge Identification
A Discharge may be recognized retrospectively.
Later identification should not overwrite the actual effective time.
Discharge Verification
LDCHM should assess whether the applicable Discharge Basis, Scope, conditions, authority, and dependencies have been sufficiently established.
Discharge Evidence
Evidence may support Discharge assessment.
Evidence does not itself establish Discharge.
Therefore:
Evidence of Discharge-Relevant Event ≠ Liability Discharge.
Administrative Closure
An administrative system may mark a matter as closed.
That signal does not establish Discharge.
Therefore:
Administrative Closure ≠ Liability Discharge.
Claim Closure
Closure of a Claim does not automatically discharge Liability.
Therefore:
Claim Closure ≠ Liability Discharge.
Claim Payment
Claim payment may be relevant to Satisfaction or Discharge but should not automatically determine either.
Therefore:
Claim Payment ≠ Liability Discharge by default.
Harm Resolution
Resolution of Harm does not establish Discharge of Liability.
Therefore:
Harm Resolution ≠ Liability Discharge.
Operational Termination
Termination of an operational process or relationship does not discharge existing Liability.
Therefore:
Operational Termination ≠ Liability Discharge.
Contract Termination
Termination of a contract does not automatically discharge existing Liability arising in relation to it.
Therefore:
Contract Termination ≠ Liability Discharge.
Responsibility Completion
Completion of a Responsibility does not automatically discharge Liability.
Therefore:
Responsibility Completion ≠ Liability Discharge.
Accountability Closure
Closure of an Accountability process does not establish Liability Discharge.
Therefore:
Accountability Closure ≠ Liability Discharge.
Primary vs Secondary Discharge
Primary Liability and secondary Liability Relationships may discharge independently.
Therefore:
Primary Liability Discharge ≠ Secondary Liability Discharge.
Recourse Continuation
A primary Liability may be discharged while Recourse remains active.
Therefore:
Primary Liability Discharge ≠ Recourse Resolution.
Insurance Performance
Insurance-related payment may support Satisfaction of an active requirement.
It does not automatically discharge every related Liability Relationship.
Therefore:
Insurance Payment ≠ Complete Liability Discharge by default.
Indemnification Performance
Indemnification performance may satisfy a secondary requirement without altering the historical primary Liability.
Therefore:
Indemnification Performance ≠ Primary Liability Erasure.
Network Discharge State
A Liability Network may simultaneously contain:
Discharged Relationships, Partially Discharged Relationships, active Relationships, Recourse Relationships, disputed Relationships, and Relationships pending Resolution.
Relationship Discharge vs Network Discharge
Therefore:
Liability Relationship Discharge ≠ Liability Network Discharge.
Discharge Propagation
Where Discharge of one Relationship affects another, the propagation Basis should be explicit.
Therefore:
Relationship Connection ≠ Automatic Discharge Propagation.
Discharge Change
A Discharge State may change due to:
condition failure, new information, correction, reassessment, reversal, authoritative change, or another materially relevant event.
Discharge Reversal
A previously operative Discharge may later cease to have the same effect where the applicable structure permits.
The earlier Discharge should remain historically preserved.
Therefore:
Discharge Reversal ≠ Discharge History Deletion.
Discharge Correction
An incorrectly recorded Discharge may be corrected.
Therefore:
Discharge Correction ≠ Historical Erasure.
Discharge Reassessment
A previously valid Discharge assessment may require reassessment when materially relevant circumstances change.
Therefore:
Discharge Reassessment ≠ Discharge Correction.
Discharge Supersession
A later governed Discharge assessment may supersede an earlier one.
Therefore:
Discharge Supersession ≠ Historical Deletion.
Discharge History
LDCHM should preserve:
Discharge Trigger, Basis, Subjects, Relationship, Scope, conditions, dependencies, authority, supporting Satisfaction, Settlement effects, release, waiver, Extinguishment, State changes, verification, and effective time.
Therefore:
Current Discharge State ≠ Complete Discharge History.
Historical Liability Preservation
Discharge changes active governance status.
It does not erase:
Liability Origin, Basis, Determination, Scope, Allocation, State history, Transfer, Sharing, Recourse, Satisfaction, Settlement, or prior Discharge states.
Discharge ≠ Historical Erasure
This is the foundational historical-integrity rule of LDCHM:
Discharge ≠ Historical Erasure.
A discharged Liability must remain reconstructable.
Discharge vs Resolution
Discharge may be a major component of Liability Resolution.
The two concepts should remain distinguishable.
Therefore:
Discharge ≠ Complete Liability Resolution by default.
Discharge vs Finality
Even complete Discharge does not independently establish Finality.
Therefore:
Discharge ≠ Liability Finality.
Post-Discharge Continuity
After Discharge, Liability history may still require:
continuity, record preservation, network reconciliation, Re-entry capability, and Finality assessment.
Reopening
A discharged Liability requirement may require governed Re-entry where materially relevant conditions arise.
Therefore:
Discharged Liability ≠ Permanently Non-Reopenable Liability by default.
Reopening vs New Liability
Reopening should not automatically create a new Liability Origin.
Therefore:
Liability Reopening ≠ New Liability by default.
Historical Integrity of Reopening
A reopened Liability requirement should preserve the prior Discharge State and the reason for Re-entry.
Therefore:
Reopening must not rewrite history.
Upstream Re-Entry
Where Discharge governance reveals a material defect in an earlier LIGA™ governance space, governance should return to the earliest materially affected space.
The canonical rule is:
Re-enter the earliest materially affected governance space.
Targeted Reassessment
The governing principle is:
Reassess what materially changed. Preserve what remains valid.
Automated Discharge Assessment
AI or automated systems may assist with:
condition tracking, payment reconciliation, Settlement performance monitoring, Scope comparison, authority checking, dependency tracking, Discharge State classification, and conflict detection.
Automation should not silently establish authoritative Discharge.
Therefore:
Automated Discharge Assessment ≠ Authoritative Liability Discharge by default.
Discharge Provenance
LDCHM should preserve sufficient provenance to reconstruct:
the active Liability before Discharge, Discharge Trigger, Object, Basis, Subjects, Relationship, Scope, conditions, dependencies, authority, supporting Resolution mechanisms, State, effective time, and subsequent changes.
Discharge Rationale
A governed Discharge State should be supported by a rationale explaining why the active Liability requirement no longer requires the same continued performance or governance.
Therefore:
Discharge State ≠ Discharge Rationale.
Governed Liability Discharge Structure
The principal output of LDCHM is:
Governed Liability Discharge Structure
It should identify, where applicable:
Liability Origin, Liability Relationship, Discharge identity, Discharge Object, Discharge Subject, Performing Subject, Paying Subject, benefiting Subject, Discharge Basis, Discharge Trigger, Discharge Scope, remaining active Liability, conditions, dependencies, authority, Satisfaction association, payment association, performance association, Settlement association, release, waiver, Extinguishment, Discharge State, effective time, primary and secondary Liability effects, Recourse continuation, network effects, verification status, uncertainty, disputes, conflicts, reversal, correction, reassessment, supersession, rationale, provenance, and Discharge history.
Meaning of the Output
A Governed Liability Discharge Structure means that the applicable Liability requirement has been sufficiently assessed to determine whether and to what extent it no longer requires continued active performance or governance.
It does not establish complete Liability Network Resolution.
It does not erase Liability history.
It does not establish Finality.
The structure must therefore proceed to Resolution Verification.
Minimum Implementation Framework
A conforming implementation of LDCHM must provide exactly the following eight capabilities:
Discharge Object, Subject & Relationship Identification
Capability to identify the exact Liability requirement proposed for Discharge, the affected Subjects and roles, and the specific Liability Relationship or Relationships to which the Discharge applies.
Discharge Basis, Trigger, Authority, Scope & Boundary Governance
Capability to identify the Discharge Basis and Trigger, verify applicable authority, establish complete, partial, conditional, Subject-specific, or Relationship-specific Scope, and preserve remaining active Liability.
Satisfaction, Payment, Performance & Settlement Association Governance
Capability to associate Satisfaction, payment, performance, Settlement, and other Resolution mechanisms with the Discharge assessment without automatically equating those mechanisms with Discharge.
Release, Waiver, Extinguishment, Condition & Dependency Governance
Capability to govern release, waiver, Extinguishment, Discharge Conditions, dependencies, failures, and applicable effects while preserving their distinct meanings.
Discharge State, Effective Time & Verification Governance
Capability to represent Discharge States, distinguish relevant event times from effective Discharge time, preserve uncertainty and disputes, and verify whether applicable Discharge requirements have been met.
Primary, Shared, Transfer, Recourse & Network Discharge Distinction
Governance
Capability to distinguish primary from secondary Liability Discharge, Subject-specific and shared Liability effects, Transfer and insurance-related performance, Recourse continuation, and local from network-wide Discharge.
Historical Integrity, Provenance, Change & Re-Entry Governance
Capability to preserve Discharge rationale, provenance, history, reversal, correction, reassessment, supersession, Reopening, and targeted upstream re-entry without rewriting prior Liability states.
Resolution Verification Handoff Governance
Capability to produce a Governed Liability Discharge Structure sufficiently explicit, bounded, verified, traceable, and historically preserved for final LRDS Resolution Verification.
Governance Logic
The canonical LDCHM governance logic is:
Governed Resolution / Satisfaction / Settlement Structure
↓
Identify Discharge Relevance
↓
Identify Discharge Object
↓
Identify Affected Subject & Liability Relationship
↓
Identify Discharge Basis & Trigger
↓
Verify Discharge Authority
↓
Establish Discharge Scope & Boundary
↓
Identify Remaining Active Liability
↓
Assess Satisfaction / Payment / Performance
↓
Assess Settlement Effect
↓
Assess Release / Waiver / Extinguishment
↓
Assess Conditions & Dependencies
↓
Establish Discharge State
↓
Establish Effective Time
↓
Assess Primary / Secondary / Recourse / Network Effects
↓
Verify Discharge
↓
Preserve Uncertainty / Dispute / Conflict
↓
Preserve Rationale / Provenance / History
↓
Governed Liability Discharge Structure
↓
Handoff to Resolution Verification
Governance Outputs
LDCHM may produce:
Discharge Identity
Discharge Object
Discharge Subject Structure
Affected Liability Relationship
Discharge Basis
Discharge Trigger
Discharge Authority Association
Discharge Scope
Discharge Boundary
Remaining Active Liability Record
Discharge Condition Structure
Discharge Dependency Structure
Satisfaction Association
Payment Association
Performance Association
Settlement Association
Release Structure
Waiver Structure
Extinguishment Record
Discharge State
Discharge Effective Time
Recourse Continuation Record
Network Discharge Record
Discharge Verification Record
Discharge Conflict Record
Discharge Reversal Record
Discharge Correction Record
Discharge Reassessment Record
Discharge Rationale
Discharge Provenance
Discharge History
The principal output is:
Governed Liability Discharge Structure
Critical Distinctions
LDCHM preserves the following distinctions:
Discharge ≠ Historical Erasure Discharge Object ≠ Liability Object by default Discharge Object ≠ Resolution Object by default Liability Basis ≠ Discharge Basis Resolution Basis ≠ Discharge Basis by default Discharge Trigger ≠ Liability Discharge Discharge-Relevant Event ≠ Liability Discharge Performing Subject ≠ Discharged Subject by default Paying Subject ≠ Discharged Subject by default One Discharge Event ≠ Uniform Discharge Across Subjects Discharge of Relationship A ≠ Discharge of Relationship B Primary Liability Discharge ≠ Recourse Liability Discharge Subject-Specific Discharge ≠ Shared Liability Discharge Local Discharge ≠ Liability Network Discharge Complete Discharge ≠ Liability Finality Partial Discharge ≠ Complete Liability Resolution Discharge of One Requirement ≠ Elimination of Remaining Liability Conditional Discharge ≠ Unconditional Discharge Discharge Dependency ≠ Discharge Completion Local Discharge Authority ≠ Universal Liability Discharge Authority Satisfaction ≠ Discharge by default Complete Satisfaction ≠ Discharge by default Payment ≠ Discharge by default Full Payment ≠ Complete Liability Discharge by default Partial Payment ≠ Complete Discharge Performance ≠ Discharge by default Settlement ≠ Discharge by default Settlement Agreement ≠ Liability Discharge Settlement Performance ≠ Discharge by default Settlement Completion ≠ Universal Liability Discharge Local Release ≠ Network-Wide Release Release ≠ Liability History Erasure Waiver ≠ Complete Liability Discharge by default Waiver ≠ Liability Erasure Liability Extinguishment ≠ Liability Finality by default Unknown Discharge ≠ No Discharge by assumption Uncertain Discharge ≠ Authority to Select a Preferred Discharge State Disputed Discharge ≠ Governed Discharge Payment Time ≠ Discharge Effective Time by default Satisfaction Effective Time ≠ Discharge Effective Time by default Settlement Effective Time ≠ Discharge Effective Time by default Discharge Recording Time ≠ Discharge Effective Time by default Evidence of Discharge-Relevant Event ≠ Liability Discharge Administrative Closure ≠ Liability Discharge Claim Closure ≠ Liability Discharge Claim Payment ≠ Liability Discharge by default Harm Resolution ≠ Liability Discharge Operational Termination ≠ Liability Discharge Contract Termination ≠ Liability Discharge Responsibility Completion ≠ Liability Discharge Accountability Closure ≠ Liability Discharge Primary Liability Discharge ≠ Secondary Liability Discharge Primary Liability Discharge ≠ Recourse Resolution Insurance Payment ≠ Complete Liability Discharge by default Indemnification Performance ≠ Primary Liability Erasure Liability Relationship Discharge ≠ Liability Network Discharge Relationship Connection ≠ Automatic Discharge Propagation Discharge Reversal ≠ Discharge History Deletion Discharge Correction ≠ Historical Erasure Discharge Reassessment ≠ Discharge Correction Discharge Supersession ≠ Historical Deletion Current Discharge State ≠ Complete Discharge History Discharge ≠ Complete Liability Resolution by default Discharge ≠ Liability Finality Discharged Liability ≠ Permanently Non-Reopenable Liability by default Liability Reopening ≠ New Liability by default Automated Discharge Assessment ≠ Authoritative Liability Discharge by default Discharge State ≠ Discharge Rationale
Cross-Architecture Boundary
LDCHM may receive governed inputs from adjacent OOF® architectures.
ORA™ may establish payment, performance, termination, release-related actions, or other Operational Reality.
HAGA™ may establish Harm Resolution or Recovery without determining Liability Discharge.
AGA™ may establish authority, Responsibility, Accountability, delegation, or completion states.
ADIT® may provide evidence and auditability.
VALIDOS™ may validate Discharge-relevant inputs.
OBIDENITY® may provide Subject identity, authority, succession, provenance, and continuity.
VFM® may govern economic or Value Flow associated with payment or Settlement.
AIG® and ASGA™ may provide AI or autonomous-system events relevant to Discharge.
These inputs may support Discharge assessment.
They do not independently establish Liability Discharge.
The canonical interoperability principle is:
An external system may establish that a Discharge-relevant event occurred; LDCHM governs whether that event legitimately ends the active Liability requirement to which it relates.
Canonical Boundary
LDCHM begins when an active Liability requirement has entered a state in which Discharge, Extinguishment, release, waiver, Satisfaction effect, Settlement effect, or another applicable mechanism may legitimately end all or part of its continuing active requirement.
LDCHM governs:
Discharge Objects, Subjects, Relationships, Basis, Triggers, authority, Scope, Boundary, remaining Liability, conditions, dependencies, Satisfaction association, payment, performance, Settlement effects, release, waiver, Extinguishment, Discharge States, effective time, primary and secondary Liability effects, Recourse continuation, network effects, verification, uncertainty, disputes, conflicts, change, reversal, correction, reassessment, historical integrity, provenance, and downstream handoff.
LDCHM does not independently establish:
original Liability, original Liability Scope or Allocation, Settlement formation, complete Liability Network Resolution, or Liability Finality.
LDCHM ends when the applicable Discharge structure is sufficiently represented as a:
Governed Liability Discharge Structure
for Resolution Verification.
Use Case 1 — Partial Discharge After Payment
An established Liability Relationship contains a monetary requirement and a separate corrective performance requirement.
The monetary requirement is fully satisfied and qualifies for Discharge.
LDCHM establishes Discharge of the monetary requirement while preserving the corrective performance requirement as active Liability.
The Relationship therefore contains both:
a discharged component, and an active component.
The monetary Discharge does not create complete Liability Resolution or Finality.
Use Case 2 — Primary Liability Discharged While Recourse
Remains Active
A primary Liability requirement is satisfied through payment and reaches a governed Discharge State.
A separate Recourse Relationship remains active because another Subject may be required to reimburse part of the economic burden.
LDCHM preserves the primary Discharge while keeping the Recourse Relationship independently active.
The primary Liability history remains reconstructable, and the Recourse lifecycle continues without rewriting the original Liability.
Canonical Closing Statement
Discharge changes whether a Liability requirement remains active.
It does not change the fact that the Liability existed.
Payment may support Discharge.
Satisfaction may support Discharge.
Settlement may support Discharge.
Release, waiver, or Extinguishment may support Discharge.
But each effect must remain bounded to the Liability requirement, Subject, Relationship, Scope, conditions, and authority to which it legitimately applies.
And even complete Discharge does not by itself establish Finality.
Discharge ≠ Historical Erasure.
End the active requirement where Discharge is legitimate. Preserve the Liability history that explains why it ended.