LIGA™ Complete Standards & Modules Index

Liability Governance Architecture — Liability Governance Layer

Official Liability Governance Architecture Map for Individuals, Groups, Organizations, Physical and Digital Objects, AI Systems, Autonomous Systems,

Infrastructure, Environments, Institutions, Networks, and Future Operational Systems

This document serves as the official OOF® Liability Governance architecture map and structural index used for Liability Governance design, Liability Lifecycle navigation, Liability diagnostics, architecture development, Liability Governance assessment, lifecycle governance, Liability state analysis, Liability Resolution and Finality governance, and interoperability across individuals, groups, organizations, physical and digital objects, AI systems, autonomous systems, infrastructure, environments, institutions, networks, and future operational systems.

LIGA™ consists of 12 Parent Standards and 60 Core Modules.

Additional standards and modules may be added when new governable Liability spaces are identified. However, the standards and modules listed below form the core structural backbone of LIGA™.

Liability Context Standard (LCS)

Governed Space: Liability Context

Core Question: Within what context can Liability meaningfully exist and become governable?

Modules:

LCIM — Liability Context Identification Module

LCBM — Liability Context Boundary Module

LCEM — Liability Context Environment Module

LCTM — Liability Context Temporal Module

LCCM — Liability Context Continuity Module

Liability Object Standard (LOS)

Governed Space: Liability Object Governance

Core Question: What exactly is the governed matter in relation to which Liability is being considered?

Modules:

LOIM — Liability Object Identification Module

LOBM — Liability Object Boundary Module

LODM — Liability Object Distinction Module

LORM — Liability Object Representation Module

LOCM — Liability Object Continuity Module

Liability Basis Standard (LBS)

Governed Space: Liability Basis

Core Question: On what governed basis can Liability potentially exist?

Modules:

LBIM — Liability Basis Identification Module

LBCM — Liability Basis Classification Module

LBQM — Liability Basis Qualification Module

LBAM — Liability Basis Association Module

LBCOM — Liability Basis Continuity Module

Liability Relationship Standard (LRS)

Governed Space: Liability Subjects & Relationships

Core Question: Who or what participates in the potential Liability structure, and what Liability-relevant relationships exist between them?

Modules:

LSUIM — Liability Subject Identification Module

LRIM — Liability Relationship Identification Module

LRMM — Liability Relationship Mapping Module

LRDM — Liability Relationship Distinction Module

LRCM — Liability Relationship Continuity Module

Liability Conditions Standard (LCOS)

Governed Space: Liability Conditions

Core Question: What conditions must exist, fail, change, or be satisfied for potential Liability to proceed toward determination under the applicable Liability Basis?

Modules:

LCNIM — Liability Condition Identification Module

LCNRM — Liability Condition Requirement Module

LCNSM — Liability Condition State Module

LCNXM — Liability Condition Exception Module

LCNCM — Liability Condition Continuity Module

Liability Connection Standard (LCNS)

Governed Space: Liability-Relevant Connection

Core Question: What sufficiently governed connection exists between the relevant Liability Subject, Liability Object, conditions, conduct, and other Liability-relevant inputs?

Modules:

LCXIM — Liability Connection Identification Module

LCXRM — Liability Connection Relationship Module

LCXCM — Liability Connection Chain Module

LCXQM — Liability Connection Qualification Module

LCXEAM — Liability Connection Evidence Association Module

Liability Determination Standard (LDS)

Governed Space: Liability Determination & Attachment

Core Question: Can Liability legitimately attach and be determined to exist on the established governed basis?

Modules:

LDIM — Liability Determination Input Module

LDEM — Liability Determination Evaluation Module

LDAM — Liability Determination & Attachment Module

LDRM — Liability Determination Rationale Module

LDVM — Liability Determination Versioning Module

Liability Scope & Allocation Standard (LSAS)

Governed Space: Liability Scope & Allocation

Core Question: For what and to what extent does established Liability apply, and how is that Liability distributed where multiple Liability relationships exist?

Modules:

LSCIM — Liability Scope Identification Module

