LIGA™ Liability Governance Architecture — Liability Governance Layer
Liability Governance Architecture — Liability Governance Layer
Official Liability Governance Architecture for Individuals, Groups, Organizations, Physical and Digital Objects, AI Systems, Autonomous Systems, Infrastructure, Environments, Institutions, Networks, and Future Operational Systems
LIGA™ serves as the official OOF® Liability Governance architecture used for Liability Context governance, Liability Object governance, Liability Basis governance, Liability Relationship governance, Liability Conditions governance, Liability Connection governance, Liability Determination & Attachment, Liability Scope & Allocation governance, Liability State & Change governance, Liability Transfer & Recourse governance, Liability Resolution & Discharge, and Liability Continuity, Re-Entry & Finality across individuals, groups, organizations, physical and digital objects, AI systems, autonomous systems, infrastructure, environments, institutions, networks, and future operational systems.
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 causation analysis, govern evidence, or replace validation and audit systems.
LIGA™ defines the governance architecture required to ensure that Liability becomes contextually identifiable, object-bounded, basis-grounded, relationally structured, condition-aware, sufficiently connected, determinable, 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 material circumstances require Re-entry, and capable of reaching governed Finality throughout its complete lifecycle.
LIGA™ consists of 12 Core Parent Standards and 60 Core Modules forming the primary Liability Governance backbone within the OOF® ecosystem.
Additional compatible standards, bridge standards, and specialized Liability Governance standards may extend the architecture when new Liability Governance spaces are identified. However, the standards listed below form the official core Liability Governance structure of LIGA™.
Canonical Definition
LIGA™ — Liability Governance Architecture is the OOF® reference governance architecture for governing Liability throughout its lifecycle, from Liability-relevant context and Liability Object formation through Liability Basis, Relationships, Conditions, Connection, Determination and Attachment, Scope and Allocation, active Liability State and Change, Transfer and Recourse, Resolution and Discharge, Continuity, Re-Entry where required, and Finality.
Core Question
Under what governed conditions can Liability arise, attach, be determined, scoped, allocated, changed, transferred, resolved, and legitimately reach finality?
Governance Flow
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 Parent Standards
Liability Context Standard (LCS)
Governed Space: Liability Context
Core Question: Within what context can Liability meaningfully exist and become governable?
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?
Liability Basis Standard (LBS)
Governed Space: Liability Basis
Core Question: On what governed basis can Liability potentially exist?
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?
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?
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?
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?
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?
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?
Liability Transfer & Recourse Standard (LTRS)
Governed Space: Liability Transfer, Sharing & Recourse
Core Question: How may Liability or its consequences move, be shared, redistributed, recovered, succeeded, or create secondary Liability Relationships?
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?
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?
Compatible OOF® Architectures
LIGA™ interoperates with multiple OOF® architectures governing complementary spaces surrounding Liability.
GOA™ — Governance Architecture provides the constitutional governance layer defining how governance itself is structured, bounded, delegated, validated, and maintained.
ORA™ — Operational Reality Architecture governs what is actually occurring in Operational Reality, while LIGA™ governs whether and how that reality becomes relevant to the formation, determination, state, transfer, resolution, and Finality of Liability.
HAGA™ — Harm Governance Architecture governs Harm throughout its independent lifecycle, while LIGA™ governs Liability that may arise in relation to Harm without treating Harm itself as Liability or requiring Harm as a universal prerequisite for Liability.
AGA™ — Accountability Governance Architecture governs Responsibility, Accountability, attribution, authority, and related accountability structures, while LIGA™ governs Liability independently from whether Accountability alone has been established.
AIG® — AI Governance Architecture governs AI behavioral integrity and behavioral governance, while LIGA™ governs Liability Relationships that may arise around AI behavior without becoming an architecture for AI behavior itself.
ASGA™ — Autonomous Systems Governance Architecture governs autonomous-system identity, authority, execution, constraints, coordination, intervention, escalation, and operational governability, while LIGA™ governs Liability that may arise around autonomous operation without treating autonomous action itself as Liability.
ADIT® — Continuous Audit & Evidence Governance Architecture governs evidential observation, preservation, correlation, verification, examination, and auditability, while LIGA™ determines what sufficiently governed Liabilityrelevant inputs mean within the Liability lifecycle.
VALIDOS™ — Validation Governance Architecture governs whether a validation basis sufficiently supports a Validation Determination, while LIGA™ governs Liability Determination and subsequent Liability lifecycle states supported by relevant validated information.
INTEGROS® — Integrity Governance Architecture governs integrity across objects, states, evidence, and processes, while LIGA™ governs Liability as a distinct lifecycle object.
OBIDENITY® — Origin-Bound Identity Governance Architecture governs Origin, Identity, Ownership, Authority, Permission, Responsibility, Provenance, Transfer, Continuity, and Auditability, while LIGA™ governs how identified Subjects and objects participate in Liability structures.
VFM® — Value Flow Mechanism governs what happens to Value as a consequence of events and conditions, while LIGA™ governs Liability and does not treat Value movement, Value loss, payment, or compensation as Liability by default.
SIMULOS® — Simulation Governance Architecture governs simulation purpose, structure, execution, outputs, and lifecycle, while LIGA™ governs actual Liability structures and does not treat simulated Liability outcomes as operational Liability Determinations by default.
LIGA™ serves as the common Liability Governance architecture supporting the broader OOF® ecosystem by ensuring that Liability becomes a governed lifecycle object rather than an undefined conclusion attached directly to Harm, loss, fault, breach, accountability, payment, Claim, or an operational event.
Architectural Position
LIGA™ governs the complete Liability Governance Lifecycle from Liability-relevant context and potential Liability formation to legitimate Resolution, Continuity, Re-Entry, and Finality.
The architecture progresses through:
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 the governed Liability Object is, the Basis under which Liability may potentially exist, which Subjects and Relationships participate, what Conditions must be satisfied, what Liability-Relevant Connection exists, whether Liability may legitimately attach and be determined, what its Scope is and how it is allocated, what its current State is and how it changes, how Liability or its consequences may move or create Recourse, when active Liability may be resolved or discharged, and when the Liability lifecycle may legitimately reach Finality while remaining historically reconstructable and capable of governed Re-Entry.
LIGA™ remains distinct from the events, mechanisms, Harm, losses, Claims, accountability structures, and evidence that may contribute inputs to Liability governance.
Human Action / AI Behavior / Autonomous Action / Process Failure / Physical Interaction / Contractual Event / Harm / Loss / Composite Operation → Liability-Relevant Inputs → Governed Liability Lifecycle under LIGA™ An event may create Liability relevance. It does not by itself establish Liability.
Harm may be relevant to Liability. Harm is not Liability.
LIGA™ governs Liability — not the operational mechanism, Harm lifecycle, Claim lifecycle, or accountability structure surrounding it.
Core Governed Liability Spaces
LIGA™ establishes twelve distinct governable Liability spaces:
Liability Context
→ within what operational, temporal, relational, institutional, contractual, technical, physical, digital, or other relevant context Liability may meaningfully exist.
Liability Object
→ what exact governed matter is being considered in relation to potential Liability.
Liability Basis
→ on what governed Basis Liability may potentially exist.
Liability Relationships
→ which Subjects participate and what Liability-relevant Relationships exist between them.
Liability Conditions
→ what conditions must exist, fail, change, or be satisfied for potential Liability to proceed toward Determination.
Liability Connection
→ what sufficiently governed connection exists between relevant Subjects, the Liability Object, conditions, conduct, events, and other Liability-relevant inputs.
Liability Determination
→ whether Liability can legitimately attach and be represented as determined Liability.
Liability Scope & Allocation
→ for what and to what extent Liability applies and how established Liability is distributed across applicable Relationships and Subjects.
Liability State & Change
→ what the current governed State of Liability is and how that State legitimately changes over time.
Liability Transfer & Recourse
→ how Liability or its consequences may move, be shared, redistributed, succeeded, recovered, or create secondary Liability Relationships.
Liability Resolution & Discharge
→ when active Liability may be satisfied, settled, discharged, extinguished, resolved, or otherwise cease requiring the same active performance or governance.
Liability Continuity & Finality
→ how Liability remains continuously identifiable and historically reconstructable, when Re-Entry is required, and when a Liability Relationship or Liability Network may legitimately reach governed Finality.
Each space answers a different methodological question.
Each can fail independently.
Their separation is therefore foundational to LIGA™.
Cross-Architecture Boundary Lock
LIGA™ is intentionally bounded to prevent duplication with adjacent OOF® architectures and external Liability-related systems.
LIGA™ ↔ ORA™
ORA™: What is actually occurring in Operational Reality?
LIGA™: Under what governed conditions does that reality become relevant to Liability, and what is the resulting Liability lifecycle state?
Operational Reality ≠ Liability.
Operational Causation ≠ Liability-Relevant Connection.
LIGA™ ↔ HAGA™
HAGA™: governs Harm.
LIGA™: governs Liability.
Harm may become a relevant input into Liability governance, but Harm neither universally requires Liability nor automatically establishes it.
Harm ≠ Liability.
Harm Determination ≠ Liability Determination.
Harm Resolution ≠ Liability Resolution.
Harm Finality ≠ Liability Finality.
LIGA™ ↔ AGA™
LIGA™: governs Liability.
AGA™: governs Responsibility, Accountability, attribution, authority, and related accountability structures.
Responsibility ≠ Liability.
Accountability ≠ Liability.
Accountability Attribution ≠ Liability Allocation.
LIGA™ ↔ ADIT®
LIGA™: governs whether Liability can be established and how that Liability progresses through its lifecycle.
ADIT®: governs evidential observation, preservation, verification, correlation, examination, and auditability.
Evidence of Liability-Relevant Facts ≠ Liability Determination.
LIGA™ ↔ VALIDOS™
LIGA™: governs Liability Determination and Liability lifecycle states.
VALIDOS™: governs whether a validation basis sufficiently supports a Validation Determination.
Validation Determination ≠ Liability Determination.
LIGA™ ↔ INTEGROS®
LIGA™: governs Liability as a lifecycle object.
INTEGROS®: governs integrity across objects, states, processes, and evidence.
Liability Governance ≠ General Integrity Governance.
LIGA™ ↔ OBIDENITY®
LIGA™: governs Liability Subjects and Liability Relationships.
OBIDENITY®: governs Origin-Bound 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 around AI behavior.
AIG®: governs AI behavior itself.
AI Behavior ≠ Liability.
AI Behavioral Failure ≠ Liability Determination.
LIGA™ ↔ ASGA™
LIGA™: governs Liability that may arise around 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™: What Liability exists and what is happening to that Liability?
VFM®: What happened to Value as a result of events and conditions?
Value Loss ≠ Liability.
Payment ≠ Liability Admission.
Value Transfer ≠ Liability Transfer by default.
LIGA™ ↔ SIMULOS®
LIGA™: governs actual Liability.
SIMULOS®: governs simulations and simulated conditions.
A simulation may model potential Liability or support Liability-related analysis, but:
Simulated Liability ≠ Actual Liability.
Simulated Liability Determination ≠ Governed Liability Determination.
Architectural Origin
LIGA™ evolved from the foundational methodological problem that Liability is frequently treated as a single conclusion rather than as a governed lifecycle.
Traditional processes may move directly from:
Event / Harm / Loss / Breach → Investigation → Liability → Payment / Settlement / Closure while the internal governance structure of Liability remains insufficiently separated.
This becomes increasingly inadequate where:
Liability relevance exists before Liability is determined the governed Liability Object is unclear multiple Liability Bases may potentially apply multiple Subjects participate in different Relationships Liability Conditions change over time operational causation and Liability-Relevant Connection are not equivalent Liability attaches only after governed Determination Scope differs from Allocation one occurrence creates multiple Liability Relationships Liability changes after Determination the party producing Harm differs from the party bearing Liability the Liability-bearing party differs from the paying party Transfer, Sharing, insurance, Indemnification, contribution, succession, or Recourse create secondary
Relationships
primary Liability resolves while Recourse continues a Liability Relationship resolves while the wider Liability Network remains active Resolution occurs without lifecycle Finality or:
new material information requires Re-Entry after previous Resolution or Finality LIGA™ therefore establishes Liability as an independent governed lifecycle object.
Its foundational lifecycle is:
Context → Object → Basis → Relationships → Conditions → Connection → Determination → Scope & Allocation → State & Change → Transfer & Recourse → Resolution & Discharge → Continuity & Finality
Architectural Structure
Architecture: LIGA™ — Liability Governance Architecture
Category: Governance & Enforcement
Subcategory: Liability Governance
Core Parent Standards: 12
Core Modules: 60
Architecture Model: Lifecycle-Based · Modular · Methodology-Neutral · Technology-Neutral
Primary Governance Domain: Liability Governance
The architecture deliberately separates governable spaces that can independently fail.
Liability may:
be considered outside a sufficiently established context; be attached to an incorrectly defined Liability Object; be asserted without a sufficient Liability Basis; collapse multiple Subjects or Relationships into one; proceed without the necessary Liability Conditions; confuse operational causation with Liability-Relevant Connection; be treated as attached before legitimate Determination; possess an incorrect or overbroad Scope; be incorrectly allocated between Subjects; change without its State transition being governed; be transferred without preserving the original Liability history; create Recourse without preserving the distinction between primary and secondary Liability; be treated as resolved merely because payment occurred; be treated as discharged while active requirements remain; be represented as Final because an administrative or Claim process closed; lose historical continuity across systems or Transfers; be reopened without preserving earlier Resolution or Finality; or remain indefinitely active because Finality was never methodologically defined.
LIGA™ treats these not as one generic liability management problem, but as distinct Liability Governance spaces requiring distinct methodological controls.
Complete Lifecycle Principle
LIGA™ does not treat Liability Determination as completion of the Liability lifecycle.
The complete lifecycle may proceed:
Potential Liability → Attached / Determined Liability → Active Liability Governance → Liability Change → Transfer / Recourse where applicable → Resolution / Discharge → Continuity / Re-Entry where required → Finality Liability may therefore continue materially after Determination.
During its lifecycle:
Liability Scope may change.
Liability Allocation may change.
Liability State may change.
Subjects and Relationships may change.
Liability may be transferred or shared.
Secondary Liability Relationships may arise.
Recourse may arise after primary Liability has already been determined.
Primary Liability may resolve while Recourse continues.
A Liability Relationship may reach Resolution while the Liability Network remains active.
Resolution or Discharge may occur before Finality.
New material information may require Re-Entry.
A previously Final Liability may legitimately reopen.
The lifecycle may therefore proceed:
Determined Liability → Scope & Allocation → Active Liability State → Change → Transfer / Recourse → Resolution / Discharge → Finality Assessment → Finality and where material circumstances require renewed governance:
Resolution / Finality → Re-Entry → Earliest Materially Affected LIGA™ Governance Space → Renewed Governance → Resolution / Discharge → Finality Liability Determination ≠ Liability Lifecycle Completion.
Liability Resolution ≠ Liability Finality.
Re-entry must not rewrite history.
Finality does not erase Liability history.
Recursive Lifecycle Principle
LIGA™ does not assume that Liability progresses through its lifecycle only once.
A governed Liability may change after Determination.
A Subject may change.
A Relationship may change.
Scope may expand or contract.
Allocation may change.
A Transfer may occur.
A Recourse Relationship may emerge.
A Resolution condition may fail.
A payment may reverse.
A Settlement may collapse.
A discharged requirement may require renewed governance.
New information may materially affect an earlier Determination.
A Final Liability Relationship may require Re-Entry.
LIGA™ therefore supports targeted recursive governance.
The canonical Re-Entry rule is:
Re-enter the earliest materially affected governance space.
The canonical reassessment rule is:
Reassess what materially changed. Preserve what remains valid.
Re-Entry does not require complete reconstruction of the entire Liability lifecycle by default.
Only materially affected governance spaces and dependent downstream states require renewed governance.
Re-entry ≠ Full Lifecycle Restart by default.
Re-entry ≠ New Liability by default.
Re-entry ≠ New Origin by default.
Re-entry must not rewrite history.
Liability Relationship & Network Principle
LIGA™ does not assume that one event creates one Liability Relationship.
A Liability-relevant event may create:
multiple Subjects multiple Liability Relationships different Liability Bases different Conditions different Liability-Relevant Connections different Liability Determinations different Scopes different Allocations primary and secondary Liability shared Liability transferred Liability
Recourse Relationships
or:
a wider Liability Network Therefore:
One Occurrence ≠ One Liability Relationship.
One Liability Subject ≠ One Liability Relationship.
One Liability Relationship ≠ Complete Liability Network.
Primary Liability ≠ Recourse Liability.
Relationship Resolution ≠ Network Resolution.
Relationship Finality ≠ Network Finality.
Each Liability Relationship may possess its own lifecycle while remaining connected to a broader Liability Network.
Transfer & Recourse Principle
The Subject or system associated with the original event does not necessarily remain the only Liability-relevant Subject throughout the lifecycle.
Liability governance may involve:
Transfer
Sharing
Succession
Contribution
Indemnification
Insurance-related structures
Recovery
Recourse
or other secondary Liability Relationships.
LIGA™ therefore preserves the distinction:
Harm-Producing Actor ≠ Liability-Bearing Party ≠ Paying Party.
Transfer or Recourse should not rewrite the original Liability history.
A secondary Relationship may arise without replacing the primary Relationship.
Transfer ≠ Historical Replacement.
Primary Liability ≠ Recourse Liability.
Continuity & Finality Principle
Liability must remain historically reconstructable from Origin through Finality.
Changes in:
Subject
Relationship
Scope
Allocation
State
Transfer
Recourse
Resolution
Discharge
system representation or:
technical identifier should not silently destroy the continuity of the Liability lifecycle.
Therefore:
Current Liability State ≠ Complete Liability History.
Representation Change ≠ Liability Identity Change by default.
System Migration ≠ New Liability Origin.
Supersession ≠ Historical Deletion.
Correction ≠ Historical Erasure.
Liability Finality ≠ Liability Erasure.
Finality ends active Liability governance within its legitimate Scope.
It does not mean that Liability never existed.
It does not mean that all connected Liability Relationships are Final.
It does not prevent legitimate future Re-Entry.
Finality ends active Liability governance. It does not erase Liability history.
Foundational Architecture Principles
LIGA™ governs Liability — not the event, Harm, Claim, operational mechanism, evidence, or accountability structure surrounding it.
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.
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 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 Finality ≠ Network Finality.
Re-entry ≠ New Liability by default.
Re-entry ≠ New Origin by default.
Re-entry must not rewrite history.
Finality ends active Liability governance. It does not erase Liability 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 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 a previous Resolution or Finality. LIGA™ provides the governance architecture for that entire lifecycle.
LIGA™ governs Liability from relevance to Finality.