LSTIM — Liability State Identification Module
LSTIM — Liability State Identification 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 State Identification
Module ID: LIGA-LSCS-LSTIM-001
Origin ID: OOF.CM.LIGA.09.01.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 State Identification Module (LSTIM) governs how the current state of established Liability is identified, bounded, associated with the correct Liability structure, temporally situated, and represented as an explicit Governed Liability State.
LSTIM begins with a Governed Liability Scope & Allocation Structure and determines the operative state of the relevant Liability, Subject, Relationship, Scope portion, Allocation, obligation, or other governed Liability component at the applicable point or period in time.
It distinguishes the current Liability State from the earlier Liability Determination State, from historical states, and from states belonging to Claims, Harm, Responsibility, Accountability, Insurance, Payment, Settlement, or other adjacent governance objects.
LSTIM does not govern how the Liability State transitions.
It does not determine whether an identified change is legitimate.
It does not perform Liability Transfer, Recourse, Resolution, Discharge, or Finality governance.
It governs the transition:
Governed Liability Scope & Allocation Structure → State Object Identification → State Association → State Classification → Temporal State Identification → State Sufficiency → Governed Liability State Its foundational distinction is:
Liability Determination State ≠ Current Liability State.
Operational Role
The operational role of LSTIM is:
to establish what state the governed Liability is currently in, to which Liability structure that state applies, and when that state applies.
Before a system can govern State Transition or Liability Change, it must first establish the current state from which any transition would occur.
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 LSTIM governs:
Liability State Identification
Its principal input is:
Governed Liability Scope & Allocation Structure
Its principal output is:
Governed Liability State
Its handoff is:
Governed Liability State → LSTTM — Liability State Transition Module
Central Operational Question
What is the current governed state of this established Liability, to which Liability component does that state apply, and during what time is it operative?
State Identification Object
Every State Identification should begin by identifying exactly what Liability component requires a current state.
The State Identification Object may be:
the complete Liability Relationship, one Liability Subject's Liability, one Scope portion, one Allocation, one obligation, one temporal segment, one layer within a Liability Network, or another explicitly governed Liability component.
State Object Identity
The State Identification Object should possess sufficient identity to distinguish it from other Liability components.
Therefore:
Liability Matter ≠ State Identification Object by default.
Liability Origin Association
The identified state should remain linked to the Liability lifecycle from which it originates.
The state should not exist as an isolated status record.
Therefore:
Liability State without Lifecycle Origin ≠ Fully Governed Liability State.
Liability Determination Association
Every current Liability State should remain traceable to the Liability Determination establishing the Liability to which the state relates.
LSTIM does not redetermine Liability.
It establishes the current state of already determined Liability.
Scope Association
The current Liability State should remain associated with the applicable Governed Liability Scope.
A state should not silently extend beyond that Scope.
Therefore:
State Identification ≠ Scope Expansion.
Allocation Association
Where Liability has been allocated, the current state should remain associated with the applicable Governed Liability Allocation.
Different allocated portions may possess different states.
Subject Association
LSTIM should identify which Liability Subject the state concerns.
Therefore:
State of Subject A ≠ State of Subject B by default.
Relationship Association
A Subject may participate in multiple Liability Relationships.
The state should remain associated with the correct Relationship.
Therefore:
Subject State ≠ Universal Relationship State.
Basis Association
Where Liability exists under multiple Liability Bases, the state should remain Basis-specific where materially necessary.
Therefore:
State under Basis A ≠ State under Basis B by default.
Object Association
The Liability State should remain associated with the relevant Governed Liability Object.
A state concerning one Liability Object should not automatically apply to another.
Obligation Association
Where established Liability contains multiple obligations, each obligation may require an independently identifiable state.
Therefore:
One Liability Relationship ≠ One Obligation State by default.
Scope-Portion Association
Different Scope portions may possess different operative states.
LSTIM should preserve those distinctions rather than compressing them into one universal state.
Allocation-Portion Association
Where Allocation divides Liability across Subjects or Relationships, each allocated portion may possess its own state.
Therefore:
Shared Allocation ≠ Shared Liability State.
State Classification
LSTIM should classify the identified Liability State sufficiently for subsequent State Transition governance.
Possible state classes may include, where applicable:
Active, Inactive, Conditional, Suspended, Partially Active, Pending, Under Reassessment, Unknown, Uncertain, Disputed, Modified, Superseded, or another explicitly governed state.
These classifications are methodological states, not universal jurisdiction-specific legal statuses.
Active State
An Active state indicates that the applicable established Liability or Liability portion is presently operative under the governed structure.
Therefore:
Active Liability ≠ Enforced Liability.
Active does not automatically mean:
claimed, paid, admitted, enforced, or resolved.
Inactive State
An Inactive state indicates that the applicable Liability is not presently operative under the relevant state conditions.
Therefore:
Inactive Liability ≠ No Liability.
Conditional State
A Conditional state indicates that Liability operation depends upon an explicit governed condition.
The relevant condition should remain identifiable.
Therefore:
Conditional Liability ≠ Active Liability by default.
Suspended State
A Suspended state indicates that the operation of Liability has been temporarily interrupted under a governed basis.
Suspension does not erase the Liability.
Therefore:
Suspended Liability ≠ Discharged Liability.
Partially Active State
Where only part of the Liability is operative, LSTIM should represent the applicable active and non-active portions separately.
Therefore:
Partially Active Liability ≠ Fully Active Liability.
Pending State
A Pending state indicates that the current operative state depends upon a governance event, decision, process, or dependency that has not yet completed.
Therefore:
Pending Liability State ≠ Inactive Liability.
Under Reassessment State
Where an existing Liability State is undergoing legitimate reassessment, that status should remain explicit.
The prior state should not disappear merely because reassessment has begun.
Therefore:
Under Reassessment ≠ Prior State Erasure.
Unknown State
Where available governed information cannot establish the current state, the state should be represented as Unknown.
Therefore:
Unknown Liability State ≠ No Liability.
Uncertain State
Where multiple states remain materially plausible and the available governed information cannot support one sufficiently, the state should remain Uncertain.
Therefore:
Uncertain Liability State ≠ Authority to Select a Preferred State.
Disputed State
Where materially competing governed positions exist concerning the current state, LSTIM should preserve the dispute.
Therefore:
Disputed Liability State ≠ Unknown Liability State.
The state may be known to be disputed even when no final state is agreed.
Modified State
A Modified state may be used where the Liability remains operative but its applicable conditions, Scope-related effect, Allocation-related effect, obligation, or another material component has legitimately changed.
The underlying modification should remain traceable.
Superseded State
A Superseded state identifies a state that was previously operative but has been replaced by another legitimate state.
Therefore:
Superseded State ≠ Deleted State.
State Vocabulary Governance
Implementations may use additional state labels where required.
Each state should have:
a defined meaning, clear applicability, explicit boundaries, and an identifiable relationship to other states.
State labels should not be introduced merely for convenience.
No Universal State Vocabulary
LSTIM does not require every implementation or jurisdiction to use identical Liability State labels.
It requires the underlying state meaning to remain explicit and interoperable.
Therefore:
Different State Labels ≠ Different Liability State Meaning by default.
State Granularity
State identification should use the level of granularity required by the Liability structure.
A complex Liability should not be compressed into a single state where materially different components require different states.
Therefore:
One Status Label ≠ Complete Liability State Structure.
Complete-Liability State
Where the same state legitimately applies to the complete governed Liability structure, a complete-Liability state may be represented.
This should not be assumed merely for administrative simplicity.
Component State
Where different components possess different states, each materially distinct component should remain separately represented.
State Composition
A complete Liability representation may consist of multiple component states.
The overall representation should preserve those component states rather than replacing them with a misleading single label.
Temporal Identification
Every current Liability State should be situated in time.
LSTIM should distinguish relevant temporal markers where necessary.
State Creation Time
State Creation Time identifies when the state record or governed representation was created.
It does not necessarily identify when the state became operative.
State Effective Time
State Effective Time identifies when the Liability State becomes or became operative.
Therefore:
State Creation Time ≠ State Effective Time by default.
State Observation Time
State Observation Time identifies when the state was observed, detected, or assessed.
Therefore:
State Observation Time ≠ State Effective Time by default.
State Recording Time
State Recording Time identifies when the state was entered into the relevant system or record.
Therefore:
State Recording Time ≠ State Effective Time by default.
State End Time
Where a Liability State ceases to be operative, the applicable end time should be identifiable where materially relevant.
Current State
The Current Liability State is the state that legitimately governs the applicable Liability component at the relevant present governance point.
The newest record is not automatically the current state.
Therefore:
Latest Record ≠ Current Governed Liability State by default.
Historical State
A state that applied previously should remain identifiable as a Historical Liability State.
Historical does not mean invalid.
The state may have been fully correct during its applicable period.
Future State
A future state may be scheduled, anticipated, conditional, or otherwise represented.
It should not be treated as currently operative until its governing conditions are satisfied.
Therefore:
Scheduled Future State ≠ Current Liability State.
State Duration
Where materially relevant, LSTIM should identify the duration for which a state has applied or is expected to apply.
Duration does not itself establish a State Transition.
State Dependency
A Liability State may depend upon:
a Liability Condition, an obligation, a Scope state, an Allocation state, an authority decision, a temporal event, another Liability Relationship, or another governed dependency.
Material dependencies should remain explicit.
Conditional Dependency
Where a state is conditional upon another governed state, LSTIM should identify the dependency rather than representing the state as unconditional.
External Dependency
An external governed state may affect Liability State.
Its existence does not transfer governance ownership of the external domain to LIGA™.
State Evidence Association
Evidence may support State Identification.
Evidence should remain associated with the state without becoming the state itself.
Therefore:
Evidence of Liability State ≠ Liability State.
State Authority Association
Where a state depends upon an authoritative decision or determination, the relevant authority should remain identifiable.
Therefore:
Authority Record ≠ Liability State by itself.
State Source
The source from which the state is identified should remain traceable where materially relevant.
Possible sources may include:
governed system state, authoritative decision, validated operational information, contractual state, institutional record, or another legitimate source.
Multiple State Sources
Different sources may report different states.
LSTIM should preserve materially conflicting source states rather than silently selecting one.
State Conflict
A State Conflict exists where materially relevant governed sources or authorities indicate incompatible current states.
Therefore:
Conflicting State Records ≠ One Governed State by default.
State Priority
Where one state legitimately governs over another, the basis for that priority should be explicit.
Chronological recency alone is insufficient.
Therefore:
Latest State ≠ Governing State by default.
State Sufficiency
A Liability State is sufficiently identified when a qualified downstream process can determine:
what Liability component the state concerns, what the state means, to whom and to what Relationship it applies, when it applies, what Scope and Allocation it relates to, what dependencies remain, what uncertainty exists, and where the state originated.
State Completeness
State Identification is complete when all materially necessary current Liability components possess an explicit state or an explicit unresolved state.
Completeness does not require artificial certainty.
Therefore:
State Identification Completeness ≠ Universal State Certainty.
State Uncertainty
Where state uncertainty exists, it should be represented as part of the Governed Liability State.
It should not be hidden in narrative notes or omitted from machine-readable state.
State Confidence
Where an implementation uses confidence or reliability indicators, those indicators should remain separate from the state itself.
Therefore:
State Confidence ≠ Liability State.
State Rationale
Where necessary, the reason supporting the identified state should be reconstructable.
Therefore:
State Label ≠ State Rationale.
State Provenance
LSTIM should preserve sufficient provenance to identify:
where the state came from, which Liability structure it concerns, which inputs support it, which authority applies, and which prior state preceded it where applicable.
State Traceability
A qualified reviewer should be able to trace:
Liability Determination → Governed Scope & Allocation → State Identification Object → Current Liability State without reconstructing the matter from raw information.
State Integrity
A State Identification should not:
create new Liability, expand Scope, change Allocation, erase unresolved states, collapse distinct Relationships, or rewrite historical Liability.
No Determination Shortcut
The state of Liability cannot substitute for Liability Determination.
Therefore:
Active State ≠ Proof of Original Liability Attachment.
The Attachment must remain traceable to LDS.
No Scope Shortcut
A current state should not be used to enlarge or narrow Liability Scope.
Therefore:
State Classification ≠ Scope Determination.
No Allocation Shortcut
A state should not be used to redistribute Liability.
Therefore:
State Identification ≠ Liability Reallocation.
No Harm-State Shortcut
A Harm state should not automatically become the Liability State.
Therefore:
Harm State ≠ Liability State.
No Responsibility-State Shortcut
A Responsibility state does not automatically establish the Liability State.
Therefore:
Responsibility State ≠ Liability State.
No Accountability-State Shortcut
An Accountability state does not automatically establish the Liability State.
Therefore:
Accountability State ≠ Liability State.
No Claim-State Shortcut
A Claim may be Open, Accepted, Rejected, Paid, Closed, or Reopened.
Those states should not automatically become Liability States.
Therefore:
Claim State ≠ Liability State.
No Payment-State Shortcut
Payment may be relevant to downstream Liability governance.
It does not automatically define the current Liability State.
Therefore:
Payment State ≠ Liability State by default.
No Settlement-State Shortcut
Settlement status should remain distinct from substantive Liability State.
Therefore:
Settlement State ≠ Liability State by default.
No Insurance-State Shortcut
Insurance status does not automatically define the state of underlying Liability.
Therefore:
Insurance State ≠ Liability State.
No Operational-State Shortcut
The state of an underlying operational mechanism, contract, system, service, or activity does not automatically determine Liability State.
Therefore:
Operational State ≠ Liability State by default.
Operational Termination
Termination of the underlying activity or mechanism does not automatically make Liability Inactive, Resolved, Discharged, or Final.
Therefore:
Operational Termination ≠ Liability Termination.
Automated State Identification
AI or automated systems may assist in State Identification where appropriately governed.
The system should preserve:
input states, methodology, system identity, authority, time, uncertainty, and provenance.
Therefore:
Automated State Identification ≠ Authoritative Liability State by default.
State Identification Change
The identified current state may later change because:
new information becomes available, a dependency changes, a prior state was incorrect, a legitimate transition occurs, or an upstream governance structure changes.
Such change belongs to subsequent LSCS governance rather than being silently rewritten inside State Identification.
State Identification Correction
Where the identified state itself was recorded incorrectly, it may require correction.
The previous record should remain historically reconstructable.
Therefore:
State Identification Correction ≠ Historical Erasure.
State Identification Reassessment
Where the original state identification was legitimate but circumstances changed, reassessment may be required.
Therefore:
State Identification Reassessment ≠ State Identification Correction.
Re-Entry to Scope & Allocation
Where State Identification reveals that the Governed Liability Scope or Allocation is insufficient, inconsistent, or outdated, the matter should return to LSAS.
LSTIM must not repair Scope or Allocation by manipulating the state.
Re-Entry to Liability Determination
Where State Identification reveals a material issue concerning whether Liability attaches, the matter should return to LDS.
Therefore:
State Identification ≠ Determination Correction.
Earlier Lifecycle Re-Entry
Where the issue originates earlier in LIGA™, governance should return to the earliest materially affected governance space.
The canonical rule is:
Re-enter the earliest materially affected governance space.
Historical Integrity
State Identification must preserve the distinction between:
current state, historical state, superseded state, corrected state, and unresolved state.
Therefore:
Current Liability State ≠ Complete Liability State History.
Governed Liability State
The principal output of LSTIM is:
Governed Liability State
It should identify, where applicable:
State Identity, State Identification Object, Liability Origin, Liability Determination reference, Subject, Relationship, Object, Basis, Scope, Allocation, obligation, state classification, state applicability, effective time, duration, dependencies, authority, source, uncertainty, conflict, rationale, provenance, and historical association.
Meaning of the Output
A Governed Liability State means that the operative state of the relevant established Liability has been sufficiently identified for State Transition governance.
It does not mean that a transition has occurred.
Therefore:
Governed Liability State ≠ Liability State Transition.
Handoff to Liability State Transition
LSTIM hands the:
Governed Liability State
to:
LSTTM — Liability State Transition Module
The next governance question becomes:
Under what governed conditions may this Liability move from its current state to another state?
The boundary is explicit:
LSTIM identifies the current Liability State.
LSTTM governs transition between Liability States.
Minimum Implementation Framework
A conforming implementation of LSTIM must provide exactly the following eight capabilities:
State Identification Object & Lifecycle Association
Capability to identify the Liability component requiring State Identification and associate it with its Liability Origin, Determination, Scope, Allocation, Subject, Relationship, Object, and Basis.
Liability State Classification Governance
Capability to identify and represent Active, Inactive, Conditional, Suspended, Partially Active, Pending, Under Reassessment, Unknown, Uncertain, Disputed, Modified, Superseded, or other explicitly governed Liability States without imposing a universal jurisdiction-specific vocabulary.
Subject, Relationship, Scope, Allocation & Obligation State Association
Capability to preserve materially distinct states across Liability Subjects, Relationships, Scope portions, Allocations, obligations, and other governed Liability components.
Temporal State Governance
Capability to distinguish State Creation Time, Effective Time, Observation Time, Recording Time, End Time, duration, historical state, current state, and future state where materially relevant.
Dependency, Source, Authority & Evidence Association
Capability to identify material state dependencies, sources, authority relationships, and evidence associations without confusing those inputs with the Liability State itself.
Unknown, Uncertain, Disputed & Conflicting State Governance
Capability to preserve unresolved or conflicting Liability States without forcing artificial classification or treating missing information as absence of Liability.
State Identification Integrity, Traceability, Correction & Re-Entry
Capability to preserve rationale, provenance, historical integrity, corrections, reassessments, and targeted re-entry to the earliest materially affected LIGA™ governance space.
State Transition Handoff Governance
Capability to produce a Governed Liability State sufficiently explicit, bounded, temporally situated, traceable, and historically connected for Liability State Transition governance.
Governance Logic
The canonical LSTIM governance logic is:
Governed Liability Scope & Allocation Structure
↓
Identify State Object
↓
Associate Liability Origin & Determination
↓
Associate Subject / Relationship / Object / Basis
↓
Associate Scope / Allocation / Obligation
↓
Identify State Classification
↓
Identify Temporal Applicability
↓
Identify Dependencies / Sources / Authority
↓
Identify Unknown / Uncertain / Disputed / Conflicting States
↓
Assess State Sufficiency
↓
Preserve Rationale / Provenance / History
↓
Governed Liability State
↓
Handoff to Liability State Transition
Governance Outputs
LSTIM may produce:
State Identification Object
Liability State Identity
Liability Origin Association
Liability Determination Association
Subject State Association
Relationship State Association
Object State Association
Basis State Association
Scope State Association
Allocation State Association
Obligation State Association
Liability State Classification
Active State Record
Inactive State Record
Conditional State Record
Suspended State Record
Partial State Record
Pending State Record
Under Reassessment State Record
Unknown State Record
Uncertain State Record
Disputed State Record
Modified State Record
Superseded State Record
State Effective Time
State Duration Record
State Dependency Record
State Source Record
State Authority Association
State Conflict Record
State Rationale
State Provenance Record
State Sufficiency State
The principal output is:
Governed Liability State
Critical Distinctions
LSTIM preserves the following distinctions:
Liability Determination State ≠ Current Liability State Liability Matter ≠ State Identification Object by default Liability State without Lifecycle Origin ≠ Fully Governed Liability State State Identification ≠ Scope Expansion State of Subject A ≠ State of Subject B by default Subject State ≠ Universal Relationship State State under Basis A ≠ State under Basis B by default One Liability Relationship ≠ One Obligation State by default Shared Allocation ≠ Shared Liability State Active Liability ≠ Enforced Liability Inactive Liability ≠ No Liability Conditional Liability ≠ Active Liability by default Suspended Liability ≠ Discharged Liability Partially Active Liability ≠ Fully Active Liability Pending Liability State ≠ Inactive Liability Under Reassessment ≠ Prior State Erasure Unknown Liability State ≠ No Liability Uncertain Liability State ≠ Authority to Select a Preferred State Disputed Liability State ≠ Unknown Liability State Superseded State ≠ Deleted State Different State Labels ≠ Different Liability State Meaning by default One Status Label ≠ Complete Liability State Structure State Creation Time ≠ State Effective Time by default State Observation Time ≠ State Effective Time by default State Recording Time ≠ State Effective Time by default Latest Record ≠ Current Governed Liability State by default Scheduled Future State ≠ Current Liability State Evidence of Liability State ≠ Liability State Authority Record ≠ Liability State by itself Conflicting State Records ≠ One Governed State by default Latest State ≠ Governing State by default State Identification Completeness ≠ Universal State Certainty State Confidence ≠ Liability State State Label ≠ State Rationale Active State ≠ Proof of Original Liability Attachment State Classification ≠ Scope Determination State Identification ≠ Liability Reallocation Harm State ≠ Liability State Responsibility State ≠ Liability State Accountability State ≠ Liability State Claim State ≠ Liability State Payment State ≠ Liability State by default Settlement State ≠ Liability State by default Insurance State ≠ Liability State Operational State ≠ Liability State by default Operational Termination ≠ Liability Termination Automated State Identification ≠ Authoritative Liability State by default State Identification Correction ≠ Historical Erasure State Identification Reassessment ≠ State Identification Correction State Identification ≠ Determination Correction Current Liability State ≠ Complete Liability State History Governed Liability State ≠ Liability State Transition
Cross-Architecture Boundary
LSTIM may use governed inputs from other OOF® architectures where those inputs are relevant to identifying Liability State.
HAGA™ may provide Harm states.
ORA™ may provide Operational Reality.
AGA™ may provide Responsibility and Accountability states.
ADIT® may provide evidence and auditability.
VALIDOS™ may provide validation states.
OBIDENITY® may provide identity, authority, provenance, ownership, and continuity information.
AIG® and ASGA™ may provide AI or autonomous-system states.
VFM® may provide Value Flow states.
PGA™ may provide Prediction states.
SIMULOS® may provide Simulation outputs.
Those states remain external governed objects.
The canonical interoperability principle is:
An external governed state may inform Liability State Identification without becoming the Liability State and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LSTIM begins with a:
Governed Liability Scope & Allocation Structure
and governs identification of the current Liability State.
LSTIM governs:
State Identification Object, State Identity, Liability Origin association, Determination association, Subject association, Relationship association, Object association, Basis association, Scope association, Allocation association, Obligation association, State Classification, State Granularity, Temporal State, State Dependencies, State Sources, State Authority association, State Uncertainty, State Conflict, State Rationale, State Provenance, State Sufficiency, State Identification correction, State Identification reassessment, Historical Integrity, and State Transition handoff.
LSTIM does not govern:
initial Liability Determination, Scope establishment, Allocation distribution, State Transition itself, Liability Change Assessment, Transfer, Recourse, Resolution, Discharge, or Finality.
LSTIM ends when a:
Governed Liability State
is sufficiently explicit and traceable for State Transition governance.
Use Case 1 — Multi-Party Industrial Liability State
Identification
An industrial incident has already produced a reconciled Liability Scope & Allocation Structure involving an operator and a maintenance provider.
LSTIM identifies the current state of each governed Liability portion.
The operator's repair obligation is Active.
A separate allocated portion involving the maintenance provider remains Conditional.
Another portion is Disputed.
LSTIM preserves these states separately rather than representing the entire incident through one status such as “Open.” Each state remains connected to its Subject, Relationship, Scope, Allocation, effective time, and Liability Determination.
The resulting Governed Liability States are ready for State Transition governance.
Use Case 2 — Autonomous System Liability State
Identification
An autonomous system deployment contains several established Liability Relationships.
The system has been deactivated, but the underlying Liability relationships remain governed independently.
LSTIM identifies one Liability portion as Active, another as Under Reassessment, and a third as Pending because a governed dependency remains unresolved.
The system's operational state is not converted automatically into Liability State.
The module therefore preserves the distinction:
Operational Termination ≠ Liability Termination.
The resulting Governed Liability States provide explicit starting states for subsequent transition governance.
Canonical Closing Statement
Liability cannot change coherently unless its current state is first known.
That state must belong to the correct Liability, Subject, Relationship, Scope, Allocation, obligation, and time.
It must remain distinguishable from Harm, Responsibility, Accountability, Claims, Payment, Insurance, Settlement, and Operational State.
And it must remain connected to the Liability history from which it emerged.
Liability Determination establishes that Liability exists. State Identification establishes what condition that Liability is in now.
Identify the state before governing its transition.