LSCBM — Liability Scope Boundary Module

LALIM — Liability Allocation Identification Module

LALDM — Liability Allocation Distribution Module

LSARM — Liability Scope & Allocation Reconciliation Module

Liability State & Change Standard (LSCS)

Governed Space: Liability State & Change

Core Question: What is the current governed state of Liability, and how may that state legitimately change?

Modules:

LSTIM — Liability State Identification Module

LSTTM — Liability State Transition Module

LCHIM — Liability Change Identification Module

LCHAM — Liability Change Assessment Module

LSTHM — Liability State History Module

Liability Transfer & Recourse Standard (LTRS)

Core Question: How may Liability or its consequences move, be shared, redistributed, recovered, succeeded, or create secondary Liability Relationships?

Modules:

LTFIM — Liability Transfer Identification Module

LSHRM — Liability Sharing Module

LREIM — Liability Recourse Identification Module

LRENM — Liability Recourse Network Module

LTFCM — Liability Transfer Continuity Module

Liability Resolution & Discharge Standard (LRDS)

Governed Space: Liability Resolution & Discharge

Core Question: Under what governed conditions may active Liability be resolved, satisfied, discharged, extinguished, or otherwise cease requiring active performance or governance?

Modules:

LRSIM — Liability Resolution Initiation Module

LSATM — Liability Satisfaction Module

LSETM — Liability Settlement Module

LDCHM — Liability Discharge Module

LRVFM — Liability Resolution Verification Module

Liability Continuity & Finality Standard (LCFS)

Governed Space: Liability Continuity, Re-Entry & Finality

Core Question: How must Liability remain continuous and reconstructable, when may a Liability Relationship or Liability Network legitimately reach finality, and under what conditions must governed re-entry occur?

Modules:

LCOIM — Liability Continuity Identification Module

LHRM — Liability Historical Record Module

LFAM — Liability Finality Assessment Module

LREM — Liability Re-Entry Module

LFRM — Liability Finality Record Module

LIGA™ Architecture Summary

Parent Standards: 12

Core Modules: 60

Core Governed Liability Spaces

Liability Context

Liability Object

Liability Basis

Liability Relationships

Liability Conditions

Liability Connection

Liability Determination

Liability Scope & Allocation

Liability State & Change

Liability Transfer & Recourse

Liability Resolution & Discharge

Liability Continuity & Finality

Core Questions Map

LCS → Within what context can Liability meaningfully exist and become governable?

LOS → What exactly is the governed matter in relation to which Liability is being considered?

LBS → On what governed basis can Liability potentially exist?

LRS → Who or what participates in the potential Liability structure, and what Liability-relevant relationships exist between them?

LCOS → What conditions must exist, fail, change, or be satisfied for potential Liability to proceed toward determination under the applicable Liability Basis?

LCNS → What sufficiently governed connection exists between the relevant Liability Subject, Liability Object, conditions, conduct, and other Liability-relevant inputs?

LDS → Can Liability legitimately attach and be determined to exist on the established governed basis?

LSAS → For what and to what extent does established Liability apply, and how is that Liability distributed where multiple Liability relationships exist?

LSCS → What is the current governed state of Liability, and how may that state legitimately change?

LTRS → How may Liability or its consequences move, be shared, redistributed, recovered, succeeded, or create secondary Liability Relationships?

LRDS → Under what governed conditions may active Liability be resolved, satisfied, discharged, extinguished, or otherwise cease requiring active performance or governance?

LCFS → How must Liability remain continuous and reconstructable, when may a Liability Relationship or Liability Network legitimately reach finality, and under what conditions must governed re-entry occur?

Architectural Position

LIGA™ governs the complete Liability Governance lifecycle from Liability-relevant Context and Liability Object formation through Liability Resolution, Discharge, Continuity, Re-Entry, and Finality.

The architecture progresses:

