LREM — Liability Re-Entry Module
LREM — Liability Re-Entry Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Continuity & Finality Standard (LCFS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Re-Entry
Module ID: LIGA-LCFS-LREM-001
Origin ID: OOF.CM.LIGA.12.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 Re-Entry Module (LREM) governs when, why, where, and how an existing Liability lifecycle must return to active governance after a material change, newly available information, identified defect, failed condition, reversal, conflict, or other Re-entry-relevant development.
LREM determines whether Re-entry is required, identifies the earliest materially affected LIGA™ governance space, defines the Scope of reassessment, preserves unaffected prior governance, and maintains the historical continuity of the Liability lifecycle through the Re-entry process.
Re-entry does not automatically create a new Liability.
It does not erase prior Resolution, Discharge, or Finality.
It continues governance of the existing Liability lifecycle where materially required.
Its principal output is:
Governed Liability Re-Entry Structure
Its foundational rule is:
Re-entry must not rewrite history.
Operational Role
The operational role of LREM is:
to reactivate only the materially affected parts of an existing Liability lifecycle when renewed governance becomes necessary, while preserving the original Liability identity, valid prior governance, complete historical record, and explicit relationship between the pre-Re-entry and post-Re-entry states.
Position in the LCFS Internal Flow
The LCFS internal module progression is:
Liability Continuity Identification → Liability Historical Record → Liability Finality Assessment → Liability ReEntry → Liability Finality Record LREM governs:
Liability Re-Entry
Its principal inputs include:
Governed Liability Finality Assessment
Governed Liability Historical Record
and
Governed Liability Continuity Identification Structure
Its principal output is:
Governed Liability Re-Entry Structure
Where Re-entry is not required, the Finality assessment may proceed toward:
LFRM — Liability Finality Record Module
Where Re-entry is required, LREM routes the Liability lifecycle to the earliest materially affected LIGA™ governance space.
Central Operational Question
Has a material development occurred that requires renewed Liability governance, and if so, what is the earliest materially affected governance space, what must be reassessed, what remains valid, and how must the existing Liability history be preserved?
Re-Entry Object
Every Re-entry assessment should identify the exact Liability structure potentially requiring renewed governance.
The Re-Entry Object may be:
a Liability requirement, a Liability Relationship, a defined part of a Liability Relationship, a Recourse Relationship, a group of Relationships, or a Liability Network.
Re-Entry Object vs Liability Object
The Re-Entry Object is not necessarily identical to the original Liability Object.
Therefore:
Re-Entry Object ≠ Liability Object by default.
Re-Entry Trigger
A Re-entry Trigger is a development sufficiently relevant to require assessment of whether prior Liability governance remains valid.
Potential triggers may include:
new materially relevant information, new evidence, incorrect earlier information, changed conditions, new Subject information, new Relationship information, changed Liability-Relevant Connection, payment reversal, performance failure, Settlement failure, Discharge reversal, authority correction, new Transfer, new Recourse, or another material lifecycle development.
Trigger vs Re-Entry
A trigger does not automatically establish Re-entry.
Therefore:
Re-Entry Trigger ≠ Liability Re-Entry.
Materiality
LREM should determine whether the trigger is materially capable of affecting an existing Liability governance result.
Immaterial developments should not reopen governance unnecessarily.
Material Change vs Any Change
Therefore:
Change ≠ Material Re-Entry Trigger by default.
Re-Entry Requirement
Re-entry is required only where the trigger materially affects an existing Liability governance state or a dependency upon which that state relies.
Re-Entry vs Active Continuation
A Liability lifecycle that remains active does not necessarily require Re-entry.
Normal continuation through an active lifecycle should remain distinct from return to an earlier governance space.
Therefore:
Continued Liability Governance ≠ Re-Entry.
Re-Entry vs Reassessment
Reassessment is the renewed evaluation of a governance state.
Re-entry is the routing mechanism that determines where such reassessment must occur.
Therefore:
Re-Entry ≠ Reassessment.
Re-Entry vs Correction
Correction addresses an earlier governance representation that was incorrect.
Re-entry may also occur because circumstances legitimately changed after an earlier valid state.
Therefore:
Re-Entry ≠ Correction by default.
Re-Entry vs New Liability
Where the same Liability lifecycle continues, Re-entry should preserve its existing identity.
Therefore:
Re-entry ≠ New Liability by default.
Re-Entry vs New Origin
Re-entry should not create a new Origin merely because governance becomes active again.
Therefore:
Re-entry ≠ New Origin by default.
Reopening
Reopening occurs where a previously resolved, discharged, or Final Liability structure returns to active governance.
Re-entry provides the governance mechanism for that return.
Reopening vs New Liability
Therefore:
Liability Reopening ≠ New Liability by default.
Reopening vs Re-Entry
Not every Re-entry involves reopening a Final Liability.
A still-active Liability may re-enter an earlier governance space.
Therefore:
Re-Entry ≠ Post-Finality Reopening only.
Pre-Finality Re-Entry
Re-entry may occur before Finality where a material issue is discovered during active governance or Finality assessment.
Post-Finality Re-Entry
A Liability structure that previously reached Finality may legitimately return to active governance where a sufficient Reentry Basis exists.
Prior Finality Preservation
A later Re-entry should not erase the historical fact that Finality had previously been established.
Therefore:
Post-Finality Re-Entry ≠ Historical Finality Deletion.
Re-Entry Basis
Every governed Re-entry should possess an identifiable Basis explaining why renewed governance is necessary.
Re-Entry Basis Sufficiency
The Basis should be sufficient for the Scope and destination of Re-entry.
Therefore:
Re-Entry-Relevant Information ≠ Sufficient Re-Entry Basis by default.
Re-Entry Scope
LREM should identify exactly which part of the Liability lifecycle requires renewed governance.
The Scope may be:
requirement-specific, Subject-specific, Relationship-specific, state-specific, Recourse-specific, or network-wide.
Targeted Re-Entry
Re-entry should be limited to what materially requires renewed governance.
The canonical principle is:
Reassess what materially changed. Preserve what remains valid.
Full Lifecycle Restart
A material change does not automatically require restarting the complete LIGA™ lifecycle.
Therefore:
Re-entry ≠ Full Lifecycle Restart by default.
Earliest Materially Affected Governance Space
LREM should identify the earliest LIGA™ governance space whose output is materially affected by the Re-entry Basis.
The canonical routing rule is:
Re-enter the earliest materially affected governance space.
Why Earliest Matters
Returning too late may preserve a materially invalid upstream assumption.
Returning too early may unnecessarily reconstruct valid governance.
LREM therefore identifies the earliest point at which renewed governance is materially required.
Liability Context Re-Entry
Where the relevant context has materially changed or was incorrectly established, Re-entry may route to:
Liability Context Standard (LCS)
Liability Object Re-Entry
Where the governed Liability Object was materially misidentified, incorrectly bounded, or changed in a way affecting the lifecycle, Re-entry may route to:
Liability Object Standard (LOS)
Liability Basis Re-Entry
Where the applicable Liability Basis materially changes or was incorrectly represented, Re-entry may route to:
Liability Basis Standard (LBS)
Liability Relationship Re-Entry
Where a new Subject, corrected Subject, new Relationship, or material Relationship change emerges, Re-entry may route to:
Liability Relationship Standard (LRS)
Liability Conditions Re-Entry
Where relevant conditions materially change, fail, become satisfied, or were incorrectly represented, Re-entry may route to:
Liability Conditions Standard (LCOS)
Liability Connection Re-Entry
Where new information materially changes the Liability-Relevant Connection, Re-entry may route to:
Liability Connection Standard (LCNS)
Liability Determination Re-Entry
Where new information materially affects whether Liability attached or was correctly determined, Re-entry may route to:
Liability Determination Standard (LDS)
Scope & Allocation Re-Entry
Where the extent or distribution of Liability materially changes, Re-entry may route to:
Liability Scope & Allocation Standard (LSAS)
State & Change Re-Entry
Where the current Liability State materially changes without invalidating earlier upstream governance, Re-entry may route to:
Liability State & Change Standard (LSCS)
Transfer & Recourse Re-Entry
Where a new or changed Transfer, Sharing, succession, Indemnification, insurance-related, contribution, or Recourse structure arises, Re-entry may route to:
Liability Transfer & Recourse Standard (LTRS)
Resolution & Discharge Re-Entry
Where Satisfaction, Settlement, Resolution, Discharge, release, waiver, Extinguishment, or related conditions materially change, Re-entry may route to:
Liability Resolution & Discharge Standard (LRDS)
LCFS Internal Reassessment
Where the material change affects only continuity, historical reconstruction, Finality assessment, or Finality recording, reassessment may remain within LCFS.
Re-Entry Destination
The Re-entry Destination should identify the Parent Standard and, where sufficiently known, the relevant governance object requiring reassessment.
Re-Entry Boundary
LREM should establish a boundary identifying:
what changed, what prior output is affected, what remains valid, what must be reassessed, which downstream states depend on the affected output, and where reassessment may legitimately stop.
Preserved Validity
Prior governance unaffected by the Re-entry Basis should remain valid unless a material dependency requires reassessment.
Therefore:
Re-entry ≠ Automatic Invalidation of All Prior Governance.
Dependency Propagation
A changed upstream output may require reassessment of downstream outputs that materially depend upon it.
Propagation should follow actual governance dependencies.
Dependency vs Automatic Cascade
Therefore:
Upstream Change ≠ Automatic Full Downstream Invalidation.
Downstream Reassessment
LREM should identify which downstream governance outputs require reassessment because their Basis materially depends on the changed state.
Reassessment Stop Point
Reassessment may stop where the changed information no longer materially affects downstream governance.
Liability Identity Continuity
Re-entry should preserve the existing Liability identity where the same lifecycle continues.
Relationship Identity Continuity
A reopened Liability Relationship should remain linked to its earlier Relationship identity unless a genuinely new Relationship is formed.
Network Continuity
Where Re-entry affects one Relationship within a Liability Network, LREM should preserve the network association while limiting reassessment to materially affected Relationships.
Local Re-Entry
One Liability Relationship may re-enter governance while other Relationships remain Final.
Therefore:
Relationship Re-Entry ≠ Liability Network Re-Entry by default.
Network Re-Entry
Network-level Re-entry should occur only where the material change affects the wider network structure.
Primary Liability Re-Entry
Primary Liability may reopen without automatically reopening Recourse.
Recourse Re-Entry
Recourse may re-enter governance independently from primary Liability.
Therefore:
Primary Liability Re-Entry ≠ Recourse Re-Entry by default.
Shared Liability Re-Entry
Where Liability is shared, Re-entry should identify which Subjects and Relationships are materially affected.
Re-Entry Authority
Where renewed governance requires authority, LREM should identify the applicable authority and its Scope.
Authority to Reopen vs Authority to Determine
Authority to initiate Re-entry does not necessarily equal authority to perform the resulting Liability Determination.
Therefore:
Re-Entry Authority ≠ Liability Determination Authority by default.
Local Re-Entry Authority
Authority to reopen one Relationship should not automatically extend to the complete Liability Network.
Therefore:
Local Re-Entry Authority ≠ Universal Network Re-Entry Authority.
Authority Conflict
Where Re-entry authority is disputed or conflicting, the conflict should remain explicit.
Re-Entry Conditions
Re-entry may depend on specific conditions.
LREM should represent whether those conditions are:
satisfied, unsatisfied, pending, unknown, uncertain, or disputed.
Conditional Re-Entry
Where Re-entry depends on unresolved conditions, its status should remain conditional.
Re-Entry State
LREM may represent states such as:
Not Required, Assessment Pending, Conditionally Required, Required, Initiated, In Progress, Completed, Unknown, Uncertain, Disputed, Superseded, or another explicitly governed state.
These are methodological governance states, not universal legal classifications.
Unknown Re-Entry State
Where available information is insufficient to determine whether Re-entry is required, the state should remain Unknown.
Therefore:
Unknown Re-Entry State ≠ No Re-Entry Required by assumption.
Uncertain Re-Entry
Where materially plausible alternatives remain, uncertainty should remain explicit.
Disputed Re-Entry
A disputed Re-entry requirement should remain represented as disputed until legitimately resolved.
Re-Entry Effective Time
LREM should identify when renewed governance becomes effective where applicable.
Trigger Time vs Re-Entry Time
The triggering event may occur before Re-entry is identified or initiated.
Therefore:
Re-Entry Trigger Time ≠ Re-Entry Effective Time by default.
Discovery Time vs Trigger Time
Information about an earlier event may become known later.
Therefore:
Discovery Time ≠ Re-Entry Trigger Event Time by default.
Reopening Time vs Original Finality Time
A reopened Liability lifecycle should preserve both times.
The later Reopening does not rewrite the earlier Finality Effective Time.
New Evidence
New evidence may justify Re-entry where it materially affects prior governance.
Evidence alone does not automatically establish the new Liability state.
Therefore:
New Evidence ≠ New Liability Determination.
Evidence vs Re-Entry
New evidence may create a Re-entry Basis without determining the outcome of the reassessment.
Therefore:
Evidence Supporting Re-Entry ≠ Predetermined Reassessment Outcome.
Incorrect Earlier Information
Where prior governance relied on materially incorrect information, LREM should identify the earliest governance space affected.
Correction vs Changed Reality
LREM should distinguish:
an earlier state that was incorrect when established, from an earlier state that was valid but later became outdated because reality changed.
Historical Correction
Correction should preserve what was previously recorded and why it was corrected.
Therefore:
Correction ≠ Historical Erasure.
Changed Reality
Where reality changed after a valid earlier governance state, Re-entry should preserve the validity of the earlier state for its historical period.
Payment Reversal
A reversed payment may require renewed Satisfaction, Resolution, State, or other Liability governance.
It does not automatically recreate every earlier Liability state.
Settlement Failure
Failure or termination of a Settlement may require renewed governance where it materially affects Resolution or Discharge.
Therefore:
Settlement Failure ≠ Automatic Restoration of Every Prior Liability State.
Discharge Reversal
Where a Discharge state becomes invalid or is legitimately reversed, LREM should identify the affected requirement and appropriate Re-entry Destination.
Resolution Reversal
Resolution reversal should preserve the prior Resolution as part of the history.
Therefore:
Resolution Reversal ≠ Resolution History Deletion.
Finality Reversal
Where a Final Liability legitimately re-enters active governance:
Finality Reversal ≠ Finality History Deletion.
New Subject Information
New information about a Subject may require Relationship, Scope, Allocation, Transfer, Recourse, or other reassessment depending on material effect.
New Relationship Information
Discovery of a previously unidentified Liability Relationship may require local or network-level Re-entry.
New Recourse Relationship
A newly formed or newly identified Recourse Relationship does not automatically reopen the primary Liability Relationship.
Therefore:
New Recourse Relationship ≠ Primary Liability Reopening by default.
External Lifecycle Change
Changes in Harm, Accountability, Claims, Operational Reality, identity, or another adjacent governance domain may create Re-entry-relevant inputs.
They do not automatically require Liability Re-entry.
Harm Change
A change in Harm governance may be relevant to Liability.
Therefore:
Harm Reopening ≠ Liability Reopening by default.
Claim Reopening
A reopened Claim does not automatically reopen Liability.
Therefore:
Claim Reopening ≠ Liability Reopening.
Accountability Reopening
Renewed Accountability governance does not automatically require Liability Re-entry.
Therefore:
Accountability Reopening ≠ Liability Reopening.
Operational Change
A new operational event may create a new Liability issue or affect an existing one.
LREM should distinguish these cases.
Therefore:
New Operational Event ≠ Existing Liability Re-Entry by default.
Re-Entry vs New Liability Formation
Where a new event creates a genuinely separate Liability Origin, it should enter LIGA™ as a new lifecycle rather than being forced into Re-entry of an unrelated prior Liability.
Same Origin Test
LREM should assess whether the renewed governance concerns:
the same Liability Origin, the same continuing Liability Relationship, a secondary Relationship, or a genuinely new Liability lifecycle.
Historical Integrity
Re-entry should preserve:
the pre-Re-entry State, Resolution, Discharge, Finality assessment, Finality State where applicable, Trigger, Basis, Destination, reassessment path, and resulting new State.
Re-Entry History
Each Re-entry should become part of the Governed Liability Historical Record.
No Retroactive Rewrite
A later state should not be represented as though it had always existed.
Therefore:
Later Liability State ≠ Historical State by retroactive substitution.
Re-Entry Provenance
LREM should preserve sufficient provenance to explain:
what triggered Re-entry, where the information came from, what governance state was affected, why the chosen destination was selected, and what reassessment followed.
Re-Entry Rationale
A governed Re-entry should contain sufficient rationale to explain why renewed governance was necessary.
Re-Entry Conflict
Conflicting information concerning whether Re-entry is required should remain explicit.
Therefore:
Conflicting Re-Entry Inputs ≠ Authority to Force Re-Entry.
Re-Entry Gap
Where material information necessary to determine Re-entry is unavailable, the gap should remain visible.
Automated Re-Entry Detection
AI or automated systems may assist with:
change detection, new evidence detection, condition monitoring, payment reversal detection, Settlement failure detection, relationship change detection, historical inconsistency detection, dependency analysis, and Re-entry routing.
Automation may identify potential triggers.
It should not silently rewrite Liability states.
Therefore:
Automated Re-Entry Trigger Detection ≠ Liability Re-Entry.
Automated Routing
Automated systems may propose the earliest materially affected governance space.
The routing should remain explainable and preserve uncertainty where material ambiguity exists.
Re-Entry Completion
Re-entry is complete when the materially affected governance spaces have been reassessed and a sufficiently coherent updated Liability state has been established.
Re-Entry Completion vs Finality
Completion of Re-entry does not automatically establish Finality.
Therefore:
Re-Entry Completion ≠ Liability Finality.
Return to LCFS
After upstream reassessment, the updated Liability structure should return to LCFS where continuity, historical record, Finality assessment, or Finality recording requires renewed governance.
Finality Reassessment After Re-Entry
Where Re-entry materially affects a previous Finality Basis, Finality should be reassessed.
Finality Restoration
A reopened Liability may later qualify for Finality again.
The new Finality assessment should remain connected to the earlier Finality and Re-entry history.
Multiple Re-Entry Cycles
One Liability lifecycle may contain multiple Re-entry cycles.
Each should remain distinguishable and historically reconstructable.
Governed Liability Re-Entry Structure
The principal output of LREM is:
Governed Liability Re-Entry Structure
It should identify, where applicable:
Re-Entry Object, Liability Origin, affected Liability requirement, affected Subjects, affected Liability Relationships, Liability Network relevance, Re-Entry Trigger, Trigger Time, Discovery Time, Re-Entry Basis, materiality assessment, Re-Entry Scope, affected prior governance output, earliest materially affected governance space, Re-Entry Destination, preserved valid governance, downstream dependencies, required reassessment, Re-Entry authority, conditions, Re-Entry State, effective time, uncertainty, disputes, conflicts, historical continuity, prior Resolution, prior Discharge, prior Finality, provenance, and Re-Entry rationale.
Meaning of the Output
A Governed Liability Re-Entry Structure means that renewed Liability governance has been sufficiently bounded and routed.
It identifies:
what must be reconsidered, where governance must return, what prior governance remains valid, and how the existing Liability history must be preserved.
It does not predetermine the result of the reassessment.
It does not create Finality.
Minimum Implementation Framework
A conforming implementation of LREM must provide exactly the following eight capabilities:
Re-Entry Object, Trigger, Basis & Materiality Identification
Capability to identify the Re-Entry Object, Re-entry Trigger, supporting Basis, relevant times, and whether the development is materially capable of affecting prior Liability governance.
Liability Origin, Subject, Relationship & Network Continuity Governance
Capability to preserve the existing Liability Origin and identity, distinguish affected Subjects and Relationships, maintain Liability Network associations, and separate Re-entry from genuinely new Liability formation.
Re-Entry Scope, Boundary & Earliest Affected Governance Space Identification
Capability to define the Scope of Re-entry, establish what prior governance is affected, and identify the earliest materially affected LIGA™ governance space.
Dependency, Preserved Validity & Reassessment Propagation Governance
Capability to identify which prior outputs remain valid, which downstream outputs materially depend on the affected state, where reassessment must propagate, and where it may legitimately stop.
Resolution, Discharge, Finality, Transfer & Recourse Re-Entry Governance
Capability to govern Re-entry involving Resolution, Discharge, prior Finality, Transfer, Sharing, secondary Liability, Recourse, and Liability Network structures without collapsing their independent lifecycle states.
Authority, Condition, State, Temporal, Uncertainty & Conflict Governance
Capability to represent Re-entry authority, conditions, states, effective time, uncertainty, disputes, conflicts, and unresolved information without forcing unsupported Re-entry.
Historical Integrity, Provenance, Correction & Reopening Governance
Capability to preserve pre-Re-entry states, distinguish correction from changed reality, maintain Re-entry provenance and rationale, govern Reopening, and ensure that Re-entry does not rewrite history.
Re-Entry Routing, Completion & LCFS Return Governance
Capability to route reassessment to the correct LIGA™ governance space, determine when Re-entry is complete, and return the updated Liability structure to LCFS for renewed continuity, historical, Finality, and Finality Record governance.
Governance Logic
The canonical LREM governance logic is:
Governed Liability Finality Assessment + Governed Liability Historical Record
↓
Identify Potential Re-Entry Trigger
↓
Identify Re-Entry Object
↓
Associate Liability Origin / Subjects / Relationships / Network
↓
Assess Trigger Materiality
↓
Establish Re-Entry Basis
↓
Define Re-Entry Scope & Boundary
↓
Identify Earliest Materially Affected Governance Space
↓
Identify Preserved Valid Governance
↓
Map Downstream Dependencies
↓
Determine Required Reassessment Propagation
↓
Assess Authority / Conditions / Time / Uncertainty / Conflict
↓
Preserve Prior Resolution / Discharge / Finality History
↓
Establish Re-Entry Destination
↓
Governed Liability Re-Entry Structure
↓
Route to Affected LIGA™ Governance Space
↓
Reassess Materially Affected Governance
↓
Return Updated Liability Structure to LCFS
Governance Outputs
LREM may produce:
Re-Entry Object
Re-Entry Trigger Record
Re-Entry Basis
Re-Entry Materiality Assessment
Re-Entry Scope
Re-Entry Boundary
Affected Liability Relationship Record
Liability Network Re-Entry Record
Affected Prior Governance Record
Earliest Materially Affected Governance Space
Re-Entry Destination
Preserved Validity Record
Dependency Map
Required Reassessment Record
Re-Entry Authority Record
Re-Entry Condition Record
Re-Entry State
Re-Entry Temporal Record
Re-Entry Uncertainty Record
Re-Entry Conflict Record
Prior Resolution Association
Prior Discharge Association
Prior Finality Association
Reopening Record
Re-Entry Provenance
Re-Entry Rationale
The principal output is:
Governed Liability Re-Entry Structure
Critical Distinctions
LREM preserves the following distinctions:
Re-entry must not rewrite history Re-Entry Object ≠ Liability Object by default Re-Entry Trigger ≠ Liability Re-Entry Change ≠ Material Re-Entry Trigger by default Continued Liability Governance ≠ Re-Entry Re-Entry ≠ Reassessment Re-Entry ≠ Correction by default Re-entry ≠ New Liability by default Re-entry ≠ New Origin by default Liability Reopening ≠ New Liability by default Re-Entry ≠ Post-Finality Reopening only Post-Finality Re-Entry ≠ Historical Finality Deletion Re-Entry-Relevant Information ≠ Sufficient Re-Entry Basis by default Re-entry ≠ Full Lifecycle Restart by default Re-entry ≠ Automatic Invalidation of All Prior Governance Upstream Change ≠ Automatic Full Downstream Invalidation Relationship Re-Entry ≠ Liability Network Re-Entry by default Primary Liability Re-Entry ≠ Recourse Re-Entry by default Re-Entry Authority ≠ Liability Determination Authority by default Local Re-Entry Authority ≠ Universal Network Re-Entry Authority Unknown Re-Entry State ≠ No Re-Entry Required by assumption Re-Entry Trigger Time ≠ Re-Entry Effective Time by default Discovery Time ≠ Re-Entry Trigger Event Time by default New Evidence ≠ New Liability Determination Evidence Supporting Re-Entry ≠ Predetermined Reassessment Outcome Correction ≠ Historical Erasure Settlement Failure ≠ Automatic Restoration of Every Prior Liability State Resolution Reversal ≠ Resolution History Deletion Finality Reversal ≠ Finality History Deletion New Recourse Relationship ≠ Primary Liability Reopening by default Harm Reopening ≠ Liability Reopening by default Claim Reopening ≠ Liability Reopening Accountability Reopening ≠ Liability Reopening New Operational Event ≠ Existing Liability Re-Entry by default Later Liability State ≠ Historical State by retroactive substitution Conflicting Re-Entry Inputs ≠ Authority to Force Re-Entry Automated Re-Entry Trigger Detection ≠ Liability Re-Entry Re-Entry Completion ≠ Liability Finality
Cross-Architecture Boundary
LREM may receive Re-entry-relevant inputs from adjacent OOF® architectures.
ORA™ may establish new or changed Operational Reality.
HAGA™ may establish new Harm, Harm change, Harm Reopening, or revised Harm states.
AGA™ may establish changes in Responsibility, Accountability, attribution, or authority.
ADIT® may provide newly available evidence or audit findings.
VALIDOS™ may identify validation changes or failures.
OBIDENITY® may provide new identity, Origin, succession, provenance, or authority information.
VFM® may provide payment reversal, Transfer, or other Value Flow developments.
AIG® and ASGA™ may provide new AI or autonomous-system events.
Claims governance may identify Claim Reopening or Claim lifecycle changes.
These developments may create Liability Re-entry relevance.
They do not automatically reopen Liability.
The canonical interoperability principle is:
A change in an adjacent governance domain may create a Re-entry-relevant input, but LREM determines whether the existing Liability lifecycle itself requires renewed governance and where that governance must resume.
Canonical Boundary
LREM begins when a material development creates a legitimate question about whether an existing Liability governance state remains sufficient.
LREM governs:
Re-Entry Objects, Re-entry Triggers, materiality, Re-entry Basis, Liability Origin continuity, Subjects, Relationships, Liability Network relevance, Re-entry Scope, Re-entry Boundary, earliest materially affected governance space, Re-entry Destination, preserved validity, dependency propagation, reassessment Scope, Resolution and Discharge Re-entry, Finality Re-entry, Transfer and Recourse Re-entry, authority, conditions, Re-entry State, time, uncertainty, disputes, conflicts, historical integrity, Reopening, provenance, and Re-entry rationale.
LREM does not predetermine the outcome of the governance space to which the matter returns.
LREM does not automatically create a new Liability Origin.
LREM does not erase prior Resolution, Discharge, or Finality.
LREM ends when renewed governance has been sufficiently bounded and routed through a:
Governed Liability Re-Entry Structure
or when Re-entry has been assessed as not required.
Use Case 1 — New Evidence After Finality
A Liability Relationship previously reached a Governed Liability Finality State.
New materially relevant evidence later emerges that may affect the original Liability Determination.
LREM preserves the earlier Finality State, identifies the new evidence as a potential Re-entry Trigger, assesses its materiality, and determines that Liability Determination is the earliest materially affected governance space.
The matter is routed back to LDS for reassessment.
The prior Finality remains part of the historical record.
Re-entry must not rewrite history.
Use Case 2 — Settlement Failure Requires Limited Re-Entry
A Liability Relationship entered Resolution through a Settlement and was represented as conditionally discharged.
A material Settlement condition later fails.
The original Liability Basis, Relationships, Connection, Determination, Scope, and Allocation remain valid.
LREM therefore does not restart the complete LIGA™ lifecycle.
It routes the matter back to Liability Resolution & Discharge governance for targeted reassessment while preserving unaffected upstream governance.
Reassess what materially changed. Preserve what remains valid.
Canonical Closing Statement
Re-entry is not a failure of Finality governance.
It is the mechanism that prevents Finality from becoming an irreversible methodological error.
New information may emerge.
Conditions may fail.
Payments may reverse.
Settlements may collapse.
Relationships may become visible later.
And a previously valid Finality State may become insufficient under materially changed circumstances.
The answer is not to erase the earlier lifecycle.
The answer is to continue it.
Re-enter the earliest materially affected governance space.
Reassess what materially changed. Preserve what remains valid.
Re-entry must not rewrite history.