About Liability Conditions Standard (LCOS)
About Liability Conditions Standard (LCOS)
What Is the Liability Conditions Standard?
The Liability Conditions Standard (LCOS) is the LIGA™ Parent Standard governing the conditions that must be evaluated before potential Liability can proceed from an established Liability Basis and Liability Relationship Structure toward Liability Connection and later Liability Determination.
LCOS establishes a governed structure for identifying what must be true, false, present, absent, satisfied, failed, changed, or excepted under the applicable Liability Basis.
It prevents Liability governance from moving directly from the existence of a Basis, Relationship, Harm, Loss, Breach, Fault, adverse outcome, or other significant fact to a Liability conclusion without first governing the Conditions that the applicable Basis actually requires.
Canonical Meaning
A Liability Condition is a governed requirement, circumstance, state, threshold, dependency, exception, exclusion, or other conditional element whose existence, absence, satisfaction, failure, change, or applicability may materially affect whether potential Liability can proceed under a Governed Liability Basis.
A Liability Basis explains why Liability may potentially exist.
Liability Conditions establish what must be true under that Basis.
Neither establishes Liability by itself.
Liability Basis ≠ Liability Conditions.
Liability Condition ≠ Liability.
Condition Satisfaction ≠ Liability Determination.
Why Is LCOS Necessary?
Liability cannot be governed reliably merely by identifying:
an event, a Liability Object, a Liability Basis, relevant Subjects, or the Relationships among them.
The applicable Basis may require additional Conditions before Liability can legitimately proceed toward Determination.
Those Conditions may concern:
conduct, knowledge, authority, control, timing, performance, non-performance, thresholds, relationships, Subject states, Object states, exceptions, exclusions, or other governed requirements.
Without LCOS, these requirements can remain implicit, be applied inconsistently, or be replaced by assumptions based on outcome.
LCOS makes the conditional structure explicit.
What Does LCOS Govern?
LCOS governs the methodological structure of Liability Conditions, including:
Condition Identification, Condition Identity, Condition Origin, Condition Requirement, Condition Applicability, Condition Type, Condition State, Condition Satisfaction, Condition Failure, Positive and Negative Conditions, Threshold Conditions, Temporal Conditions, Subject-Specific Conditions, Relationship-Specific Conditions, Object-Specific Conditions, Basis-Specific Conditions, Concurrent Conditions, Alternative Conditions, Cumulative Conditions, Sequential Conditions, Dependent Conditions, Nested Conditions, Exceptions, Exclusions, Condition Conflict, Condition Uncertainty, Condition Change, Condition Correction, Condition Reassessment, and Condition Continuity.
Its principal output is:
Governed Liability Condition Structure
What Does LCOS Not Govern?
LCOS does not determine:
whether the required Liability-Relevant Connection exists, whether Liability attaches, whether Liability is ultimately determined, how far Liability extends, how Liability is allocated, how Liability later changes, whether Liability is transferred or creates Recourse, whether Liability is resolved or discharged, or whether Liability reaches Finality.
These questions belong to subsequent LIGA™ governance spaces.
LCOS also does not replace jurisdiction-specific courts, regulators, arbitrators, insurers, contractual authorities, or other legally empowered decision-makers.
Liability Basis and Liability Conditions
The distinction between Basis and Conditions is foundational.
The Liability Basis answers:
Why can Liability potentially exist?
The Liability Conditions answer:
What must be true under that Basis?
A Basis may exist while one or more required Conditions remain unsatisfied.
Therefore:
Applicable Liability Basis ≠ Satisfied Liability Conditions.
A Condition must not be invented merely because an adverse outcome occurred.
Its relevance must derive from the applicable Basis.
Condition Requirement and Condition State
Every governed Condition should distinguish:
what is required, from:
whether that requirement is satisfied.
The Condition Requirement defines the state that must be evaluated.
The Condition State represents the governed result of that evaluation.
Therefore:
Condition Requirement ≠ Condition State.
and:
Condition Requirement ≠ Condition Satisfaction.
This separation prevents the requirement itself from being treated as proof that it was fulfilled.
Condition Applicability
A Condition may exist within a wider Liability Basis without applying to every Subject, Relationship, Object, or circumstance.
LCOS therefore governs applicability separately from satisfaction.
A Condition may be:
Applicable, Not Applicable, Conditionally Applicable, or unresolved as to applicability.
Therefore:
Condition Existence ≠ Condition Applicability.
and:
Non-Applicable Condition ≠ Failed Condition.
Condition States
LCOS supports explicit Condition States such as:
Satisfied, Not Satisfied, Partially Satisfied, Failed, Present, Absent, Not Applicable, Unknown, Uncertain, Disputed, or Pending.
These states prevent incomplete information from being forced into a binary conclusion.
In particular:
Unknown Condition State ≠ Failed Condition.
Unknown Condition State ≠ Satisfied Condition.
Multiple Conditions
Potential Liability may depend on more than one Condition.
Conditions may operate as:
concurrent requirements, alternatives, sequences, cumulative requirements, dependencies, or nested structures.
For example:
Condition A AND Condition B
is different from:
Condition A OR Condition B
and from:
Condition A → Condition B LCOS preserves these structures rather than collapsing them into one generalized Condition.
Subject- and Relationship-Specific Conditions
Conditions may differ across Subjects and Relationships.
A Condition satisfied for one Subject does not automatically apply to another.
Likewise, a Subject may have different Condition States in different Relationships.
Therefore:
Condition Satisfaction for Subject A ≠ Condition Satisfaction for Subject B.
and:
Condition State in Relationship A ≠ Condition State in Relationship B.
This becomes particularly important in multi-party Liability structures.
Temporal Conditions
Conditions may depend upon the state that existed at a specific time.
A current state cannot automatically be projected backward.
Therefore:
Condition State at T2 ≠ Condition State at T1 by default.
LCOS preserves temporal Condition States so later Liability governance can evaluate the matter against the correct historical reality.
Exceptions and Exclusions
LCOS separately governs Conditions, Exceptions, and Exclusions.
An Exception may modify the ordinary operation of a Condition.
An Exclusion may remove a defined matter from the Condition's applicability.
Therefore:
Exception ≠ Condition Absence.
Exclusion ≠ Failed Condition.
Exception ≠ Exclusion.
Their existence and applicability must be explicitly governed.
Conditions and Harm
Harm may be relevant to some Liability Conditions.
Where it is relevant, HAGA™ may provide the governed Harm state.
However, Liability does not universally require Harm.
Therefore:
Established Harm ≠ Satisfied Liability Conditions by default.
and:
Harm ≠ Universal Liability Condition.
This preserves the architectural boundary between HAGA™ and LIGA™.
Conditions and Fault
Fault may be required under some Liability Bases and irrelevant under others.
LCOS therefore does not treat Fault as a universal Liability requirement.
Fault ≠ Universal Liability Condition.
The applicable Liability Basis determines whether Fault is conditionally relevant.
Conditions and Breach
A Breach may become relevant under an applicable Liability Basis.
However:
Breach ≠ Liability.
and:
Breach ≠ Liability Condition Satisfaction by default.
LCOS determines how the relevant Condition should be represented and evaluated without converting Breach directly into Liability.
Conditions and Responsibility
Responsibility may provide an input to a Liability Condition where relevant.
AGA™ remains responsible for governing Responsibility itself.
Therefore:
Responsibility ≠ Liability.
and:
Responsibility ≠ Liability Condition Satisfaction by default.
An externally governed Responsibility state may enter LCOS without becoming a Liability conclusion.
Conditions and Operational Reality
ORA™ may provide operational states required for Condition evaluation.
For example, LCOS may need to know:
who actually operated a system, whether a Subject actually exercised control, whether an action occurred, or whether a required operational state existed.
ORA™ governs that Operational Reality.
LCOS governs its conditional significance.
Therefore:
Operational Reality ≠ Liability Condition State by itself.
Conditions and Evidence
ADIT® may provide evidence supporting Condition evaluation.
Evidence may establish or challenge facts relevant to a Condition.
However:
Evidence ≠ Condition Satisfaction.
LCOS evaluates the governed Condition Requirement against the relevant inputs.
The evidence and the resulting Condition State remain separate governance objects.
Conditions and Liability Connection
The boundary between LCOS and the next LIGA™ Parent Standard is critical.
LCOS determines the governed Condition Structure.
LCNS determines whether the required Liability-Relevant Connection exists.
Therefore:
Satisfied Conditions ≠ Liability-Relevant Connection.
All required Conditions may appear satisfied while the required Liability-Relevant Connection remains absent.
Conversely, a strong operational or factual connection may exist while required Liability Conditions remain unsatisfied.
Therefore:
Condition Satisfaction ≠ Connection Satisfaction.
Connection ≠ Condition Satisfaction.
Conditions and Liability Determination
Condition Satisfaction is not Liability Determination.
The governed sequence remains:
Basis → Relationships → Conditions → Connection → Determination not:
Condition Satisfaction → Liability Even a fully satisfied Condition Structure remains an input to later Liability governance.
Therefore:
Satisfied Liability Conditions ≠ Liability Attachment.
Satisfied Liability Conditions ≠ Established Liability.
Position in the LIGA™ Governance Flow
The canonical LIGA™ Governance Flow is:
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 LCOS occupies the fifth governance space:
Liability Conditions
It receives a:
Governed Liability Relationship Structure
and produces a:
Governed Liability Condition Structure
for Liability Connection governance.
Relationship to Adjacent Standards
LBS — Liability Basis Standard establishes why Liability may potentially exist.
LRS — Liability Relationship Standard establishes the Subjects and Relationships participating in the potential Liability structure.
LCOS — Liability Conditions Standard establishes what must be true under the applicable Basis.
LCNS — Liability Connection Standard determines whether the required Liability-Relevant Connection exists.
LDS — Liability Determination Standard later determines whether Liability can legitimately attach and be determined.
The sequence prevents one governance question from substituting for another.
Critical Distinctions
Liability Basis ≠ Liability Conditions Liability Condition ≠ Liability Condition Identity ≠ Condition State Condition Requirement ≠ Condition Satisfaction Condition Existence ≠ Condition Applicability Non-Applicable Condition ≠ Failed Condition Applicable Condition ≠ Satisfied Condition Unknown Condition State ≠ Failed Condition Partial Satisfaction ≠ Full Satisfaction Exception ≠ Exclusion Condition Satisfaction ≠ Liability-Relevant Connection Connection ≠ Condition Satisfaction Satisfied Liability Conditions ≠ Liability Attachment Satisfied Liability Conditions ≠ Liability Determination Fault ≠ Universal Liability Condition Harm ≠ Universal Liability Condition Breach ≠ Liability Responsibility ≠ Liability Condition Satisfaction by default Evidence ≠ Condition Satisfaction Adverse Outcome ≠ Satisfied Liability Conditions
Use Case 1 — AI-Enabled Service
An AI-enabled service involves a provider, deploying organization, operator, customer, and AI system whose relevant relationships have already been governed through LRS.
An applicable Liability Basis requires evaluation of several Conditions concerning operational authority, control, required safeguards, relevant knowledge, and actions taken during the applicable period.
LCOS identifies each Condition separately, determines which Subjects and Relationships it applies to, preserves the relevant temporal state, and records whether each Condition is satisfied, unsatisfied, unknown, disputed, or subject to an Exception.
The existence of an adverse AI output does not automatically satisfy those Conditions.
The resulting Governed Liability Condition Structure proceeds to LCNS for Liability-Relevant Connection governance.
Use Case 2 — Industrial Equipment Matter
An industrial equipment matter involves an owner, operating company, maintenance provider, subcontractor, operator, and manufacturer.
The applicable Liability Basis requires evaluation of Conditions concerning maintenance requirements, operational authority, relevant equipment state, timing, and defined performance requirements.
LCOS evaluates those Conditions against the relevant Subjects, Relationships, and historical states.
A maintenance relationship alone does not establish that a maintenance-related Condition was satisfied or failed.
Likewise, equipment Harm or Loss does not automatically establish the required conditional structure.
LCOS produces the governed Condition Structure required for subsequent Liability Connection analysis without determining which party bears Liability.
Canonical Closing Statement
Liability cannot be governed reliably by moving directly from a Basis, Relationship, Breach, Harm, Fault, or adverse outcome to a Liability conclusion.
The applicable Conditions must first be made explicit, associated with the correct Subjects and Relationships, evaluated in the correct temporal context, and preserved with their dependencies, Exceptions, Exclusions, and uncertainty.
Conditions establish what must be true. They do not establish Liability.
Govern the Conditions before determining the Connection.