LCXQM — Liability Connection Qualification Module
LCXQM — Liability Connection Qualification Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Connection Standard (LCNS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Connection Qualification
Module ID: LIGA-LCNS-LCXQM-001
Origin ID: OOF.CM.LIGA.06.04.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 22 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 Connection Qualification Module (LCXQM) governs how Governed Liability Connection Chains are evaluated and assigned explicit qualification states according to their relevance, structural coherence, Basis alignment, Subject association, Object association, Condition alignment, relational integrity, chain integrity, temporal coherence, uncertainty, contradiction, and methodological readiness for subsequent Liability Determination.
LCXQM determines whether a governed Connection is sufficiently qualified to proceed toward Liability Determination.
It does not determine whether Liability exists, attaches, or should be allocated.
It governs the transition:
Governed Liability Connection Chain Set → Qualification Criteria → Relevance Assessment → Structural & Contextual Assessment → Uncertainty & Conflict Assessment → Qualification State → Qualified Liability
Connection Set
Its foundational distinction is:
Qualified Liability Connection ≠ Established Liability.
Operational Role
The operational role of LCXQM is:
to determine whether each governed Liability Connection possesses sufficient methodological quality, relevance, coherence, and completeness to become an admissible Connection input for Liability Determination.
LCXCM asks:
How do the Relationships combine into a governed Connection Chain?
LCXQM asks:
Is that Connection sufficiently governed to proceed toward Liability Determination?
LCXQM does not ask:
Is the Subject liable?
That question belongs downstream to the Liability Determination Standard (LDS).
Position in the Parent Standard Flow
The internal LCNS progression is:
Liability Connection Identification → Liability Connection Relationship → Liability Connection Chain → Liability Connection Qualification → Liability Connection Evidence Association LCXQM governs:
Liability Connection Qualification
Its principal input is:
Governed Liability Connection Chain Set
Its principal output is:
Qualified Liability Connection Set
Its canonical handoff is:
Qualified Liability Connection Set → Liability Connection Evidence Association
Central Operational Question
Which governed Liability Connections are sufficiently relevant, coherent, bounded, traceable, and methodologically qualified to proceed toward Liability Determination, and what qualification state should each Connection receive?
Governed Space
LCXQM governs:
Connection Qualification Criteria, Qualification Scope, Qualification Basis, Connection Relevance, Basis Alignment, Subject Alignment, Object Alignment, Condition Alignment, Relationship Integrity, Chain Integrity, Endpoint Integrity, Direction Integrity, Sequence Integrity, Temporal Coherence, Boundary Coherence, Intermediate Element Sufficiency, Connection Completeness, Connection Strength Representation, Connection Uncertainty, Connection Conflict, Alternative Connections, Qualification Confidence, Qualification State, Partial Qualification, Pending Qualification, Non-Qualification, Qualification Change, Qualification Correction, Qualification Reassessment, and Qualification Readiness.
Qualification Object
The object being qualified is the governed Liability Connection.
LCXQM does not directly qualify:
the Subject, the Harm, the Claim, the Liability, or the final legal conclusion.
Therefore:
Connection Qualification ≠ Subject Qualification.
Qualification Basis
Every Qualification should identify the methodological basis under which the Connection is being assessed.
The Qualification Basis may include:
applicable Liability Basis, relevant Liability Conditions, governed Subjects, Governed Liability Object, Connection Relationships, Connection Chain, and applicable qualification criteria.
Basis-Specific Qualification
A Connection may qualify under one Liability Basis and fail to qualify under another.
Therefore:
Qualified under Basis A ≠ Qualified under Basis B.
Qualification must remain Basis-specific where materially necessary.
Condition-Specific Qualification
A Connection may satisfy the connective requirements associated with one Liability Condition while remaining insufficient for another.
Therefore:
Connection Qualification for Condition A ≠ Connection Qualification for Condition B.
Subject-Specific Qualification
The same Connection Network may contain different qualification states for different Subjects.
Therefore:
Connection Qualified for Subject A ≠ Connection Qualified for Subject B.
Object-Specific Qualification
Where several Liability Objects exist, Qualification should preserve the Object to which the Connection applies.
Therefore:
Connection Qualified for Object A ≠ Connection Qualified for Object B.
Relationship-Specific Qualification
A Connection may depend upon different upstream Liability Relationships.
Qualification should preserve which Relationship structure makes the Connection relevant.
Therefore:
Relationship Context A ≠ Relationship Context B.
Qualification Criteria
Qualification criteria should be explicit enough to make the resulting Qualification State:
traceable, reviewable, reproducible, and explainable.
Criteria must not be created after observing the preferred Liability outcome merely to support that outcome.
Qualification Criteria Integrity
Qualification criteria should be:
defined, applicable, consistent, bounded, and relevant to the Connection being evaluated.
Therefore:
Desired Outcome ≠ Qualification Criterion.
Connection Relevance
A Connection must be materially relevant to the Liability inquiry to qualify.
Relevance may derive from its relationship to:
Liability Basis, Subject, Object, Condition, conduct, event, state, or consequence.
Relevance and Existence
A Connection may exist factually without being materially relevant to the Liability inquiry.
Therefore:
Connection Existence ≠ Liability Relevance.
Relevance and Liability
A materially relevant Connection still does not establish Liability.
Therefore:
Liability Relevance ≠ Liability Determination.
Basis Alignment
Qualification should determine whether the Connection aligns with the applicable Governed Liability Basis.
A Connection irrelevant to the applicable Basis should not qualify merely because it is operationally significant.
Therefore:
Operational Significance ≠ Basis Alignment.
Subject Alignment
The Connection should be associated with the correct Liability Subject or Subjects.
A valid Connection concerning Subject A must not be transferred automatically to Subject B.
Therefore:
Connection to Subject A ≠ Connection to Subject B.
Object Alignment
The Connection should relate to the correct Governed Liability Object.
Therefore:
Connection to Related Matter ≠ Connection to Governed Liability Object by default.
Condition Alignment
The Connection should correspond to the Liability Conditions whose relevance it is intended to support.
Therefore:
Condition Satisfaction ≠ Connection Alignment.
A satisfied Condition may still lack the required Connection.
Endpoint Integrity
Qualification should verify that Connection endpoints are sufficiently identified and governably continuous.
Ambiguous endpoints may prevent full Qualification.
Therefore:
Ambiguous Endpoint ≠ Fully Qualified Endpoint.
Relationship Integrity
The Relationships forming the Connection should be sufficiently explicit and internally coherent.
A Chain built on undefined relational jumps should not receive full Qualification merely because its overall narrative appears plausible.
Chain Integrity
Qualification should evaluate whether the Connection Chain preserves:
material Relationships, intermediate elements, direction, sequence, boundaries, and uncertainty.
Therefore:
Narrative Plausibility ≠ Chain Integrity.
Direction Integrity
Where direction matters, the Chain should preserve a sufficiently governed directional structure.
Unknown direction may affect Qualification but should not be converted into false direction.
Therefore:
Unknown Direction ≠ Failed Connection by default.
Sequence Integrity
Where sequence materially affects the Connection, the relevant order should be sufficiently governed.
Therefore:
Correct Elements + Incorrect Sequence ≠ Qualified Chain by default.
Temporal Coherence
The timing of Chain elements should be compatible with the claimed Connection structure where time is materially relevant.
Temporal incoherence may prevent or reduce Qualification.
Temporal Proximity
Temporal proximity alone cannot satisfy Qualification.
Therefore:
Temporal Proximity ≠ Qualified Liability Connection.
Spatial Coherence
Spatial relationships may be relevant to Qualification where applicable.
Spatial proximity alone is insufficient.
Therefore:
Spatial Proximity ≠ Qualified Liability Connection.
Boundary Coherence
The Connection should possess an appropriate governance boundary.
An over-broad Connection may include irrelevant structures.
An under-bounded Connection may omit materially necessary structures.
Both may affect Qualification.
Intermediate Element Sufficiency
Materially necessary intermediate elements should be represented.
Therefore:
Missing Material Intermediate Element ≠ Complete Qualified Chain.
Intermediate Relationship Sufficiency
Materially necessary relationships between intermediate elements should also be explicit.
Therefore:
Visible Nodes + Missing Relationships ≠ Complete Connection.
Connection Completeness
Completeness concerns whether the governed Connection contains the materially necessary structure for the specific Qualification scope.
Completeness does not require every imaginable fact.
Therefore:
Connection Completeness ≠ Information Exhaustiveness.
Complete Connection and Liability
Even a complete Connection does not establish Liability.
Therefore:
Complete Liability Connection ≠ Liability Determination.
Connection Strength
LCXQM may represent the methodological strength of a Connection where useful.
Strength may reflect the quality and coherence of the governed Connection structure.
It must not be treated as a probability of Liability unless a separate governed methodology explicitly establishes such interpretation.
Strength and Qualification
A Connection may be sufficiently qualified even where its strength is not maximal.
Therefore:
Qualification ≠ Maximum Connection Strength.
Strength and Liability
Connection Strength must remain separate from Liability Strength or legal outcome.
Therefore:
Connection Strength ≠ Liability Strength.
Connection Sufficiency
Connection Sufficiency asks whether enough governed connective structure exists for the intended downstream use.
It does not require absolute certainty.
Therefore:
Connection Sufficiency ≠ Connection Certainty.
Qualification Confidence
LCXQM may preserve a governed confidence representation where methodology supports it.
Confidence should refer to the Qualification assessment, not directly to Liability.
Therefore:
Qualification Confidence ≠ Liability Probability.
Connection Uncertainty
Qualification should explicitly preserve uncertainty concerning:
Connection existence, endpoint identity, relationship type, direction, sequence, intermediate elements, timing, Basis relevance, Condition relevance, or other material characteristics.
Uncertainty and Qualification
Uncertainty does not automatically prevent Qualification.
The relevant question is whether the uncertainty remains within the permitted Qualification boundary for the intended downstream use.
Therefore:
Uncertainty ≠ Automatic Non-Qualification.
Material Uncertainty
Uncertainty is material where resolving it could change:
Connection identity, Connection structure, Connection relevance, Qualification State, or downstream Determination readiness.
Material uncertainty should remain visible.
Unknown Connection State
A Connection may receive an Unknown Qualification State where available governed information is insufficient to determine Qualification.
Therefore:
Unknown ≠ Not Qualified.
Disputed Connection State
A Connection may remain disputed where competing governed representations materially affect Qualification.
Therefore:
Disputed ≠ Not Qualified by default.
Connection Conflict
Conflicting Connection structures should be explicitly represented.
Qualification must not resolve conflict merely by selecting the most convenient Chain.
Therefore:
Conflict ≠ Authority to Select Preferred Connection.
Alternative Connections
Several alternative Connections may remain methodologically plausible.
Each should be qualified independently where materially relevant.
Therefore:
Multiple Plausible Connections ≠ One Established Connection.
Competing Connections
Competing Connections may receive different Qualification States.
LCXQM should preserve those states without collapsing them into one artificial conclusion.
Partial Qualification
A Connection may be sufficiently governed in some respects while materially incomplete in others.
Such a Connection may receive:
Partially Qualified
where the applicable methodology permits.
Partial Qualification must identify the unresolved elements.
Partial Qualification and Liability
A Partially Qualified Connection does not represent partial Liability.
Therefore:
Partial Connection Qualification ≠ Partial Liability.
Pending Qualification
A Connection may receive:
Pending
where Qualification depends upon unresolved governed inputs expected to become available.
Therefore:
Pending ≠ Qualified.
and:
Pending ≠ Not Qualified.
Qualified State
A Connection may receive:
Qualified
when it satisfies the applicable methodological Qualification criteria sufficiently for subsequent Connection Evidence Association and downstream Liability Determination.
Qualified does not mean Liability exists.
Not Qualified State
A Connection may receive:
Not Qualified
where it does not satisfy the applicable Qualification requirements.
The reason should be explicit.
Not Qualified and No Liability
A Connection failing Qualification does not necessarily establish the absence of all possible Liability.
It may mean only that:
this Connection, under this Basis, for this Subject, Object, Condition, or lifecycle state is not sufficiently qualified.
Therefore:
Not Qualified Connection ≠ No Liability under every possible Basis.
Qualification State Model
LCXQM may use the canonical Qualification States:
Qualified
Partially Qualified
Not Qualified
Pending
Unknown
Uncertain
Disputed
These states should remain methodologically distinct.
Qualified vs Partially Qualified
Qualified means the applicable criteria are sufficiently satisfied for the intended handoff.
Partially Qualified means material qualification requirements remain unresolved but sufficient structure exists to preserve a meaningful partial state.
Unknown vs Uncertain
Unknown means the relevant state cannot presently be established.
Uncertain means a state can be represented but material uncertainty remains.
Therefore:
Unknown ≠ Uncertain.
Uncertain vs Disputed
Uncertain concerns insufficiency or variability of knowledge.
Disputed concerns competing materially inconsistent representations or positions.
Therefore:
Uncertain ≠ Disputed.
Qualification Reason
Every Qualification State should preserve a reason sufficient to explain why that state was assigned.
A bare status without rationale is insufficient for high-integrity governance.
Qualification Rationale
Qualification Rationale may reference:
criteria applied, inputs considered, Chain characteristics, unresolved uncertainties, conflicts, exceptions, and limitations.
Qualification Traceability
A Qualification State should be traceable to:
the qualified Connection, applicable Basis, relevant Conditions, Subjects, Object, criteria, and governed input state.
Therefore:
Qualification without Traceability ≠ Governed Qualification.
Qualification Reproducibility
Where the same governed inputs and methodology are used, another qualified implementation should be capable of understanding how the Qualification State was produced.
Reproducibility does not require all authorities to reach identical jurisdiction-specific legal conclusions.
Qualification Explainability
Qualification should be explainable at the level necessary to distinguish:
what was evaluated, which criteria applied, what passed, what remained unresolved, and why the state resulted.
Evidence and Qualification
Evidence may support Qualification.
However, LCXQM does not own evidence governance.
ADIT® governs evidence.
LCXEAM subsequently governs Connection Evidence Association.
Therefore:
Evidence ≠ Qualification.
Evidence Volume
Large evidence volume does not automatically produce a Qualified Connection.
Therefore:
Evidence Volume ≠ Connection Qualification.
Missing Evidence
Missing evidence may affect Qualification where evidence is necessary to support a material Connection element.
But:
Missing Evidence ≠ No Connection by default.
The correct state may instead be:
Pending, Unknown, Uncertain, or Not Qualified, depending on the methodology.
Evidence Conflict
Conflicting evidence should not be silently resolved inside Qualification where the conflict belongs to evidence governance.
LCXQM should preserve its effect on Qualification.
Validation and Qualification
VALIDOS™ may provide validated inputs.
A validated input does not automatically qualify the Connection.
Therefore:
Validated Input ≠ Qualified Liability Connection.
Harm and Qualification
A governed Harm state may support a Connection Qualification where Harm is relevant to the applicable Basis.
However:
Established Harm ≠ Qualified Liability Connection.
Operational Causation and Qualification
A governed operational causal relationship may strongly support a Connection.
It does not automatically satisfy all Liability-specific Qualification criteria.
Therefore:
Established Operational Causation ≠ Qualified Liability Connection by default.
Responsibility and Qualification
A Responsibility state may be relevant.
However:
Established Responsibility ≠ Qualified Liability Connection by default.
Accountability and Qualification
Accountability may contribute to Connection relevance.
However:
Established Accountability ≠ Qualified Liability Connection by default.
Control and Qualification
Control may be materially relevant under some Liability Bases.
But:
Established Control ≠ Qualified Liability Connection by itself.
Ownership and Qualification
Ownership may support one part of a Connection.
But:
Ownership ≠ Qualified Liability Connection.
Relationship and Qualification
An established Liability Relationship may be necessary under some Bases.
It does not automatically qualify the Connection.
Therefore:
Established Liability Relationship ≠ Qualified Liability Connection.
Condition Satisfaction and Qualification
Satisfied Liability Conditions may be necessary for Qualification.
They remain distinct from Connection Qualification.
Therefore:
Satisfied Liability Conditions ≠ Qualified Liability Connection.
Harm Absence
Where a Liability Basis does not require Harm, absence of Harm should not automatically prevent Qualification.
Therefore:
No Harm ≠ No Liability Connection by default.
Fault Absence
Where a Liability Basis does not require Fault, absence of Fault should not automatically prevent Qualification.
Therefore:
No Fault ≠ No Qualified Liability Connection by default.
Directness and Qualification
A Direct Connection is not automatically more qualified than an Indirect Connection.
Therefore:
Direct Connection ≠ Qualified Connection by default.
Indirectness and Qualification
An Indirect Connection may qualify where its intermediate structure is sufficiently governed.
Therefore:
Indirect Connection ≠ Non-Qualified Connection by default.
Chain Length
Longer Chains are not automatically weaker.
Shorter Chains are not automatically stronger.
Therefore:
Chain Length ≠ Qualification State.
Multiple Connections
A matter may contain several independently Qualified Connections.
Therefore:
One Liability Matter ≠ One Qualified Connection.
Connection Network Qualification
A Connection Network may contain:
Qualified paths, Partially Qualified paths, Not Qualified paths, Pending paths, Unknown paths, and Disputed paths.
The Network should preserve these differences.
Network Qualification and Individual Paths
A qualified path does not automatically qualify the entire Network.
Likewise, one failed path does not automatically disqualify all other paths.
Therefore:
Path Qualification ≠ Network Qualification by default.
Multi-Subject Qualification
Different Subjects within the same Network may possess different Qualification States.
Therefore:
Shared Event ≠ Shared Connection Qualification.
Multi-Basis Qualification
The same Connection may be assessed separately under multiple Liability Bases.
Therefore:
One Connection ≠ One Universal Qualification State.
Qualification Change
A Qualification State may change when:
new information appears, a Chain changes, a Relationship changes, an upstream Condition changes, evidence changes, or applicable criteria change.
Changes should remain traceable.
Qualification Correction
An earlier Qualification may be found incorrect.
Correction should preserve:
the earlier state, the corrected state, reason, affected criteria, and provenance.
Therefore:
Qualification Correction ≠ Historical Erasure.
Qualification Reassessment
A previously Qualified or Not Qualified Connection may require reassessment.
Reassessment should preserve the historical state.
Therefore:
Qualification Reassessment ≠ Historical Rewrite.
Qualification Versioning
Materially changed Qualification may require a new version.
Therefore:
New Qualification Version ≠ New Connection by default.
Qualification Expiration
Where Qualification depends upon time-sensitive states, it may expire or cease to remain current.
Therefore:
Qualification Expiration ≠ Historical Non-Qualification.
Qualification Suspension
Qualification may be suspended where a material unresolved issue prevents continued reliance.
Therefore:
Qualification Suspension ≠ Qualification Erasure.
Qualification Re-Entry
Later Liability stages may reveal that Qualification must be reconsidered.
LCXQM should support targeted re-entry.
Therefore:
Qualification Re-Entry ≠ New Liability Origin by default.
Upstream Re-Entry
Qualification may reveal defects requiring return to:
LCXCM for Chain structure, LCXRM for Relationship structure, LCXIM for Connection identification, LCOS for Conditions, or another earlier LIGA™ governance space.
LCXQM must not compensate for upstream defects by manipulating Qualification criteria.
No Outcome-Based Qualification
Qualification must not be engineered backward from a desired Liability conclusion.
Therefore:
Desired Liability Outcome ≠ Qualification Basis.
No Actor-Based Presumption
A Subject should not receive a stronger Connection Qualification merely because it is:
larger, more visible, more powerful, more insured, more financially capable, or more operationally prominent.
Therefore:
Subject Prominence ≠ Connection Qualification.
No Harm-Severity Presumption
Greater Harm severity does not automatically produce stronger Connection Qualification.
Therefore:
Harm Severity ≠ Connection Qualification.
No Evidence-Volume Presumption
More evidence does not automatically mean stronger Qualification.
Therefore:
More Evidence ≠ More Qualified Connection by default.
No Simplicity Presumption
A simpler Chain is not automatically more qualified.
Therefore:
Simpler Connection ≠ Better Qualified Connection by default.
No Complexity Presumption
A complex Chain is not automatically less qualified.
Therefore:
Complex Connection ≠ Weak Connection by default.
No Majority Presumption
Where multiple sources support one Connection representation and fewer sources support another, source count alone does not determine Qualification.
Therefore:
Majority of Sources ≠ Qualified Connection by default.
Qualification Readiness
A Connection is ready for final Connection Evidence Association when its Qualification State and rationale are sufficiently explicit and the material structure required for evidence association is stable enough to proceed.
Qualified Liability Connection Set
The principal output of LCXQM is:
Qualified Liability Connection Set
This set preserves each governed Connection together with its Qualification State and materially relevant rationale.
The set may contain:
Qualified Connections, Partially Qualified Connections, Not Qualified Connections, Pending Connections, Unknown Connections, Uncertain Connections, and Disputed Connections.
Qualification Output Does Not Erase Failed Connections
Connections that do not qualify should remain historically traceable where materially relevant.
Therefore:
Not Qualified ≠ Delete Connection.
Failed, pending, uncertain, and disputed qualification states may be important to downstream reconstruction.
Handoff to Connection Evidence Association
LCXQM hands the:
Qualified Liability Connection Set
to:
LCXEAM — Liability Connection Evidence Association Module
The next governance question becomes:
What governed evidence supports, contradicts, limits, contextualizes, or leaves unresolved each qualified or otherwise materially relevant Liability Connection?
LCXQM does not perform that final evidence association itself.
Minimum Implementation Framework
A conforming implementation of LCXQM must provide exactly the following eight capabilities:
Qualification Criteria & Scope Governance
Capability to establish explicit, applicable, bounded, traceable, and Basis-specific Connection Qualification criteria and Qualification scope.
Basis, Subject, Object, Condition & Relationship Alignment
Capability to assess whether the Connection is correctly associated with the applicable Liability Basis, Subjects, Governed Liability Object, Liability Conditions, and relevant upstream Liability Relationships.
Structural, Chain & Temporal Integrity Assessment
Capability to assess endpoint integrity, Relationship integrity, Chain integrity, direction, sequence, boundaries, intermediate elements, temporal coherence, and Connection completeness.
Relevance, Sufficiency, Strength & Confidence Governance
Capability to distinguish Connection relevance, Connection sufficiency, methodological strength, Qualification confidence, completeness, and certainty without converting those measures into Liability conclusions.
Uncertainty, Conflict, Alternative & Partial Qualification Governance
Capability to preserve unknown, uncertain, disputed, competing, alternative, partial, pending, and unresolved Connection states without manufacturing certainty.
Qualification State & Rationale Governance
Capability to assign and explain the canonical Qualification States — Qualified, Partially Qualified, Not Qualified, Pending, Unknown, Uncertain, and Disputed — with sufficient rationale and traceability.
Qualification Change, Correction, Versioning & Re-Entry
Capability to preserve Qualification changes, corrections, reassessments, expiration, suspension, versioning, and lifecycle re-entry without historical erasure.
Qualification Readiness & Handoff
Capability to determine whether the qualified Connection structure is sufficiently stable for Connection Evidence Association and subsequent Liability Determination without prematurely determining Liability.
Governance Logic
The canonical LCXQM governance logic is:
Governed Liability Connection Chain Set
↓
Select Connection / Chain / Path
↓
Define Qualification Scope
↓
Identify Applicable Qualification Criteria
↓
Associate Liability Basis
↓
Associate Subject / Object / Condition / Relationship
↓
Assess Connection Relevance
↓
Assess Endpoint Integrity
↓
Assess Relationship Integrity
↓
Assess Chain Integrity
↓
Assess Direction & Sequence
↓
Assess Temporal Coherence
↓
Assess Boundary Coherence
↓
Assess Intermediate Element Sufficiency
↓
Assess Connection Completeness
↓
Assess Connection Sufficiency
↓ Represent Strength / Confidence where applicable ↓
Identify Unknown / Uncertain / Disputed Elements
↓
Evaluate Alternative / Competing Connections
↓
Assign Qualification State
↓
Record Qualification Rationale
↓
Preserve Change / Correction / Reassessment History
↓
Qualified Liability Connection Set
↓
Handoff to Liability Connection Evidence Association
Governance Outputs
LCXQM may produce:
Connection Qualification Criteria Set
Connection Qualification Scope
Basis Alignment State
Subject Alignment State
Object Alignment State
Condition Alignment State
Relationship Alignment State
Connection Relevance State
Endpoint Integrity State
Relationship Integrity State
Chain Integrity Assessment
Direction Integrity State
Sequence Integrity State
Temporal Coherence State
Boundary Coherence State
Intermediate Element Sufficiency State
Connection Completeness State
Connection Sufficiency State
Connection Strength Representation
Qualification Confidence State
Connection Uncertainty State
Connection Conflict State
Alternative Connection Qualification Set
Qualified Connection
Partially Qualified Connection
Not Qualified Connection
Pending Connection
Unknown Connection
Uncertain Connection
Disputed Connection
Qualification Rationale
Qualification Trace Record
Qualification Correction Record
Qualification Reassessment Record
Qualification Version Record
Qualification Readiness State
The principal output is:
Qualified Liability Connection Set
Critical Distinctions
LCXQM preserves the following distinctions:
Qualified Liability Connection ≠ Established Liability Connection Qualification ≠ Subject Qualification Qualified under Basis A ≠ Qualified under Basis B Connection Qualification for Condition A ≠ Connection Qualification for Condition B Connection Qualified for Subject A ≠ Connection Qualified for Subject B Connection Qualified for Object A ≠ Connection Qualified for Object B Desired Outcome ≠ Qualification Criterion Connection Existence ≠ Liability Relevance Liability Relevance ≠ Liability Determination Operational Significance ≠ Basis Alignment Connection to Subject A ≠ Connection to Subject B Condition Satisfaction ≠ Connection Alignment Ambiguous Endpoint ≠ Fully Qualified Endpoint Narrative Plausibility ≠ Chain Integrity Unknown Direction ≠ Failed Connection by default Correct Elements + Incorrect Sequence ≠ Qualified Chain by default Temporal Proximity ≠ Qualified Liability Connection Spatial Proximity ≠ Qualified Liability Connection Missing Material Intermediate Element ≠ Complete Qualified Chain Visible Nodes + Missing Relationships ≠ Complete Connection Connection Completeness ≠ Information Exhaustiveness Complete Liability Connection ≠ Liability Determination Qualification ≠ Maximum Connection Strength Connection Strength ≠ Liability Strength Connection Sufficiency ≠ Connection Certainty Qualification Confidence ≠ Liability Probability Uncertainty ≠ Automatic Non-Qualification Unknown ≠ Not Qualified Disputed ≠ Not Qualified by default Conflict ≠ Authority to Select Preferred Connection Multiple Plausible Connections ≠ One Established Connection Partial Connection Qualification ≠ Partial Liability Pending ≠ Qualified Pending ≠ Not Qualified Not Qualified Connection ≠ No Liability under every possible Basis Unknown ≠ Uncertain Uncertain ≠ Disputed Qualification without Traceability ≠ Governed Qualification Evidence ≠ Qualification Evidence Volume ≠ Connection Qualification Missing Evidence ≠ No Connection by default Validated Input ≠ Qualified Liability Connection Established Harm ≠ Qualified Liability Connection Established Operational Causation ≠ Qualified Liability Connection by default Established Responsibility ≠ Qualified Liability Connection by default Established Accountability ≠ Qualified Liability Connection by default Established Control ≠ Qualified Liability Connection by itself Ownership ≠ Qualified Liability Connection Established Liability Relationship ≠ Qualified Liability Connection Satisfied Liability Conditions ≠ Qualified Liability Connection No Harm ≠ No Liability Connection by default No Fault ≠ No Qualified Liability Connection by default Direct Connection ≠ Qualified Connection by default Indirect Connection ≠ Non-Qualified Connection by default Chain Length ≠ Qualification State One Liability Matter ≠ One Qualified Connection Path Qualification ≠ Network Qualification by default Shared Event ≠ Shared Connection Qualification One Connection ≠ One Universal Qualification State Qualification Correction ≠ Historical Erasure Qualification Reassessment ≠ Historical Rewrite New Qualification Version ≠ New Connection by default Qualification Expiration ≠ Historical Non-Qualification Qualification Suspension ≠ Qualification Erasure Qualification Re-Entry ≠ New Liability Origin by default Desired Liability Outcome ≠ Qualification Basis Subject Prominence ≠ Connection Qualification Harm Severity ≠ Connection Qualification More Evidence ≠ More Qualified Connection by default Simpler Connection ≠ Better Qualified Connection by default Complex Connection ≠ Weak Connection by default Majority of Sources ≠ Qualified Connection by default Not Qualified ≠ Delete Connection
Cross-Architecture Boundary
LCXQM may rely on governed inputs originating from other OOF® architectures.
ORA™ may establish Operational Reality and operational causal structures.
HAGA™ may establish Harm states and Harm lifecycle structures.
AGA™ may establish Responsibility, Accountability, Authority, and Attribution states.
GOA™ may establish Authority, Scope, and Delegation structures.
ADIT® may govern evidence and auditability.
VALIDOS™ may govern validation states.
OBIDENITY® may govern Identity, Ownership, Authority, Permission, Provenance, Transfer, and Continuity.
AIG® and ASGA™ may govern AI and autonomous-system behavior, execution, authority, permission, override, and operational states.
LCXQM does not re-determine those external governance objects.
It evaluates whether their relevant relationships within the LIGA™ Connection structure are sufficiently qualified for Liability governance.
The canonical interoperability principle is:
External governance may establish the validity of an input within its own domain; LCXQM determines only whether the resulting Liability-specific Connection is sufficiently qualified for downstream Liability governance.
Canonical Boundary
LCXQM begins with a:
Governed Liability Connection Chain Set
and asks:
Which governed Liability Connections are sufficiently qualified to proceed toward Liability Determination?
LCXQM governs:
Qualification Criteria, Qualification Scope, Basis Alignment, Subject Alignment, Object Alignment, Condition Alignment, Relationship Alignment, Connection Relevance, Endpoint Integrity, Relationship Integrity, Chain Integrity, Direction Integrity, Sequence Integrity, Temporal Coherence, Boundary Coherence, Intermediate Element Sufficiency, Connection Completeness, Connection Sufficiency, Connection Strength Representation, Qualification Confidence, Uncertainty, Conflict, Alternative Connections, Partial Qualification, Pending Qualification, Unknown Qualification, Disputed Qualification, Qualification Rationale, Qualification Change, Correction, Reassessment, Versioning, Expiration, Suspension, Re-Entry, and Qualification Readiness.
LCXQM does not determine:
Evidence governance itself, final Connection Evidence Association, Operational Causation itself, Harm itself, Responsibility itself, Accountability itself, Fault, Claim validity, Liability Attachment, Liability Determination, Liability Scope, Liability Allocation, Liability State, Liability Transfer, Recourse, Resolution, Discharge, or Finality.
LCXQM ends when a:
Qualified Liability Connection Set
is sufficiently governed for Connection Evidence Association.
Use Case 1 — Autonomous System Connection Qualification
An autonomous industrial system performs an action followed by equipment damage.
LCXCM has established a governed Connection Chain:
Operator → Autonomous System → Execution Decision → Machine Action → Operational Event → Equipment
State
LCXQM evaluates whether that Chain is sufficiently qualified under the applicable Liability Basis.
It assesses:
whether the correct Subject is represented, whether the relevant Object is identified, whether applicable Conditions align, whether intermediate elements are sufficiently governed, whether direction and sequence are coherent, and whether material uncertainty remains.
The Chain may become Qualified, Partially Qualified, Pending, or another appropriate Qualification State.
None of those states determines Liability.
Use Case 2 — Multi-Party Connection Network Qualification
A technical incident involves an owner, operator, maintenance provider, and component producer.
LCXCM has produced several Connection paths within a common Network.
LCXQM evaluates each path independently.
The maintenance-provider path may be Qualified.
The operator path may remain Partially Qualified because one intermediate Relationship is uncertain.
The producer path may remain Pending because a material technical state has not yet been established.
The shared incident does not require identical Qualification States for all Subjects.
LCXQM preserves those differences so that downstream Liability governance receives differentiated, methodologically governed Connection inputs.
Canonical Closing Statement
A Connection should not proceed toward Liability Determination merely because it appears plausible, because Harm occurred, because a Subject had control, or because a coherent narrative can be constructed.
The Connection must first satisfy explicit methodological Qualification requirements appropriate to its Basis, Subjects, Object, Conditions, Relationships, Chain structure, and uncertainty.
Qualification determines whether the Connection is ready to be relied upon as a governed input.
It does not determine what Liability follows from that Connection.
A Qualified Connection is ready for Liability evaluation. It is not a Liability conclusion.
Qualify the Connection before determining the Liability.