About LIGA™ — Liability Governance Architecture
Governing Liability Across the Complete Liability Lifecycle
Liability increasingly emerges across complex human, organizational, contractual, digital, physical, AI-driven, autonomous, infrastructural, institutional, and distributed operational environments.
Individuals may participate in multiple Liability Relationships arising from the same occurrence.
Organizations may simultaneously hold, share, transfer, discharge, or seek Recourse in relation to different Liability structures.
AI systems may contribute outputs, recommendations, decisions, interactions, or behavioral patterns that become relevant to Liability without the AI behavior itself constituting Liability.
Autonomous systems may act across physical and digital environments in ways that create complex relationships between operators, owners, manufacturers, service providers, infrastructure, affected parties, insurers, and other participants.
One occurrence may generate multiple Liability Relationships.
The party producing Harm may differ from the party bearing Liability.
The Liability-bearing party may differ from the paying party.
Primary Liability may resolve while Recourse continues.
A Liability Relationship may reach Finality while the wider Liability Network remains active.
New material information may require Re-Entry after Resolution or even after a previous Finality state.
As these environments become more interconnected, Liability itself requires governance beyond the event, Harm, Claim, payment, contractual relationship, person, organization, AI system, autonomous system, or operational mechanism from which Liability relevance arose.
LIGA™ — Liability Governance Architecture was created to provide a stable governance architecture for this expanding Liability domain.
LIGA™ does not 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, administer legal proceedings, or replace evidence, audit, validation, insurance, contractual, regulatory, or other domainspecific systems.
LIGA™ governs Liability — not the event, Harm, Claim, accountability structure, or operational mechanism surrounding it.
Why LIGA™ Exists
Liability is frequently treated as a conclusion attached to another process.
An event occurs.
Harm may emerge.
An investigation begins.
Responsibility may be examined.
A Claim may be submitted.
Liability may be alleged.
An insurer may become involved.
Payment may occur.
A Settlement may be reached.
A case may eventually close.
But none of these processes independently answers the complete Liability Governance questions:
Within what context can Liability meaningfully exist?
What exactly is the Liability Object?
On what Basis can Liability potentially exist?
Who or what participates in the Liability structure?
What Liability Relationships exist between them?
What Conditions must exist, fail, change, or be satisfied?
What sufficiently governed Liability-Relevant Connection exists?
Can Liability legitimately attach and be determined?
For what does the Liability apply?
What is its Scope?
How is Liability allocated across multiple Relationships or Subjects?
What is the current Liability State?
How may that State legitimately change?
Can Liability be transferred, shared, succeeded, or redistributed?
Does Recourse create a secondary Liability Relationship?
Has active Liability actually been satisfied, settled, discharged, extinguished, or resolved?
Does Resolution apply to one requirement, one Relationship, or the complete Liability Network?
Does the Liability remain historically reconstructable?
When does changed information require Re-Entry?
When may a Liability Relationship legitimately reach Finality?
When has the complete Liability Network reached Finality?
LIGA™ addresses these questions by defining the governable spaces that exist throughout the complete Liability Lifecycle.
Rather than standardizing one liability-management or legal process, LIGA™ standardizes the governance conditions under which Liability can become 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 through governed Re-Entry, and capable of legitimate Finality.
Liability Beyond Harm, Accountability, and Claims
The objective of LIGA™ is not to determine whether Harm exists, who is morally responsible, who should be held accountable, whether a Claim should be accepted, what compensation should be paid, or what a jurisdiction-specific court or authority should decide.
The objective is to define how Liability itself remains governable throughout its complete lifecycle.
Before Liability can be interpreted, its Context must be understood.
The Liability Object must identify exactly what governed matter is under consideration.
A Liability Basis must establish why Liability may potentially exist.
Relevant Subjects and Relationships must be identified.
Applicable Conditions must remain explicit.
Operational causation must remain distinguishable from Liability-Relevant Connection.
Potential Liability must remain distinguishable from attached Liability.
Liability Determination must remain distinguishable from Liability Scope.
Scope must remain distinguishable from Allocation.
Current Liability State must remain distinguishable from complete Liability history.
Transfer must not erase the original Liability Relationship.
Recourse must remain distinguishable from primary Liability.
Resolution must remain distinguishable from Finality.
Relationship Finality must remain distinguishishable from Network Finality.
Re-Entry must preserve prior valid governance and historical states.
Finality must establish when active Liability governance can legitimately end without erasing the Liability history.
LIGA™ therefore treats Liability as an independent governance domain surrounding, but distinct from, Harm, causation, accountability, Responsibility, Claims, evidence, payment, compensation, insurance, contractual performance, Value consequences, and legal adjudication.
The Liability Governance Architecture
LIGA™ consists of twelve independent Liability Governance spaces.
Each space answers one architectural question.
Each space governs one distinct part of the Liability Lifecycle.
Each space has a defined beginning, operational purpose, and governance boundary.
Each space begins where the preceding Liability Governance requirement has been sufficiently established.
Together, these spaces form the complete Liability Governance Architecture.
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 This progression represents the governance journey from understanding the context in which Liability may meaningfully become relevant to determining when active governance of that Liability lifecycle can legitimately reach Finality.
Liability Spaces Rather Than Liability-Producing Mechanisms
LIGA™ does not organize Liability Governance around people, AI models, robots, organizations, insurers, contracts, incidents, machines, software systems, legal categories, Claims systems, or technical components.
Instead, it organizes governance around distinct Liability Governance spaces.
Each space represents an independent governance responsibility that exists regardless of the mechanism through which Liability relevance arose.
Liability relevance arising from a human action, AI output, autonomous-system action, physical interaction, contractual event, organizational process, software failure, infrastructure failure, Harm, loss, environmental condition, or composite operation may arise through very different mechanisms.
Yet each may still require governance of:
context → object → basis → relationships → conditions → connection → determination → scope & allocation → state & change → transfer & recourse → resolution & discharge → continuity & finality.
Because these spaces are methodology-neutral and technology-neutral, LIGA™ can remain applicable while AI systems, autonomous technologies, legal environments, contractual structures, insurance systems, organizational relationships, and operational mechanisms continue to evolve.
A Methodology Rather Than a Legal Liability System
LIGA™ is a governance methodology.
It is not a legal liability determination system.
The architecture defines which Liability Governance conditions must exist, how they relate to one another, where their boundaries lie, and what must remain explicit for Liability to remain governable throughout its lifecycle.
Organizations, institutions, authorities, and systems remain free to select their own:
legal frameworks, jurisdiction-specific rules, contractual systems, insurance processes, Claims systems, dispute-resolution processes, arbitration procedures, judicial procedures, investigation methods, evidence systems, audit systems, risk-management systems, AI governance systems, autonomous-system controls, compensation mechanisms, recovery mechanisms.
LIGA™ governs the methodological Liability structure surrounding those implementations rather than replacing them.
This separation allows the architecture to remain stable while laws, contractual arrangements, technologies, institutions, insurance structures, and operational environments change.
From Liability-Relevant Occurrence to Governed Liability
A Liability-relevant occurrence cannot automatically be treated as established Liability merely because an event, Harm, loss, breach, failure, Claim, or dispute occurred.
A real-world event, AI output, autonomous action, physical interaction, contractual event, process failure, Harm condition, Value loss, behavioral deviation, or other occurrence may be Liability-relevant without establishing Liability.
Liability Relevance ≠ Liability.
A Liability Basis may exist without Liability attaching.
Conditions may exist without being satisfied.
Operational causation may exist without establishing a Liability-Relevant Connection.
A Liability-Relevant Connection may exist without completing Liability Determination.
Potential Liability may remain potential.
Determination must establish whether Liability can legitimately attach on the governed Basis.
Once Liability is established, its lifecycle continues through Scope, Allocation, State, Change, Transfer, Recourse, Resolution, Discharge, Continuity, Re-Entry where required, and Finality.
LIGA™ transforms these dependencies into a structured and navigable Liability Lifecycle.
The Liability Object Must Be Explicit
One of the foundational requirements of LIGA™ is that Liability cannot be governed reliably if the matter against which Liability is being considered remains undefined.
The Liability Object may relate to:
an obligation a consequence an event a defined loss a performance requirement a contractual matter a governed Harm-related matter a system outcome or another sufficiently defined matter relevant to Liability.
But the Liability Object is not automatically identical to the event, Harm, Claim, Subject, obligation, or mechanism from which Liability relevance arose.
Therefore:
Occurrence ≠ Harm ≠ Liability Object ≠ Liability Relationship.
A clear Liability Object prevents materially different Liability questions from being collapsed into one undefined object.
Liability Basis Is Not Liability
A Basis establishes why Liability may potentially exist.
It does not establish that Liability has attached.
LIGA™ therefore preserves:
Liability Basis ≠ Liability Attachment and:
Liability Basis ≠ Liability Determination A relevant legal, contractual, operational, institutional, governance, or other recognized Basis may establish the possibility of Liability.
But additional governance remains necessary.
Subjects and Relationships must be identified.
Conditions must be evaluated.
Liability-Relevant Connection must be established.
Only then can Liability proceed toward legitimate Determination and Attachment.
This prevents the existence of a possible Liability Basis from being treated as proof that Liability already exists.
Liability Basis Is Not Liability Conditions
A Basis answers:
Why can Liability potentially exist?
Conditions answer:
What must be true, satisfied, failed, changed, or otherwise established under that Basis for potential Liability to proceed toward Determination?
These questions are related but methodologically distinct.
Therefore:
Liability Basis ≠ Liability Conditions.
A valid Basis may exist while required Conditions remain unsatisfied.
Conditions may change over time.
Exceptions may apply.
Dependencies may fail.
A condition may be satisfied for one Subject or Relationship but not another.
Separating Basis from Conditions allows LIGA™ to preserve these distinctions without collapsing them into one generic Liability criterion.
Connection Is Not Determination
Liability frequently depends on relationships between Subjects, objects, conduct, events, conditions, Harm, loss, performance, or other relevant inputs.
But establishing that things are factually or operationally connected does not automatically establish Liability.
LIGA™ therefore preserves:
Operational Causation ≠ Liability-Relevant Connection Factual Connection ≠ Liability-Relevant Connection by Default and:
Liability-Relevant Connection ≠ Liability Determination Operational systems may determine how an event occurred.
Evidence systems may establish facts.
HAGA™ may establish Harm.
Other systems may establish contractual, technical, financial, or operational conditions.
LIGA™ governs whether and how those inputs form a sufficiently governed connection for Liability purposes.
Potential Liability Is Not Attached Liability
Potential Liability may exist throughout the early LIGA™ lifecycle.
A relevant Context may exist.
A Liability Object may be established.
A Basis may apply.
Subjects and Relationships may exist.
Conditions may appear satisfied.
A relevant Connection may be established.
Yet Liability still requires governed Determination.
Therefore:
Potential Liability ≠ Attached Liability.
The Liability Determination space establishes whether Liability may legitimately attach and be represented as governed Liability.
This creates the transition:
Potential Liability → Qualified Determination Inputs → Determination Evaluation → Liability Attachment Determination → Governed Liability Determination State Only after this transition does LIGA™ treat Liability as established for subsequent Scope, Allocation, State, Transfer, Resolution, and Finality governance.
Scope Is Not Allocation
Determining that Liability exists does not establish its complete extent or distribution.
LIGA™ therefore separates Liability Determination from Liability Scope & Allocation.
Scope asks:
For what does established Liability apply, and to what extent?
Allocation asks:
How is that established Liability distributed across applicable Subjects or Relationships?
Therefore:
Liability Determination ≠ Liability Scope and:
Liability Scope ≠ Liability Allocation One Liability Determination may lead to different Scopes for different requirements.
One Scope may involve multiple Subjects.
Multiple Liability Relationships may require different Allocations.
This distinction becomes particularly important in complex organizational, contractual, insurance, AI, autonomous-system, infrastructure, and multi-party environments.
One Occurrence May Create a Liability Network
LIGA™ does not assume that one event creates one Liability Relationship.
A single occurrence may create:
multiple Subjects multiple Liability Relationships different Liability Bases different Conditions different Liability-Relevant Connections different Determinations different Scopes different Allocations primary Liability shared Liability secondary Liability transferred Liability
Recourse Liability
or:
a 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.
Each Relationship may possess its own lifecycle while remaining connected to the wider Liability Network.
The Harm-Producing Actor May Not Be the Liability-Bearing Party
Modern Liability structures may involve multiple operational and legal layers.
The actor producing Harm may not ultimately bear the relevant Liability.
The Liability-bearing party may not be the party that performs payment.
A party making payment may possess Recourse against another party.
Insurance, Indemnification, contribution, contractual allocation, succession, Transfer, or other structures may change how Liability or its consequences move through the network.
LIGA™ therefore preserves:
Harm-Producing Actor ≠ Liability-Bearing Party ≠ Paying Party.
This distinction is especially important in AI systems, autonomous systems, supply chains, infrastructure, insurance networks, contractual ecosystems, distributed organizations, and other environments where operational action and Liability-bearing structures may be separated.
Transfer Is Not Historical Replacement
Liability may move, be shared, succeeded, redistributed, indemnified, insured, recovered, or create Recourse.
But a later Liability Relationship should not silently rewrite the earlier one.
LIGA™ therefore preserves:
Transfer ≠ Historical Replacement.
A secondary Relationship may arise without eliminating the identity of the primary Liability Relationship.
A Recourse Relationship may exist because one party has satisfied or assumed a Liability consequence while another Relationship remains relevant.
Therefore:
Primary Liability ≠ Recourse Liability.
The architecture preserves both the continuity of the original Liability and the identity of secondary Relationships created through Transfer or Recourse.
Liability State May Change After Determination
A Liability Determination is made at a particular governed point in time.
The Liability lifecycle does not freeze at that moment.
Scope may change.
Allocation may change.
Conditions may change.
Relationships may change.
Performance may occur.
Transfer may occur.
Recourse may arise.
A Settlement may be reached.
A Resolution condition may fail.
New information may materially affect earlier governance.
LIGA™ therefore preserves:
Liability Determination at T1 ≠ Liability State at T2.
and:
Liability Change ≠ New Liability by default.
The current Liability State must remain connected to the complete history through which that State was formed.
Payment Is Not Liability
Payment may be relevant to Liability.
But payment alone does not establish the complete meaning of the Liability state.
A payment may represent:
Satisfaction
partial Satisfaction
Settlement
insurance performance contractual performance commercial compromise voluntary payment procedural payment or another governed condition.
Therefore:
Payment ≠ Admission of Liability.
Claim Payment ≠ Liability Admission.
Payment ≠ Liability Resolution by default.
The meaning of payment must be governed within the applicable Liability structure rather than inferred from the transaction alone.
Resolution Is Not Finality
A Liability requirement or Relationship may become legitimately resolved without the complete Liability lifecycle immediately reaching Finality.
LIGA™ therefore distinguishes:
Liability Resolution ≠ Liability Finality Resolution determines whether an active Liability requirement has been sufficiently satisfied, settled, discharged, extinguished, or otherwise resolved.
Finality determines whether the applicable Liability lifecycle may legitimately leave active governance.
A primary Liability Relationship may be resolved while Recourse continues.
One requirement may be discharged while another remains active.
One Subject may reach Finality while another remains within active governance.
One Relationship may reach Finality while the wider Liability Network remains open.
This prevents Liability from being treated as finished merely because:
payment occurred a Settlement was signed a Claim closed an insurer completed processing a contract ended an administrative record was closed or:
one Liability Relationship was resolved.
Relationship Finality Is Not Network Finality
Complex Liability structures may contain multiple connected Relationships.
Each may possess a different State.
One may remain potential.
Another may be determined.
Another may be transferred.
Another may be in Recourse.
Another may be resolved.
Another may already be Final.
LIGA™ therefore preserves:
Relationship Finality ≠ Network Finality.
Primary Liability Finality ≠ Recourse Finality.
Subject A Finality ≠ Subject B Finality.
Finality must always identify the exact Finality Object and Finality Scope.
A local terminal state must not silently propagate across an entire Liability Network.
Liability Continuity Extends Across the Complete Lifecycle
Continuity is not merely post-Resolution recordkeeping.
Liability must remain reconstructable from its Origin through Context, Object, Basis, Relationships, Conditions, Connection, Determination, Scope, Allocation, State changes, Transfer, Recourse, Resolution, Discharge, Finality, and any later Re-Entry.
Therefore:
Liability Continuity ≠ Post-Resolution Recordkeeping.
Current Liability State ≠ Complete Liability History.
Representation Change ≠ Liability Identity Change by default.
System Migration ≠ New Liability Origin.
Supersession ≠ Historical Deletion.
Correction ≠ Historical Erasure.
The objective is not merely to preserve documents.
The objective is to preserve the governed continuity of the Liability lifecycle.
Lifecycle Governance and Liability Re-Entry
Liability Governance does not necessarily end permanently when Finality is first established.
New material information may emerge.
A previously accepted fact may be corrected.
A Relationship may have been incorrectly represented.
A Settlement condition may fail.
A Transfer may be invalidated.
A Recourse right may emerge.
A relevant Condition may change.
A Determination basis may be materially affected.
A previously unknown Relationship may become visible.
LIGA™ therefore extends governance beyond Resolution and Discharge into Continuity, Re-Entry, and Finality.
Where Liability reality materially changes:
Finality / Resolution → Re-Entry → Appropriate LIGA™ Re-Entry Point → Renewed Liability Governance Re-Entry does not automatically restart the entire Liability lifecycle.
It returns governance to the earliest materially affected governance space.
The canonical rule is:
Re-enter the earliest materially affected governance space.
The reassessment principle is:
Reassess what materially changed. Preserve what remains valid.
The result is targeted governed Liability lifecycle Re-Entry.
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.
Finality Does Not Erase Liability
Finality determines when active Liability governance may legitimately end for the applicable Finality Object and Scope.
It does not determine that Liability never existed.
It does not erase the Determination.
It does not erase Scope or Allocation.
It does not erase payments, Transfers, Recourse, Settlement, Resolution, or Discharge.
It does not erase previous Liability States.
It does not automatically establish Finality for every connected Relationship.
It does not prevent legitimate future Re-Entry where materially required.
Therefore:
Liability Finality ≠ Liability Erasure.
The foundational rule is:
Finality ends active Liability governance. It does not erase Liability history.
Who May Benefit
LIGA™ may support:
public institutions, regulators, legal and governance teams, insurers, Claims organizations, contractual organizations, AI developers, AI operators, autonomous-system developers, robotics organizations, industrial organizations, infrastructure operators, manufacturers, supply-chain organizations, financial organizations, digital-platform operators, risk-management teams, compliance organizations, audit and assurance organizations, research organizations, organizations operating complex multi-party systems, organizations responsible for human, physical, digital, contractual, AI-driven, autonomous, institutional, infrastructural, or distributed operational environments.
Relationship to Other OOF® Architectures
LIGA™ governs Liability.
It operates alongside complementary OOF® architectures.
GOA™ — Governance Architecture governs governance structure, authority, boundaries, scope, delegation, accountability, validation, integrity, transparency, continuity, and interoperability.
ORA™ — Operational Reality Architecture governs what actually exists and occurs in Operational Reality.
HAGA™ — Harm Governance Architecture governs Harm throughout its lifecycle independently from whether Liability exists.
AGA™ — Accountability Governance Architecture governs authority, Responsibility, Accountability, attribution, delegation, and related accountability Relationships surrounding actions, decisions, omissions, and consequences.
ADIT® — Continuous Audit & Evidence Governance Architecture governs evidential observation, preservation, correlation, verification, examination, and auditability.
VALIDOS™ — Validation Governance Architecture governs validation purpose, criteria, methods, evidence fitness, determination, Validation States, reliance, and revalidation.
INTEGROS® — Integrity Governance Architecture governs integrity across governed objects, states, evidence, structures, and processes.
OBIDENITY® — Origin-Bound Identity Governance Architecture governs Origin, Identity, Ownership, Authority, Permission, Responsibility, Provenance, Transfer, Continuity, and Auditability.
AIG® — AI Governance Architecture governs AI behavioral governance and behavioral integrity.
ASGA™ — Autonomous Systems Governance Architecture governs autonomous-system identity, authority, execution, constraints, coordination, intervention, escalation, and operational governability.
VFM® — Value Flow Mechanism governs what happens to Value as a consequence of events and conditions.
SIMULOS® — Simulation Governance Architecture governs simulation purpose, structure, execution, outputs, and lifecycle.
Together, these architectures allow Liability Governance to interact with Operational Reality, Harm, Accountability, identity, evidence, validation, integrity, AI behavior, autonomous operation, Value, and simulation without collapsing those independent governance domains into one architecture.
Use Case 1 — One Event Creates Multiple Liability Relationships
An autonomous industrial system causes an operational event that damages equipment and interrupts connected production.
The event may involve:
an autonomous-system operator, a system owner, a manufacturer, a maintenance provider, a software provider, an affected customer, an insurer, and other contractual parties.
HAGA™ may govern the resulting Harm.
ORA™ may govern what actually occurred.
ADIT® may govern relevant evidence.
AGA™ may govern Responsibility and Accountability structures.
But LIGA™ asks a different set of questions:
What is the Liability Context?
What exactly is the Liability Object?
What Liability Bases may apply?
Which Subjects participate?
What distinct Liability Relationships exist?
What Conditions apply to each Relationship?
What Liability-Relevant Connections exist?
Which Relationships support Liability Determination?
What is the Scope of each established Liability?
How is Liability allocated?
What are the current Liability States?
Has any Liability been transferred or shared?
Has payment created Recourse?
Which Relationships have been resolved?
Which remain active?
Has one Relationship reached Finality while the wider Network remains open?
LIGA™ therefore preserves:
One Occurrence ≠ One Liability Relationship.
Harm-Producing Actor ≠ Liability-Bearing Party ≠ Paying Party.
Primary Liability ≠ Recourse Liability.
Relationship Finality ≠ Network Finality.
The objective is not to decide jurisdiction-specific legal Liability.
The objective is to ensure that the complete Liability structure remains methodologically governable.
Use Case 2 — Resolution Followed by Material Re-Entry
A Liability Relationship has been determined, scoped, allocated, and later resolved.
Applicable performance occurs.
A Settlement is recorded.
The active Liability requirement is discharged.
After continuity and Finality assessment, the Relationship reaches a governed Finality State.
Later, materially relevant information becomes available.
The new information does not automatically erase the earlier Determination, Resolution, Discharge, or Finality.
Nor does it automatically require reconstruction of the complete Liability lifecycle.
LIGA™ asks:
What materially changed?
Does the new information affect Context?
Does it alter the Liability Object?
Does it affect the Basis?
Does it reveal a new or incorrectly represented Relationship?
Does it alter a Condition?
Does it materially affect Liability-Relevant Connection?
Does it challenge the Determination?
Does it alter Scope or Allocation?
Does it affect Resolution or Discharge?
What prior governance remains valid?
What is the earliest materially affected governance space?
LIGA™ therefore applies:
Re-enter the earliest materially affected governance space.
Reassess what materially changed. Preserve what remains valid.
Re-entry must not rewrite history.
The previous Finality remains part of the historical Liability record even where renewed governance becomes necessary.
The Long-Term Vision
Liability-relevant environments are becoming increasingly distributed, automated, interconnected, cross-organizational, and difficult to reduce to one event, one actor, one Relationship, or one legal process.
AI systems may contribute to decisions without independently holding the complete operational role surrounding those decisions.
Autonomous systems may perceive, decide, and act across physical environments.
Multi-agent systems may distribute one operational objective across many agents.
Digital platforms may connect millions of users, providers, contractors, and automated systems.
Global supply chains may distribute production, ownership, control, insurance, maintenance, and operational Responsibility across multiple organizations.
Infrastructure systems may depend on interconnected public and private actors.
One Harm event may create multiple Liability Relationships.
One payment may create Recourse.
One Transfer may create a new secondary Relationship.
One Settlement may resolve only part of a Liability Network.
One Finality determination may apply only to one Relationship.
New information may later require targeted Re-Entry.
As this transition accelerates, the central question will no longer be only:
Who is liable?
It will also be:
What exactly is the Liability Object, on what Basis can Liability exist, which Subjects and Relationships participate, what Conditions apply, what Connection has been established, has Liability legitimately attached, what is its Scope, how is it allocated, what is its current State, how has it changed, has it moved or created Recourse, what has been resolved or discharged, what remains active, what history must remain reconstructable, and when can the Liability lifecycle legitimately reach Finality?
The long-term objective of LIGA™ is to provide a common Liability Governance language through which humans, organizations, AI systems, autonomous systems, insurers, public institutions, infrastructure operators, contractual networks, and future operational environments can identify, distinguish, determine, scope, allocate, track, transfer, resolve, reconstruct, reopen, and bring Liability to legitimate Finality without confusing Liability with the event that preceded it, Harm associated with it, evidence supporting it, Accountability surrounding it, Claims relating to it, payment resulting from it, or Value consequences connected to it.
LIGA™ is intended to make Liability governable from relevance and potential formation through Determination, active governance, Resolution, Re-Entry where required, and Finality.
Canonical Principle
Human systems, AI systems, autonomous technologies, contractual environments, insurance networks, digital platforms, infrastructure, organizational processes, legal systems, and Liability-relevant mechanisms will continue to change. Liability Governance must remain stable. LIGA™ therefore governs the methodological conditions that determine the context in which Liability may become relevant, what 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 that State changes, how Liability may be transferred, shared, succeeded, or create Recourse, when active Liability may legitimately be resolved or discharged, how its complete history remains continuous and reconstructable, when material change requires governed Re-Entry, and when the complete Liability lifecycle can legitimately reach Finality.
Canonical Closing Statement
LIGA™ — Liability Governance Architecture provides the governance foundation through which Liability involving individuals, groups, organizations, physical and digital objects, AI systems, autonomous systems, infrastructure, institutions, contractual networks, and future operational environments can be contextually identified, structured around an explicit Liability Object, grounded in an applicable Liability Basis, organized through distinct Liability Subjects and Relationships, governed through applicable Conditions, connected through sufficiently governed Liability-Relevant Connections, legitimately determined and attached where justified, scoped, allocated, maintained through active Liability States and Changes, transferred, shared, succeeded, or connected to Recourse where applicable, brought into legitimate Resolution and Discharge, preserved through complete lifecycle Continuity and historical reconstructability, returned through targeted ReEntry where material circumstances change, and ultimately brought to governed Finality. By defining the independent governable spaces of the complete Liability Lifecycle, LIGA™ establishes a methodology-neutral and technology-neutral architecture for ensuring that Liability remains governable without requiring one legal system, jurisdiction, insurer, Claims process, contractual model, AI system, autonomous technology, evidence system, or operational mechanism to define Liability Governance itself. LIGA™ therefore establishes Liability Governance as a distinct methodological layer around Liability itself, enabling Liability to remain identifiable, object-bounded, basis-grounded, relationally structured, condition-aware, sufficiently connected, 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.