Liability Context → Liability Object → Liability Basis → Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Scope & Allocation → Liability State & Change → Liability Transfer & Recourse → Liability Resolution & Discharge → Liability Continuity & Finality Together these standards govern the context in which Liability may become relevant, what exact matter forms the Liability Object, on what Basis Liability may potentially exist, which Subjects and Relationships participate in the Liability structure, what Conditions must exist or be satisfied, what Liability-Relevant Connection exists, whether Liability can legitimately attach and be determined, for what and to what extent Liability applies, how Liability is allocated, what its current State is and how it changes, how Liability or its consequences may move or create secondary and Recourse Relationships, when active Liability may be resolved or discharged, and when the Liability lifecycle can legitimately reach Finality while remaining historically reconstructable and capable of governed Re-Entry.

Its complete lifecycle progresses:

Potential Liability → Attached / Determined Liability → Active Liability Governance → Liability Change → Transfer / Recourse where applicable → Resolution / Discharge → Continuity / Re-Entry where required → Finality Liability Determination therefore does not complete the Liability lifecycle.

Liability Determination ≠ Liability Lifecycle Completion.

Where material Liability conditions or information change:

Governed Liability → Liability State Change → Scope / Allocation Change where applicable → Transfer / Recourse where applicable → Resolution / Discharge → Finality Assessment Where Resolution or Discharge is sufficient and terminal conditions are established:

Resolution / Discharge → Continuity & Historical Reconstruction → Finality Assessment → Finality Record →

Governed Liability Finality State

Where material information, conditions, events, corrections, reversals, conflicts, or other developments require renewed governance:

Resolution / Finality → Re-Entry → Earliest Materially Affected LIGA™ Governance Space → Renewed Liability Governance → Resolution / Discharge → Continuity & Finality This recursive structure allows Liability Governance to remain responsive to Liability State change, Scope change, Allocation change, new or changed Relationships, Transfer, Sharing, succession, Recourse, failed Resolution conditions, payment reversal, Settlement failure, new materially relevant information, correction, Reassessment, Reopening, and legitimate post-Finality Re-Entry.

Re-enter the earliest materially affected governance space.

Reassess what materially changed. Preserve what remains valid.

Re-entry must not rewrite history.

Cross-Architecture Boundary

LIGA™ ↔ ORA™

ORA™ governs what is actually occurring in Operational Reality. LIGA™ governs whether and how that Operational Reality becomes relevant to Liability and what Liability state results from the complete governed Liability lifecycle.

Operational Reality ≠ Liability.

Operational Causation ≠ Liability-Relevant Connection.

LIGA™ ↔ HAGA™

HAGA™ governs the Harm lifecycle. LIGA™ governs the Liability lifecycle.

Harm may provide Liability-relevant input where applicable, but Harm is not a universal prerequisite for Liability.

Harm ≠ Liability.

Harm Determination ≠ Liability Determination.

Harm Resolution ≠ Liability Resolution.

Harm Finality ≠ Liability Finality.

LIGA™ ↔ AGA™

LIGA™ governs Liability. AGA™ governs authority, responsibility, accountability, attribution, and related accountability relationships surrounding actions, decisions, omissions, systems, and consequences.

Responsibility ≠ Liability.

Accountability ≠ Liability.

Accountability Attribution ≠ Liability Allocation.

LIGA™ ↔ ADIT®

LIGA™ governs Liability and its lifecycle states. ADIT® governs evidential observation, preservation, verification, correlation, examination, and auditability.

Evidence of Liability-Relevant Facts ≠ Liability Determination.

LIGA™ ↔ VALIDOS™

LIGA™ governs Liability Determination and subsequent Liability lifecycle governance. VALIDOS™ governs whether a validation basis sufficiently supports a Validation Determination and intended reliance.

Validation Determination ≠ Liability Determination.

LIGA™ ↔ INTEGROS®

LIGA™ governs Liability as a distinct lifecycle object. INTEGROS® governs integrity across objects, states, evidence, and processes.

Liability Governance ≠ General Integrity Governance.

LIGA™ ↔ OBIDENITY®

LIGA™ governs Liability Subjects and Liability Relationships. OBIDENITY® governs Origin, Identity, Ownership, Authority, Permission, Responsibility, Provenance, Transfer, Continuity, and Auditability.

