Liability Basis Standard (LBS)
Liability Basis Standard (LBS)
Architecture: LIGA™ — Liability Governance Architecture
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Parent Standard
Governed Space: Liability Basis
Standard ID: LIGA-LBS-001
Origin ID: OOF.PS.LIGA.03.00.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 21 September 2026
Compatibility: OOF® Methodology OS™ · Modular OOF® Architecture Ecosystem
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection: MIP® — Methodological Intellectual Property
Canonical Language: English (UCL™)
Canonical Definition
The Liability Basis Standard (LBS) governs how the basis upon which Liability may potentially exist in relation to a Governed Liability Object is identified, classified, qualified, associated, and maintained so that subsequent Liability governance proceeds from an explicit and traceable Liability Basis rather than from consequence, assertion, assumption, responsibility, Harm, Loss, Damage, or perceived wrongdoing alone.
A Liability Basis establishes the governed foundation under which Liability may potentially arise.
It does not establish that Liability exists.
Liability Basis ≠ Liability Determination.
Operational Role
The operational role of LBS is:
to establish the governed foundation upon which Liability may potentially exist before Liability Subjects and Relationships, applicable Liability Conditions, Liability-Relevant Connection, Attachment, or Liability Determination are evaluated.
LOS establishes:
What is the governed Liability Object?
LBS establishes:
On what governed basis can Liability potentially exist in relation to that Object?
LBS therefore prevents Liability governance from proceeding directly from an observed consequence or allegation to a Liability conclusion.
Core Question
On what governed basis can Liability potentially exist?
Position in the LIGA™ Governance Flow
The complete 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 LBS governs:
Liability Basis
Its canonical transition is:
Governed Liability Object → Liability Basis Identification → Basis Classification → Basis Qualification → Basis Association → Governed Liability Basis → Liability Relationship Governance
Governed Space
LBS begins when a Governed Liability Object exists and the methodological question becomes:
Under what basis could Liability potentially arise in relation to this Object?
LBS governs:
Liability Basis Identification, Basis Origin, Basis Source, Basis Type, Basis Classification, Basis Qualification, Basis Applicability, Basis Association, Multiple Liability Bases, Alternative Liability Bases, Concurrent Liability Bases, Competing Liability Bases, Conditional Liability Bases, Basis Uncertainty, Basis Conflict, Basis Change, Basis Supersession, Basis Continuity, and Basis Readiness.
LBS ends when one or more Liability Bases are sufficiently governed for Liability Relationship governance.
Why Liability Basis Is Necessary
A Liability-relevant matter does not become Liability merely because:
Harm occurred, Loss occurred, Damage occurred, a duty may exist, an obligation was asserted, a person acted, a system failed, a Claim was made, or responsibility was alleged.
Liability requires a governed basis under which Liability can potentially exist.
Without that basis, later governance risks converting consequence or allegation directly into Liability.
The canonical sequence is:
Liability-Relevant Matter → Governed Liability Object → Liability Basis → Further Liability Governance not:
Consequence → Liability.
Liability Basis as a Governance Foundation
A Liability Basis is the methodological foundation that makes a potential Liability inquiry structurally possible.
It establishes the relevant governed reason why Liability may be considered.
A Basis may originate from different governance environments and authoritative structures.
LBS does not decide the ultimate legal meaning of those structures.
It governs how the basis is identified and represented for the Liability lifecycle.
Basis Origin
Every Liability Basis should have an identifiable origin.
Basis Origin may arise from a:
legal rule, contractual structure, statutory requirement, regulatory requirement, organizational rule, governed obligation, undertaking, warranty, guarantee, ownership relationship, control relationship, assumed responsibility, or another recognized Liability-relevant foundation.
The origin must be traceable.
Therefore:
Liability Assertion ≠ Liability Basis Origin.
Basis Source
Basis Source identifies the governed source from which the potential Liability Basis derives.
The source should be distinguishable from:
the person asserting the Basis, the evidence proving the source, the Object to which the Basis may apply, and the later determination concerning Liability.
Therefore:
Basis Source ≠ Basis Assertion.
and:
Basis Source ≠ Liability Determination.
Basis Identification
LBS requires explicit identification of the potential Liability Basis.
A basis should not remain implicit merely because participants assume that it exists.
The identified Basis should answer:
What is the proposed foundation for potential Liability?
Where does that foundation originate?
What type of Basis is it?
To what Object may it relate?
What uncertainty exists?
The identification stage does not establish that the Basis ultimately applies.
Potential Basis and Governed Basis
A possible reason for Liability may initially exist only as a Basis Candidate.
The canonical progression is:
Potential Basis → Identified Basis → Classified Basis → Qualified Basis → Associated Basis → Governed
Liability Basis
Therefore:
Potential Liability Basis ≠ Governed Liability Basis.
A Basis becomes governance-ready only after sufficient methodological processing.
Basis Classification
A Liability Basis should be classified according to its governed nature.
Classification may distinguish, where applicable:
contractual basis, statutory basis, regulatory basis, ownership-related basis, control-related basis, duty-related basis, undertaking-related basis, warranty-related basis, guarantee-related basis, strict or status-based basis, or another appropriately defined category.
Classification is methodological.
It must not substitute for jurisdiction-specific legal classification.
Therefore:
Methodological Basis Classification ≠ Jurisdiction-Specific Legal Classification.
Basis Qualification
Identification and classification alone are insufficient.
A proposed Basis must also be qualified.
Qualification asks whether the identified foundation is sufficiently coherent, attributable, applicable in principle, and governable to proceed into subsequent Liability governance.
Qualification may evaluate:
source integrity, basis identity, basis status, relevant authority, potential applicability, known limitations, known exclusions, uncertainty, and temporal relevance.
Qualification does not determine whether all Liability Conditions are satisfied.
Basis Qualification and Liability Conditions
LBS determines whether a Basis is sufficiently established as a potential foundation for Liability governance.
LCOS later determines what conditions must exist, fail, change, or be satisfied under that Basis.
Therefore:
Liability Basis ≠ Liability Conditions.
and:
Basis Qualification ≠ Condition Satisfaction.
A qualified Basis may later fail because its required Liability Conditions are not satisfied.
Basis Applicability
A valid Basis may exist generally without being applicable to the specific Governed Liability Object.
LBS must therefore distinguish:
Basis Existence
from:
Potential Basis Applicability.
The relevant question is whether the Basis is capable, in principle, of applying to the governed matter.
Therefore:
Existing Liability Basis ≠ Applicable Liability Basis by default.
Object–Basis Association
A Liability Basis must be explicitly associated with the Governed Liability Object to which it may apply.
The canonical structure is:
Governed Liability Object ↔ Governed Liability Basis
This association does not establish Liability.
It establishes that the Basis is methodologically relevant to further Liability governance concerning that Object.
Therefore:
Object–Basis Association ≠ Liability Attachment.
Liability Object and Liability Basis
The Liability Object and Liability Basis perform different governance functions.
The Object answers:
What is the matter?
The Basis answers:
Why could Liability potentially exist in relation to that matter?
Therefore:
Liability Object ≠ Liability Basis.
The Object must not be redefined merely to fit a preferred Basis.
Likewise, the Basis must not redefine the Object silently.
Basis and Liability Subject
A Liability Basis may exist before the complete set of Liability Subjects is established.
For example, a Basis may be identified in relation to an Object while it remains uncertain which parties participate in the resulting Liability structure.
Therefore:
Liability Basis ≠ Liability Subject.
and:
Basis Identification ≠ Subject Identification.
LRS governs Liability Subjects and Relationships.
Basis and Liability Relationship
A Basis may support one or more potential Liability Relationships.
However:
Liability Basis ≠ Liability Relationship.
A single Basis may apply differently across multiple Relationships.
Multiple Bases may also apply to one Relationship.
LRS governs the Relationship structure.
LBS governs the Basis structure.
Basis and Responsibility
Responsibility may be relevant to a Liability Basis.
It is not identical to Liability.
AGA™ may establish Responsibility structures that become inputs to LIGA™.
Therefore:
Responsibility ≠ Liability Basis by default.
and:
Responsibility ≠ Liability.
Responsibility may support or contextualize a Basis only where the relevant governance structure establishes that relationship.
Basis and Accountability
Accountability may identify who must answer for conduct, decisions, systems, or outcomes.
That does not automatically establish a Liability Basis.
Therefore:
Accountability ≠ Liability Basis by default.
and:
Accountability ≠ Liability.
AGA™ retains governance ownership of Accountability.
LBS governs only its potential relevance to Liability Basis.
Basis and Fault
Fault may be relevant under some Liability Bases.
Other Bases may not require fault.
Therefore:
Fault ≠ Liability Basis.
and:
Absence of Fault ≠ Absence of Liability Basis by default.
LBS must not assume a universal fault model.
Basis and Breach
A breach may become relevant under a particular Liability Basis.
But:
Breach ≠ Liability Basis.
The Basis may establish the governed framework within which a breach becomes relevant.
Whether a breach occurred may belong to subsequent Conditions, Connection, Determination, or an external governed domain depending on the matter.
Basis and Obligation
An obligation may form or contribute to a Liability Basis.
However, not every obligation automatically establishes a Liability Basis.
Therefore:
Obligation ≠ Liability Basis by default.
The obligation must be identified, qualified, and associated with the relevant Liability Object.
Basis and Harm
Harm may be relevant to some Liability Bases.
Other Liability Bases may operate without established Harm.
Therefore:
Harm ≠ Liability Basis.
and:
Absence of Harm ≠ Absence of Liability Basis by default.
HAGA™ governs Harm.
LBS governs the potential Liability foundation.
Basis and Loss or Damage
Loss or Damage may be required, relevant, or irrelevant depending on the applicable Basis.
They must not automatically be treated as the Basis itself.
Therefore:
Loss ≠ Liability Basis.
Damage ≠ Liability Basis.
A consequence may become a condition or input without becoming the foundation for Liability.
Basis and Claim
A Claim may assert a Liability Basis.
That assertion does not establish the Basis.
Therefore:
Claimed Basis ≠ Governed Liability Basis.
Likewise:
Claim Acceptance ≠ Liability Basis Validation.
Claim Rejection ≠ Absence of Liability Basis.
Claims and Liability remain separate governed concepts.
Basis and Evidence
Evidence may establish or challenge:
the existence of a Basis, its source, its status, its applicability, or its relationship to the Object.
However:
Evidence of a Liability Basis ≠ Liability Basis itself.
ADIT® governs evidence.
LBS governs the methodological Basis derived from sufficiently governed information.
Basis and Authority
Some Liability Bases depend on the authority of the source from which they arise.
LBS should preserve relevant authority references where necessary.
However:
Authority ≠ Liability Basis by default.
Authority may enable a rule, obligation, undertaking, or other structure that becomes Basis-relevant.
The authority structure remains independently governed.
Basis and Jurisdiction
A Liability Basis may depend on a particular jurisdiction or authoritative environment.
LBS may represent that dependency.
It does not decide jurisdiction-specific legal questions on behalf of courts, regulators, arbitrators, or other competent authorities.
Therefore:
Jurisdictional Relevance ≠ Jurisdictional Legal Determination.
LBS structures the Basis.
It does not replace jurisdiction-specific legal interpretation.
Temporal Basis Validity
A Basis may exist at one time and not another.
LBS must therefore preserve relevant temporal states such as:
effective, not yet effective, expired, superseded, terminated, amended, or uncertain.
The Basis applicable today may differ from the Basis relevant at the Liability-relevant moment.
Therefore:
Current Basis State ≠ Historical Basis State.
Basis Change
A Liability Basis may change after the Liability Object has been formed.
Change may result from:
amendment, replacement, termination, expiration, new authoritative interpretation, contractual modification, or another governed event.
The change must be represented without rewriting the earlier Basis state.
Therefore:
Basis Change ≠ Historical Basis Erasure.
Multiple Liability Bases
One Liability Object may be associated with multiple Liability Bases.
For example:
Object A → Basis 1 + Basis 2 + Basis 3 Each Basis must remain separately governable.
Therefore:
One Liability Object ≠ One Liability Basis.
The existence of several Bases does not imply that all will later support Liability.
One Basis Across Multiple Objects
One Liability Basis may potentially apply to multiple Liability Objects.
Therefore:
One Liability Basis ≠ One Liability Object.
Each Object–Basis association must be governed independently where material differences exist.
A Basis applicable to Object A does not automatically apply to Object B.
Alternative Liability Bases
Several Bases may represent alternative routes through which Liability could potentially arise.
The structure may be:
Basis A OR Basis B OR Basis C
Alternative Bases must not be collapsed merely because they could lead to similar Liability outcomes.
Each Basis may have different:
Conditions, Relationships, Connection requirements, scope implications, and determination logic.
Concurrent Liability Bases
Several Liability Bases may operate concurrently.
The structure may be:
Basis A + Basis B
Concurrent operation does not make the Bases identical.
Therefore:
Concurrent Bases ≠ Single Basis.
Each Basis must preserve its own identity, source, qualification, conditions, and lifecycle state.
Competing Liability Bases
Two or more proposed Bases may conflict or compete.
For example, participants may disagree about:
which Basis applies, whether one Basis excludes another, or which Basis governs the relevant Object.
LBS must preserve the conflict where it cannot yet be legitimately resolved.
Therefore:
Basis Conflict ≠ Governance Failure.
Explicit unresolved conflict is preferable to false methodological certainty.
Conditional Liability Basis
A Basis may be potentially applicable only if certain later conditions are satisfied.
This does not prevent it from being identified as a Liability Basis.
The correct state may be:
Qualified Basis — Conditional Applicability
rather than:
Established Liability.
Therefore:
Conditional Basis Applicability ≠ Liability Attachment.
Basis Uncertainty
Uncertainty may concern:
Basis existence, source, classification, qualification, applicability, authority, temporal status, Object association, or interaction with another Basis.
LBS must represent uncertainty explicitly.
Possible states may include:
Identified
Qualified
Conditionally Applicable
Uncertain
Disputed
Competing
Superseded
Inactive
where appropriate.
Therefore:
Basis Uncertainty ≠ Basis Absence.
Basis Assumptions
A proposed Liability Basis may depend on assumptions.
Examples include assumptions concerning:
source validity, authority, temporal applicability, contractual status, ownership, control, or another underlying structure.
Material assumptions must remain visible.
Therefore:
Basis Assumption ≠ Established Basis Fact.
Later validation or new evidence may require reassessment.
Basis Exclusion
A candidate Basis may be determined to be inapplicable to the governed Object.
Exclusion should preserve:
the Basis considered, the reason for exclusion, the relevant state, and the relationship to the Object.
Therefore:
Excluded Basis ≠ Never-Considered Basis.
Historical Basis governance should remain reconstructable.
Basis Supersession
A Liability Basis may be superseded by another Basis state or source.
Supersession may affect future governance without erasing the earlier Basis.
Therefore:
Basis Supersession ≠ Historical Deletion.
The relevant lifecycle moment determines which Basis state may matter.
Basis Continuity
A Liability Basis may persist across:
amendments, versions, technical representations, organizational systems, or later Liability stages.
Its identity and lineage should remain reconstructable.
Therefore:
Current Liability Basis ≠ Complete Liability Basis History.
Basis continuity allows later governance to determine which Basis existed and which state applied at the relevant moment.
Basis Reassessment
New information may require Basis reassessment.
Reassessment may:
confirm the Basis, change its classification, change its qualification, change its applicability, exclude it, identify an additional Basis, or establish that a previously governed Basis no longer applies.
Reassessment must preserve earlier states.
Therefore:
Basis Reassessment ≠ Historical Rewrite.
Basis Readiness
A Liability Basis is ready for Liability Relationship governance when it is sufficiently:
identified, sourced, classified, qualified, associated with the relevant Liability Object, temporally situated, traceable, and explicit about material uncertainty.
Readiness does not require Liability to be established.
Therefore:
Basis Readiness ≠ Liability Determination Readiness.
Potential Liability Formation
LBS contributes to the formation of Potential Liability by establishing a governed Basis in relation to a Governed Liability Object.
The canonical structure is:
Governed Liability Object + Governed Liability Basis → Structured Potential Liability Inquiry This is not Liability Attachment.
It establishes only that the matter has progressed beyond general Liability relevance into a structured Liability inquiry.
Therefore:
Potential Liability ≠ Attached Liability.
Liability Attachment
Liability Attachment belongs to Liability Determination governance.
LBS must not determine Attachment merely because a Basis has been established.
The lifecycle distinction is:
Liability Basis → Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Attachment / Determination State Therefore:
Liability Basis ≠ Liability Attachment.
Basis Failure
A Liability inquiry may legitimately end or narrow because no sufficient Basis can be established.
That outcome must be distinguishable from:
failure of Conditions, failure of Connection, or a later negative Liability Determination.
Therefore:
No Governed Liability Basis ≠ Failed Liability Conditions.
No Governed Liability Basis ≠ Failed Liability Connection.
No Governed Liability Basis ≠ Negative Liability Determination.
The lifecycle stage at which the inquiry fails matters.
Basis Dependency
One Liability Basis may depend on another governed structure.
For example, a Basis may depend on:
an underlying obligation, an ownership state, an authority state, a contractual relationship, or another Basis.
Dependency must be explicit.
Therefore:
Basis Dependency ≠ Basis Identity.
A dependent Basis remains separately governable where its meaning is distinct.
Basis Hierarchy
Some Liability structures may contain hierarchical Basis relationships.
A higher-level foundation may authorize or generate a more specific Basis.
The hierarchy may be represented as:
Foundational Source → Derived Basis → Object-Specific Basis Association Hierarchy must not be confused with applicability.
Therefore:
Higher Basis Authority ≠ Automatic Object-Specific Applicability.
Basis Network
Complex Liability matters may contain a network of interacting Bases.
The network may contain:
parallel Bases, alternative Bases, dependent Bases, competing Bases, superseded Bases, and Bases associated with different Liability Relationships.
LBS must preserve the structure without collapsing it into a single generic reason for Liability.
Therefore:
Multiple Liability Bases ≠ One Composite Basis by default.
Governance Requirements
A conforming implementation of LBS should ensure that:
every material Liability Basis can be explicitly identified;
the Basis has a traceable origin and source;
the Basis is methodologically classified;
the Basis is sufficiently qualified;
potential applicability to the Governed Liability Object is explicit;
Object–Basis association is governed;
Basis and Liability Conditions remain distinct;
Basis and Liability Attachment remain distinct;
Basis and Liability Determination remain distinct;
multiple, alternative, concurrent, dependent, and competing Bases remain separately identifiable;
temporal Basis states are preserved where material;
Basis uncertainty and assumptions remain explicit;
Basis exclusions remain traceable;
Basis changes and supersession preserve history;
Basis reassessment does not rewrite earlier states;
Basis continuity remains reconstructable;
jurisdiction-specific legal determination is not replaced by methodological governance;
downstream governance receives a sufficiently governed Liability Basis rather than an implicit Liability assumption.
Governance Logic
The canonical LBS governance logic is:
Governed Liability Object
↓
Identify Potential Liability Basis
↓
Identify Basis Origin and Source
↓
Classify Basis
↓
Qualify Basis
↓ Is the Basis potentially applicable to the Governed Liability Object?
If no:
Record Basis Exclusion / Inapplicability
If uncertain:
Preserve Basis Uncertainty / Conditional Applicability
If yes:
↓
Associate Basis with Governed Liability Object
↓
Identify Multiple / Alternative / Concurrent / Competing / Dependent Bases
↓
Establish Relevant Temporal Basis State
↓
Identify Material Assumptions and Conflicts
↓
Preserve Basis Lineage and Continuity
↓
Assess Basis Readiness
If insufficient:
Clarify / Validate / Reassess / Exclude / Preserve Uncertainty
If sufficient:
↓
Governed Liability Basis
↓
Handoff to Liability Relationship Governance
Governance Outputs
LBS may produce:
Liability Basis Candidate
Liability Basis Identity
Liability Basis Origin
Liability Basis Source
Liability Basis Classification
Liability Basis Qualification State
Liability Basis Applicability State
Object–Basis Association
Alternative Basis Structure
Concurrent Basis Structure
Competing Basis Structure
Dependent Basis Structure
Basis Hierarchy
Basis Network
Basis Temporal State
Basis Uncertainty State
Basis Assumption Record
Basis Conflict State
Basis Exclusion Record
Basis Change Record
Basis Supersession Record
Basis Reassessment Record
Basis Continuity Record
Basis Readiness State
The principal output is:
Governed Liability Basis
The canonical handoff is:
Governed Liability Basis → Liability Relationship Governance
Critical Distinctions
LBS preserves the following distinctions:
Liability Basis ≠ Liability Determination Liability Assertion ≠ Liability Basis Origin Basis Source ≠ Basis Assertion Potential Liability Basis ≠ Governed Liability Basis Methodological Basis Classification ≠ Jurisdiction-Specific Legal Classification Liability Basis ≠ Liability Conditions Basis Qualification ≠ Condition Satisfaction Existing Liability Basis ≠ Applicable Liability Basis by default Object–Basis Association ≠ Liability Attachment Liability Object ≠ Liability Basis Liability Basis ≠ Liability Subject Liability Basis ≠ Liability Relationship Responsibility ≠ Liability Basis by default Responsibility ≠ Liability Accountability ≠ Liability Basis by default Accountability ≠ Liability Fault ≠ Liability Basis Breach ≠ Liability Basis Obligation ≠ Liability Basis by default Harm ≠ Liability Basis Loss ≠ Liability Basis Damage ≠ Liability Basis Claimed Basis ≠ Governed Liability Basis Evidence of a Liability Basis ≠ Liability Basis itself Authority ≠ Liability Basis by default Jurisdictional Relevance ≠ Jurisdictional Legal Determination Current Basis State ≠ Historical Basis State One Liability Object ≠ One Liability Basis One Liability Basis ≠ One Liability Object Concurrent Bases ≠ Single Basis Conditional Basis Applicability ≠ Liability Attachment Basis Uncertainty ≠ Basis Absence Basis Assumption ≠ Established Basis Fact Basis Supersession ≠ Historical Deletion Current Liability Basis ≠ Complete Liability Basis History Basis Reassessment ≠ Historical Rewrite Basis Readiness ≠ Liability Determination Readiness Potential Liability ≠ Attached Liability Liability Basis ≠ Liability Attachment Basis Dependency ≠ Basis Identity Higher Basis Authority ≠ Automatic Object-Specific Applicability Multiple Liability Bases ≠ One Composite Basis by default
Cross-Architecture Boundary
LBS may receive governed inputs from other OOF® architectures without taking ownership of their original governed domains.
GOA™ may provide Authority, Scope, Delegation, Accountability, or other governance structures relevant to a potential Liability Basis.
ORA™ may provide Operational Reality concerning the matter to which a Basis may apply.
AGA™ may provide governed Responsibility, Accountability, Authority, or Attribution structures relevant to Basis formation.
HAGA™ may provide governed Harm states where Harm is relevant to a particular Basis.
ADIT® may provide evidence concerning Basis source, status, authority, applicability, or historical state.
VALIDOS™ may validate Basis-relevant inputs without determining Liability.
OBIDENITY® may provide Identity, Ownership, Authority, Permission, Provenance, Transfer, or Continuity structures relevant to a Basis.
AIG® and ASGA™ may provide governed AI or autonomous-system states relevant to a Liability Basis.
SIMULOS® may provide governed Simulation states relevant to a Basis.
PGA™ may provide governed Prediction states relevant to a Basis.
VFM® may provide governed Value relationships relevant to a Basis.
The cross-architecture principle is:
An externally governed state may contribute to a Liability Basis without becoming Liability or transferring governance ownership of its original domain to LIGA™.
Relationship to the Complete Liability Lifecycle
LBS is an early formation stage within the complete LIGA™ lifecycle.
It converts a Governed Liability Object into a matter for which one or more explicit Liability foundations have been established.
It does not complete Liability governance.
The broader lifecycle continues through:
Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Scope & Allocation → Liability State & Change → Liability Transfer & Recourse → Liability Resolution & Discharge →
Liability Continuity & Finality
The architecture-wide principle remains:
Liability Determination ≠ Liability Lifecycle Completion.
LIGA™ governs Liability beyond formation and determination through its active lifecycle and into legitimate Finality.
Canonical Boundary
LBS begins with a:
Governed Liability Object
and the question:
On what governed basis can Liability potentially exist in relation to this Object?
LBS governs:
Basis Identification, Basis Origin, Basis Source, Basis Classification, Basis Qualification, Basis Applicability, Object–Basis Association, Multiple Bases, Alternative Bases, Concurrent Bases, Competing Bases, Dependent Bases, Basis Hierarchy, Basis Network, Basis Uncertainty, Basis Assumptions, Basis Exclusion, Basis Change, Basis Supersession, Basis Reassessment, Basis Continuity, and Basis Readiness.
LBS does not determine:
Liability Subjects, complete Liability Relationships, Liability Conditions, Condition Satisfaction, Liability-Relevant Connection, Liability Attachment, Liability Determination, Liability Scope, Liability Allocation, Liability State, Transfer, Recourse, Resolution, Discharge, or Finality.
LBS ends when one or more:
Governed Liability Bases
are sufficiently established for Liability Relationship governance.
Canonical Closing Statement
Liability cannot be methodologically established merely because something happened, Harm occurred, Loss was suffered, an obligation existed, responsibility was alleged, or a Claim was made.
Before Liability can be evaluated, the foundation under which Liability could potentially exist must itself be explicit, traceable, qualified, and connected to the governed matter.
LBS establishes that foundation without converting it into a Liability conclusion.
A basis makes Liability possible to evaluate. It does not make Liability exist.
Establish the Basis before determining the Liability.