LIGA™ Architecture Map
Liability Governance Architecture — Liability Governance Layer
Official Liability Governance Reference Map 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 reference map used to identify, define, classify, navigate, govern, evaluate, and understand governable Liability spaces across individuals, groups, organizations, physical and digital objects, AI systems, autonomous systems, infrastructure, environments, institutions, networks, and future operational systems.
The purpose of LIGA™ is not to determine jurisdiction-specific legal liability, replace courts, regulators, arbitrators, insurers, contractual authorities, or Claims systems, govern Harm itself, allocate general accountability, perform general causation analysis, or replace evidence, audit, validation, legal, regulatory, insurance, contractual, or domain-specific decision systems.
The purpose of LIGA™ is to identify, define, separate, and map the governable spaces through which Liabilityrelevant Context is established, the Liability Object is formed, the applicable Liability Basis is identified, Liability Subjects and Relationships are structured, Liability Conditions are governed, Liability-Relevant Connection is established, Liability is determined and attaches where justified, Scope and Allocation are established, active Liability State and Change are governed, Transfer and Recourse are structured where applicable, Resolution and Discharge are governed, and Liability remains continuous and historically reconstructable through Re-Entry where required until legitimate Finality.
LIGA™ serves as the official Liability Governance reference map for:
Individuals
Multiple Individuals
Defined Groups
Organizations
Physical Objects
Digital Objects
Operational Systems
AI Systems
Autonomous Systems
Infrastructure
Physical Environments
Digital Environments
Institutional Systems
Contractual Networks
Liability Networks
Human-AI Environments
Multi-Agent Environments
Distributed Operational Systems
Future Operational Ecosystems
Core Architectural Principle
Every Liability Governance space answers one primary governance question.
No Liability Governance space duplicates the purpose of another Liability Governance space.
Every Liability Governance space has a defined beginning, a defined operational purpose, and a defined governance boundary.
Every Liability Governance space begins where the preceding Liability Governance requirement has been sufficiently established.
Together, these Liability Governance spaces form the official Liability Governance reference map of LIGA™.
Official Liability 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
Liability Context Standard (LCS)
Governed Space: Liability Context
Core Question
Within what context can Liability meaningfully exist and become governable?
Canonical Definition
Liability Context Standard (LCS) defines the governance conditions under which the operational, temporal, relational, institutional, contractual, technical, physical, digital, environmental, and other materially relevant context required to interpret potential Liability is identified, structured, bounded, and maintained.
Governance Boundary
Begins when a matter becomes sufficiently Liability-relevant to require methodological governance.
Ends when the relevant Liability Context has been sufficiently established to support Liability Object Governance.
Liability-Relevant Context ≠ Liability.
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?
Canonical Definition
Liability Object Standard (LOS) defines the governance conditions under which the exact matter in relation to which Liability is being considered is identified, bounded, distinguished from adjacent objects, represented, and maintained as a continuous governed Liability Object.
Governance Boundary
Begins when an established Liability Context contains a matter requiring explicit formation as a Liability Object.
Ends when the Liability Object has been sufficiently identified, bounded, distinguished, represented, and maintained to support Liability Basis Governance.
Liability Object ≠ Harm by default.
Liability Object ≠ Claim by default.
Liability Basis Standard (LBS)
Governed Space: Liability Basis
Core Question
On what governed basis can Liability potentially exist?
Canonical Definition
Liability Basis Standard (LBS) defines the governance conditions under which a potential Basis for Liability is identified, classified, qualified, associated with the relevant Liability Object, and maintained sufficiently to support subsequent Liability Relationship governance.
Governance Boundary
Begins when an established Liability Object requires identification of the Basis under which Liability may potentially attach.
Ends when the applicable Liability Basis has been sufficiently established to support Liability Subject and Relationship Governance.
Liability Basis ≠ Liability Attachment.
Liability Basis ≠ Liability Determination.
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?
Canonical Definition
Liability Relationship Standard (LRS) defines the governance conditions under which Liability-relevant Subjects are identified and the Relationships between Subjects, Liability Objects, applicable Bases, and other materially relevant structures are identified, mapped, distinguished, and maintained.
Governance Boundary
Begins when the Liability Object and applicable Liability Basis are sufficiently established to identify the Subjects and Relationships participating in the potential Liability structure.
Ends when the relevant Subjects and Liability Relationships have been sufficiently structured to support Liability Conditions Governance.
One Liability Subject ≠ One Liability Relationship.
One Liability Relationship ≠ Complete Liability Network.
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?
Canonical Definition
Liability Conditions Standard (LCOS) defines the governance conditions under which Liability-relevant requirements, states, exceptions, dependencies, and continuing conditions are identified, represented, and maintained under the applicable Liability Basis.
Governance Boundary
Begins when the Liability Object, Basis, Subjects, and Relationships are sufficiently established to determine what conditions govern progression toward potential Liability Determination.
Ends when the applicable Liability Conditions and their governed states have been sufficiently represented to support Liability Connection Governance.
Liability Basis ≠ Liability Conditions.
Liability Conditions ≠ Liability Determination.
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?
Canonical Definition
Liability Connection Standard (LCNS) defines the governance conditions under which Liability-relevant connections between Subjects, Liability Objects, conditions, conduct, events, states, consequences, and other relevant inputs are identified, related, structured into connection chains where necessary, qualified, and associated with supporting evidence.
Governance Boundary
Begins when applicable Liability Conditions and relevant external or operational inputs are sufficiently available to determine whether a Liability-Relevant Connection exists.
Ends when the relevant connection structure has been sufficiently established and qualified to support Liability Determination.
Operational Causation ≠ Liability-Relevant Connection.
Liability-Relevant Connection ≠ Liability Determination.
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?
Canonical Definition
Liability Determination Standard (LDS) defines the governance conditions under which qualified Liability inputs are evaluated to determine whether Liability may legitimately attach and be represented as an established governed Liability state.
Governance Boundary
Begins when the preceding Liability Context, Object, Basis, Relationships, Conditions, and Connection spaces have been sufficiently governed to support Liability Determination.
Ends when an explicit Governed Liability Determination State has been established and is capable of entering Liability Scope & Allocation Governance.
Potential Liability ≠ Attached Liability.
Liability Basis ≠ Liability Attachment.
Liability Determination ≠ Liability Scope.
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?
Canonical Definition
Liability Scope & Allocation Standard (LSAS) defines the governance conditions under which the extent, boundaries, applicable Subjects, Relationships, objects, requirements, and distribution of established Liability are identified, bounded, allocated, and reconciled.
Governance Boundary
Begins when a sufficient Governed Liability Determination State exists.
Ends when the applicable Liability Scope and Allocation structure has been sufficiently established to support active Liability State & Change Governance.
Liability Determination ≠ Liability Scope.
Liability Scope ≠ Liability Allocation.
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?
Canonical Definition
Liability State & Change Standard (LSCS) defines the governance conditions under which established Liability is represented as a current governed State, transitions between states are controlled, material changes are identified and assessed, and the history of Liability State changes remains reconstructable.
Governance Boundary
Begins when a sufficient Governed Liability Scope & Allocation Structure exists and the established Liability requires active lifecycle governance.
Continues while the Liability State remains active or materially relevant and routes affected states toward Liability Transfer & Recourse, Liability Resolution & Discharge, or an earlier LIGA™ governance space where Re-Entry is required.
Liability Determination at T1 ≠ Liability State at T2.
Liability Change ≠ New Liability by default.
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?
Canonical Definition
Liability Transfer & Recourse Standard (LTRS) defines the governance conditions under which Liability or its consequences may be transferred, shared, succeeded, redistributed, contributed, indemnified, recovered, or connected to secondary and Recourse Relationships while preserving the identity and continuity of the original Liability structure.
Governance Boundary
Begins when established Liability creates or enters a Transfer, Sharing, succession, contribution, Indemnification, insurance-related, Recovery, Recourse, or other secondary Liability Relationship.
Ends when the resulting Transfer, Sharing, secondary Liability, or Recourse structure and its effects have been sufficiently represented to support continuing Liability State governance, Resolution & Discharge, or subsequent lifecycle governance.
Harm-Producing Actor ≠ Liability-Bearing Party ≠ Paying Party.
Primary Liability ≠ Recourse Liability.
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?
Canonical Definition
Liability Resolution & Discharge Standard (LRDS) defines the governance conditions under which an active Liability Relationship or defined Liability requirement enters Resolution, Satisfaction, Settlement, Discharge, Extinguishment, or another legitimate condition under which the relevant active Liability no longer requires the same continuing performance or active governance.
Governance Boundary
Begins when active Liability enters a process, event, condition, performance, Settlement, Satisfaction, Discharge, or other state capable of resolving or ending an active Liability requirement.
Ends when a sufficiently governed Governed Liability Resolution & Discharge State has been established to support Liability Continuity & Finality Governance.
Payment ≠ Liability Resolution by default.
Settlement ≠ Liability Finality.
Liability Resolution ≠ Liability Finality.
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?
Canonical Definition
Liability Continuity & Finality Standard (LCFS) defines the governance conditions under which Liability remains continuously identifiable and historically reconstructable throughout and beyond active governance, prior states and transitions remain preserved, legitimate Re-Entry is governed where materially required, and a Liability requirement, Relationship, defined group of Relationships, or Liability Network may reach governed Finality without erasing its history.
Governance Boundary
Continuity begins with Liability formation and remains applicable throughout the Liability lifecycle.
Its terminal governance role becomes determinative when Resolution, Discharge, Extinguishment, or another lifecycle condition creates potential Finality.
LCFS continues through:
Continuity Identification → Historical Record → Finality Assessment → Re-Entry where required → Finality
Record
It ends active LIGA™ governance for the applicable Scope when a Governed Liability Finality State has been sufficiently established while the Liability remains historically reconstructable and capable of legitimate Re-Entry where materially required.
Liability Resolution ≠ Liability Finality.
Finality ends active Liability governance. It does not erase Liability history.
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
Complete Liability Lifecycle
LIGA™ does not treat Liability Determination as the completion of the Liability lifecycle.
The complete governed lifecycle is:
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.
A Determination establishes whether Liability has attached.
It does not establish that the complete lifecycle has ended.
Liability Determination ≠ Liability Lifecycle Completion.
Liability Resolution ≠ Liability Finality.
Liability Finality ≠ Liability Erasure.
Recursive Liability Lifecycle
LIGA™ does not assume that governed Liability progresses through its lifecycle only once.
Once Liability has been established, its condition may continue to change:
Liability State may change.
Liability Scope may expand or contract.
Liability Allocation may change.
Subjects may change.
Relationships may change.
Liability may be transferred or shared.
Secondary Liability Relationships may arise.
Recourse may arise or change.
Primary Liability may resolve while Recourse remains active.
Resolution conditions may fail.
Payments may reverse.
Settlements may fail or become ineffective.
Discharge conditions may change.
New material information may affect an earlier governance state.
A previously Final Liability may require Re-Entry.
The architecture therefore becomes recursive:
Governed Liability → Liability State & Change → Transfer / Recourse where applicable → Resolution / Discharge → Continuity → Finality Assessment → Finality Where materially relevant Liability reality changes:
Resolution / Finality → Re-Entry → Appropriate LIGA™ Re-Entry Point → Renewed Liability Governance → Resolution / Discharge → Continuity & Finality Lifecycle Re-Entry occurs at the earliest materially affected governance space.
A materially changed Liability Context may require Re-Entry into Liability Context Standard.
A materially incorrect or changed Liability Object may require Re-Entry into Liability Object Standard.
A materially changed or incorrectly represented Liability Basis may require Re-Entry into Liability Basis Standard.
A new Subject, corrected Subject, newly identified Relationship, or materially changed Relationship may require Re-Entry into Liability Relationship Standard.
Changed, failed, satisfied, or incorrectly represented Liability Conditions may require Re-Entry into Liability Conditions Standard.
New information materially affecting Liability-Relevant Connection may require Re-Entry into Liability Connection Standard.
A materially challenged Liability Determination or Attachment may require Re-Entry into Liability Determination Standard.
A changed Liability Scope or Allocation may require Re-Entry into Liability Scope & Allocation Standard.
A changed current Liability State may require Re-Entry into Liability State & Change Standard.
New or changed Transfer, Sharing, succession, contribution, Indemnification, insurance-related, or Recourse structures may require Re-Entry into Liability Transfer & Recourse Standard.
Changed Satisfaction, Settlement, Resolution, Discharge, release, Extinguishment, or related conditions may require ReEntry into Liability Resolution & Discharge Standard.
Changed Continuity, historical reconstruction, Finality, or Re-Entry conditions may require reconsideration within Liability Continuity & Finality Standard.
The architecture therefore supports targeted governed Liability lifecycle Re-Entry rather than uncontrolled reconstruction of the entire Liability lifecycle.
Re-enter the earliest materially affected governance space.
Reassess what materially changed. Preserve what remains valid.
Re-entry must not rewrite history.
Liability Relationship & Network Structure
LIGA™ does not assume that one occurrence creates one Liability Relationship.
A single Liability-relevant occurrence may create:
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 Liability Relationship may possess its own lifecycle while remaining connected to the wider Liability Network.
A primary Liability Relationship may reach Resolution while a Recourse Relationship remains active.
One Relationship may reach Finality while other Relationships remain within active governance.
Therefore:
One Occurrence ≠ One Liability Relationship.
One Harm ≠ One Liability Relationship.
One Liability Subject ≠ One Liability Relationship.
One Liability Relationship ≠ Complete Liability Network.
Relationship Resolution ≠ Network Resolution.
Relationship Finality ≠ Network Finality.
Architectural Position
LIGA™ governs the complete Liability Governance lifecycle from Liability Context and potential Liability formation through governed Liability 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 Liability Governance spaces govern the context in which Liability may become relevant, what matter constitutes the governed Liability Object, on what Basis Liability may potentially exist, which Subjects and Relationships participate, what Conditions apply, what Liability-Relevant Connection exists, whether Liability may legitimately attach and be determined, what its Scope is, how it 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, how its history remains continuous and reconstructable, when Re-Entry is required, and when active Liability governance may legitimately reach Finality.
LIGA™ therefore provides a complete governance path from the first identification of the context in which Liability can meaningfully become relevant to the determination of when active governance of that Liability lifecycle can legitimately end.
What LIGA™ Defines
LIGA™ defines:
where Liability Governance begins, how Liability Context is established, how Liability-relevant environments and temporal context are governed, how Liability Context boundaries and continuity are maintained, how the Liability Object is identified, how the Liability Object boundary is established, how the Liability Object is distinguished from adjacent objects, how the Liability Object is represented and maintained, how Liability Basis is identified, how Liability Basis is classified and qualified, how Liability Basis is associated with the Liability Object, how Liability Basis continuity is maintained, how Liability Subjects are identified, how Liability Relationships are identified, how Liability Relationships are mapped, how materially distinct Relationships are differentiated, how Liability Relationship continuity is maintained, how Liability Conditions are identified, how Liability Condition requirements are represented, how Liability Condition States are governed, how Liability Condition exceptions are governed, how Liability Condition continuity is maintained, how Liability-Relevant Connection is identified, how Liability Connection Relationships are governed, how Liability Connection Chains are structured, how Liability Connection is qualified, how relevant evidence is associated with Liability Connection without replacing evidence governance, how Liability Determination inputs are established, how Liability Determination is evaluated, how Liability Attachment is governed, how Liability Determination rationale is preserved, how Liability Determination versions remain reconstructable, how Liability Scope is identified, how Liability Scope boundaries are established, how Liability Allocation is identified, how Liability Allocation is distributed, how Liability Scope and Allocation are reconciled, how the current Liability State is identified, how Liability State transitions are governed, how Liability Change is identified, how Liability Change is assessed, how Liability State history is preserved, how Liability Transfer is identified, how Liability Sharing is governed, how Liability Recourse is identified, how Liability Recourse Networks are governed, how Liability Transfer continuity is maintained, how Liability Resolution is initiated, how Liability Satisfaction is governed, how Liability Settlement is represented, how Liability Discharge is governed, how Liability Resolution is verified, how Liability Continuity is identified, how the Liability Historical Record is preserved, how Liability Finality is assessed, when Liability requires Re-Entry, how the appropriate LIGA™ lifecycle Re-Entry point is determined, how Finality is recorded, and how the Governed Liability Finality State is formed.
LIGA™ provides the official Liability Governance language used for Liability-space identification, lifecycle navigation, governance classification, structural diagnosis, Liability-state analysis, Relationship and Network governance, Transfer and Recourse governance, Resolution, Discharge, Continuity, Re-Entry, Finality, and Liability Governance architecture design across human, physical, digital, AI-driven, autonomous, organizational, infrastructural, institutional, contractual, distributed, and future operational environments.
Critical Architectural 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 ≠ Reassessment 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 Finality Record ≠ Evidence Repository by Default Liability Finality ≠ Absolute Irreversibility Liability Finality ≠ Liability Erasure
Cross-Architecture Governance Boundaries
LIGA™ ↔ ORA™ — Operational Reality Architecture
ORA™ — Operational Reality Architecture governs what exists and occurs in actual Operational Reality.
LIGA™ — Liability Governance Architecture governs whether and how that reality becomes Liability-relevant and how Liability progresses through its governed lifecycle.
Operational Reality Governance ≠ Liability Governance.
Operational Causation ≠ Liability-Relevant Connection.
LIGA™ ↔ HAGA™ — Harm Governance Architecture
HAGA™ — Harm Governance Architecture governs Harm throughout its lifecycle.
LIGA™ — Liability Governance Architecture governs Liability throughout its lifecycle.
Harm may contribute a governed input to Liability where applicable, but:
Harm ≠ Liability.
Harm Determination ≠ Liability Determination.
Harm Resolution ≠ Liability Resolution.
Harm Finality ≠ Liability Finality.
LIGA™ ↔ AGA™ — Accountability Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability.
AGA™ — Accountability Governance Architecture governs authority, Responsibility, Accountability, attribution, and related accountability Relationships.
Responsibility ≠ Liability.
Accountability ≠ Liability.
Accountability Attribution ≠ Liability Allocation.
LIGA™ ↔ ADIT® — Continuous Audit & Evidence Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability and Liability lifecycle states.
ADIT® governs evidential observation, preservation, correlation, verification, examination, and auditability.
Evidence of Liability-Relevant Facts ≠ Liability Determination.
LIGA™ ↔ VALIDOS™ — Validation Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability Determination and subsequent Liability lifecycle governance.
VALIDOS™ — Validation Governance Architecture governs whether a validation basis sufficiently supports a Validation Determination and intended reliance.
Validation Determination ≠ Liability Determination.
LIGA™ ↔ INTEGROS® — Integrity Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability as a distinct lifecycle object.
INTEGROS® — Integrity Governance Architecture governs integrity across governed objects, structures, states, evidence, and processes.
Liability Governance ≠ General Integrity Governance.
LIGA™ ↔ OBIDENITY® — Origin-Bound Identity Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability Subjects and Liability Relationships.
OBIDENITY® — Origin-Bound Identity Governance Architecture governs Origin, Identity, Ownership, Authority, Permission, Responsibility, Provenance, Transfer, Continuity, and Auditability.
Identity ≠ Liability Subject Determination.
Identity Continuity ≠ Liability Continuity by itself.
LIGA™ ↔ AIG® — AI Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability that may arise in relation to AI behavior.
AIG® — AI Governance Architecture governs AI behavioral governance and behavioral integrity.
AI Behavior ≠ Liability.
AI Behavioral Failure ≠ Liability Determination.
LIGA™ ↔ ASGA™ — Autonomous Systems Governance Architecture
LIGA™ — Liability Governance Architecture governs Liability that may arise in relation to autonomous operation.
ASGA™ — Autonomous Systems Governance Architecture governs autonomous-system authority, execution, constraints, coordination, intervention, escalation, and operational governability.
Autonomous Action ≠ Liability.
Autonomous-System Failure ≠ Liability Determination.
LIGA™ ↔ VFM® — Value Flow Mechanism
LIGA™ — Liability Governance Architecture governs Liability and its lifecycle.
VFM® — Value Flow Mechanism 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® — Simulation Governance Architecture
LIGA™ — Liability Governance Architecture governs actual Liability.
SIMULOS® — Simulation Governance Architecture governs simulation purpose, structure, execution, outputs, and lifecycle.
Simulated Liability ≠ Actual Liability.
Simulated Liability Determination ≠ Governed Liability Determination.
LIGA™ ↔ Claims Systems
LIGA™ — Liability Governance Architecture governs Liability.
Claims systems govern Claim formation, processing, evaluation, administration, payment, rejection, closure, 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™ — Liability Governance Architecture 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 produce or contribute to conditions through which Liability relevance arises.
Liability Governance ≠ Governance of the Liability-Relevant Mechanism.
Compatible OOF® Architectures
GOA™ — Governance Architecture
ORA™ — Operational Reality Architecture
HAGA™ — Harm Governance Architecture
AGA™ — Accountability Governance Architecture
ADIT® — Continuous Audit & Evidence Governance Architecture
VALIDOS™ — Validation Governance Architecture
INTEGROS® — Integrity Governance Architecture
OBIDENITY® — Origin-Bound Identity Governance Architecture
AIG® — AI Governance Architecture
ASGA™ — Autonomous Systems Governance Architecture
VFM® — Value Flow Mechanism
SIMULOS® — Simulation Governance Architecture
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 conditions under which Liability becomes contextually identifiable, object-bounded, basis-grounded, relationally structured, condition-aware, sufficiently connected, determinable and attachable where justified, scoped, allocatable, stategoverned, 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.
Canonical Closing Statement
LIGA™ serves as the official Liability Governance reference map for individuals, groups, organizations, physical and digital objects, AI systems, autonomous systems, infrastructure, environments, institutions, networks, and future operational systems. By defining the primary governable spaces of the complete Liability Lifecycle, LIGA™ provides the architecture used to establish the context in which Liability may become relevant, define the governed Liability Object, establish the applicable Liability Basis, identify Subjects and Relationships, govern Liability Conditions, establish Liability-Relevant Connection, determine whether Liability legitimately attaches, establish Liability Scope and Allocation, govern active Liability State and Change, structure Transfer, Sharing, and Recourse where applicable, establish legitimate Resolution and Discharge, preserve lifecycle Continuity and historical reconstructability, route Re-Entry to the earliest materially affected governance space when circumstances materially change, and determine when the Liability lifecycle has reached governed Finality.
LIGA™ therefore establishes Liability Governance as a distinct methodological layer around Liability itself, enabling Liability to remain identifiable, bounded, relationally structured, condition-aware, determinable, scoped, allocatable, state-governed, transferable, recoverable through Recourse where applicable, resolvable, historically reconstructable, reopenable, and capable of legitimate Finality regardless of whether Liability relevance originates through human action, AI behavior, autonomous operation, physical interaction, contractual relationships, organizational processes, system failures, Harm, loss, environmental conditions, or composite operational mechanisms.
LIGA™ governs Liability from relevance to Finality.