Identity ≠ Liability Subject Determination.

Identity Continuity ≠ Liability Continuity by itself.

LIGA™ ↔ AIG®

LIGA™ governs Liability that may arise in relation to AI behavior. AIG® governs AI behavioral governance and behavioral integrity.

AI Behavior ≠ Liability.

AI Behavioral Failure ≠ Liability Determination.

LIGA™ ↔ ASGA™

LIGA™ governs Liability that may arise in relation to autonomous operation. ASGA™ governs autonomous-system authority, execution, constraints, coordination, intervention, escalation, and operational governability.

Autonomous Action ≠ Liability.

Autonomous-System Failure ≠ Liability Determination.

LIGA™ ↔ VFM®

LIGA™ governs what Liability exists and what happens to that Liability throughout its lifecycle. VFM® governs what happens to Value as a consequence of events and conditions.

Value Loss ≠ Liability.

Payment ≠ Liability Admission.

Value Transfer ≠ Liability Transfer by default.

LIGA™ ↔ SIMULOS®

LIGA™ governs actual Liability. SIMULOS® governs simulation purpose, structure, execution, outputs, and lifecycle.

Simulated Liability ≠ Actual Liability.

Simulated Liability Determination ≠ Governed Liability Determination.

LIGA™ ↔ Claims Systems

LIGA™ governs Liability. Claims systems govern Claims, Claim processing, Claim decisions, Claim administration, and related Claim lifecycle activities.

Claim ≠ Liability.

Claim Acceptance ≠ Liability Determination.

Claim Rejection ≠ Absence of Liability.

Claim Payment ≠ Liability Admission.

Claim Closure ≠ Liability Finality.

LIGA™ ↔ Liability-Relevant Mechanisms

LIGA™ governs the Liability lifecycle. Human actions, AI behavior, autonomous actions, physical interactions, organizational processes, contractual events, system failures, environmental conditions, Harm, loss, and composite operations may constitute or contribute to inputs through which Liability relevance may arise.

Liability-Relevant Mechanism ≠ Liability.

Liability Relationship & Network Structure

LIGA™ does not assume that one Liability-relevant event creates one Liability Relationship.

A single occurrence may produce:

multiple Liability Subjects multiple Liability Relationships different Liability Bases different Liability Conditions different Liability-Relevant Connections different Liability Determinations different Liability Scopes different Liability Allocations shared Liability transferred Liability secondary Liability Relationships

Recourse Relationships

or:

a wider Liability Network Each Relationship may possess its own lifecycle while remaining structurally connected to the wider Liability Network.

Therefore:

One Occurrence ≠ One Liability Relationship.

One Harm ≠ One Liability Relationship.

One Liability Subject ≠ One Liability Relationship.

One Liability Relationship ≠ Complete Liability Network.

Local Liability Resolution ≠ Liability Network Resolution.

Liability Relationship Finality ≠ Liability Network Finality.

Transfer & Recourse Structure

Liability may continue beyond the original Relationship through:

Transfer

Sharing

Succession

Contribution

Indemnification

Insurance-related structures

Recovery

Recourse

or another legitimate secondary Liability structure.

The architecture therefore preserves the distinction:

Harm-Producing Actor ≠ Liability-Bearing Party ≠ Paying Party.

A Transfer or Recourse Relationship does not automatically rewrite the original Liability Relationship.

Transfer ≠ Historical Replacement.

Primary Liability ≠ Recourse Liability.

Primary Liability Resolution ≠ Recourse Resolution.

Primary Liability Finality ≠ Recourse Finality.

Continuity, Re-Entry & Finality Structure

LIGA™ requires Liability to remain historically reconstructable across its complete lifecycle.

A Liability lifecycle may contain:

Context formation Liability Object formation Basis establishment Relationship formation Condition change Connection establishment

Determination

Attachment

Scope

Allocation

State change

Transfer

Sharing

Recourse

Resolution

Discharge

Finality Assessment

Finality

Re-Entry

Reopening

and:

renewed Finality These transitions must remain connected to the same Liability Origin where the same Liability lifecycle continues.

Current Liability State ≠ Complete Liability History.

Representation Change ≠ Liability Identity Change by default.

System Migration ≠ New Liability Origin.

Supersession ≠ Historical Deletion.

Correction ≠ Historical Erasure.

Reassessment ≠ Correction.

Re-entry ≠ New Origin by default.

Re-entry must not rewrite history.

Finality ends active Liability governance. It does not erase Liability history.

Foundational Architecture Distinctions

Liability Governance ≠ Governance of the Liability-Relevant Mechanism Liability Relevance ≠ Liability Liability Object ≠ Harm by Default Liability Object ≠ Claim by Default Liability Basis ≠ Liability Conditions Liability Basis ≠ Liability Attachment Liability Conditions ≠ Liability Determination Operational Causation ≠ Liability-Relevant Connection Factual Connection ≠ Liability-Relevant Connection by Default Liability-Relevant Connection ≠ Liability Determination Potential Liability ≠ Attached Liability Liability Determination ≠ Liability Scope Liability Scope ≠ Liability Allocation Responsibility ≠ Liability Accountability ≠ Liability Fault ≠ Liability Breach ≠ Liability Damage ≠ Liability Loss ≠ Liability Claim ≠ Liability Claim Acceptance ≠ Liability Determination Claim Rejection ≠ Absence of Liability Claim Payment ≠ Liability Admission Claim Closure ≠ Liability Finality Payment ≠ Admission of Liability Settlement ≠ Admission of Liability Harm ≠ Liability Harm Determination ≠ Liability Determination Liability Subject ≠ Harm-Producing Actor Liability-Bearing Party ≠ Paying Party Primary Liability ≠ Recourse Liability One Harm ≠ One Liability Relationship One Occurrence ≠ One Liability Relationship One Liability Subject ≠ One Liability Relationship One Liability Relationship ≠ Complete Liability Network Liability Determination at T1 ≠ Liability State at T2 Liability Change ≠ New Liability by Default Transfer ≠ Historical Replacement Current Liability State ≠ Complete Liability History Liability Resolution ≠ Liability Finality Harm Resolution ≠ Liability Resolution Harm Finality ≠ Liability Finality Relationship Resolution ≠ Network Resolution Relationship Finality ≠ Network Finality Primary Liability Finality ≠ Recourse Finality Resolution Basis ≠ Finality Basis by Default Closure Signal ≠ Liability Finality Administrative Closure ≠ Liability Finality Record Absence ≠ Liability Finality Re-Entry Trigger ≠ Liability Re-Entry Re-Entry ≠ Full Lifecycle Restart by Default Re-Entry ≠ New Liability by Default Re-Entry ≠ New Origin by Default Reopening ≠ New Liability by Default Re-entry must not rewrite history Liability Finality ≠ Liability Erasure

Canonical Principle

LIGA™ does not determine jurisdiction-specific legal liability, replace courts, regulators, arbitrators, insurers, contractual authorities, Claims systems, or legal decision systems, govern Harm itself, allocate general accountability, perform general incident or causation investigation, perform evidence governance, make validation determinations, determine Value consequences, or substitute for legal, regulatory, insurance, contractual, safety, medical, or other domain-specific decision systems. LIGA™ governs the methodological conditions under which Liability becomes contextually identifiable, object-bounded, basis-grounded, relationally structured, condition-aware, sufficiently connected, determinable and attachable where justified, scoped, allocatable, state-governed, traceable through change, transferable or recoverable through Recourse where applicable, legitimately resolvable and dischargeable, historically continuous, reopenable where materially required, and capable of reaching governed Finality throughout its complete lifecycle.

Liability may become relevant without Harm, may involve multiple Relationships arising from one occurrence, may change after Determination, may move between Subjects, may create secondary and Recourse Relationships, may remain active after payment or Settlement, may reach Relationship Finality while the wider Liability Network remains active, and may require Re-Entry after previous Resolution or Finality. LIGA™ provides the governance architecture for that entire lifecycle.

LIGA™ governs Liability from relevance to Finality.