LCXIM — Liability Connection Identification Module
LCXIM — Liability Connection Identification 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 Identification
Module ID: LIGA-LCNS-LCXIM-001
Origin ID: OOF.CM.LIGA.06.01.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 Identification Module (LCXIM) governs how potential Liability-Relevant Connections among Liability Subjects, Governed Liability Objects, Governed Liability Conditions, conduct, actions, omissions, events, states, consequences, and other materially relevant inputs are recognized, identified, distinguished, referenced, associated, and preserved for subsequent Liability Connection governance.
LCXIM determines which potential Connections require explicit governance.
It does not determine whether those Connections are sufficiently related, complete, qualified, evidenced, or sufficient for Liability Determination.
It governs the transition:
Governed Liability Condition Structure → Potential Connection Recognition → Connection Candidate Identification → Connection Identity → Endpoint & Relevance Association → Identified Liability Connection Set Its foundational distinction is:
Connection Identification ≠ Connection Qualification.
Operational Role
The operational role of LCXIM is:
to identify the potential Connections that must be explicitly governed before the Liability inquiry can determine their relational structure, chains, qualification, evidentiary support, or downstream significance.
LCXIM asks:
Which potential Connections are materially relevant to the Liability inquiry and therefore require explicit governance?
It does not ask whether those Connections ultimately support Liability.
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 LCXIM governs:
Liability Connection Identification
Its principal input is:
Governed Liability Condition Structure
Its principal output is:
Identified Liability Connection Set
Its canonical handoff is:
Identified Liability Connection Set → Liability Connection Relationship Governance
Central Operational Question
Which potential Connections among the relevant Liability Subjects, Objects, Conditions, conduct, events, states, consequences, and other governed inputs are materially relevant to the Liability inquiry and therefore require explicit governance?
Governed Space
LCXIM governs:
Potential Connection Recognition, Connection Candidate Identification, Connection Identity, Connection Endpoint Identification, Connection Source Reference, Connection Target Reference, Preliminary Connection Direction, Connection Relevance Association, Subject Connection Association, Object Connection Association, Condition Connection Association, Basis Connection Association, Relationship Connection Association, Conduct Connection Association, Event Connection Association, State Connection Association, Consequence Connection Association, Potential Direct Connection, Potential Indirect Connection, Potential Multi-Element Connection, Multiple Connection Candidates, Duplicate Connection Candidates, Overlapping Connection Candidates, Unknown Connection Candidates, Uncertain Connection Candidates, Disputed Connection Candidates, and Connection Identification Sufficiency.
Connection Candidate
A Connection Candidate is a potentially Liability-relevant relationship between governed elements that has been identified as requiring further Connection governance.
A Connection Candidate is not yet a Qualified Liability Connection.
Therefore:
Connection Candidate ≠ Qualified Liability Connection.
Identification Threshold
A potential Connection should enter LCNS governance when there is a sufficient methodological reason to examine whether the relationship between its elements is relevant to the Liability inquiry.
The threshold is not:
proof of Liability, proof of causation, or proof of Connection sufficiency.
The threshold is:
sufficient relevance to require explicit Connection governance.
Connection Recognition
Connection Recognition occurs when the governance process detects that two or more elements may possess a materially relevant relationship.
Recognition precedes formal identification.
Therefore:
Connection Recognition ≠ Connection Identification.
Connection Identification
Connection Identification occurs when a recognized potential Connection is explicitly represented as a governed Connection Candidate.
Identification should establish enough structure to determine:
what elements may be connected, why the potential Connection matters, and where subsequent Connection governance should continue.
Identification Before Qualification
LCXIM deliberately separates Identification from Qualification.
The sequence is:
Potential Relationship → Connection Candidate → Connection Structure → Connection Chain → Connection
Qualification
not:
Potential Relationship → Liability Conclusion Therefore:
Identification ≠ Qualification ≠ Liability Determination.
Connection Identity
Each materially distinct Connection Candidate should receive a stable governed identity where necessary for traceability.
Connection Identity enables later modules to:
structure, chain, qualify, evidence, correct, reassess, or reject the same Connection Candidate without losing its lineage.
Connection Identity and Endpoints
Connection Identity should remain distinct from the identities of its endpoints.
Therefore:
Identity of Subject A + Identity of Object B ≠ Identity of Connection A→B.
The Connection is a distinct governed object.
Connection Identity and Liability
A Connection Identity does not establish Liability.
Therefore:
Connection Identity ≠ Liability Identity.
Connection Endpoint Identification
LCXIM should identify the elements that potentially form the endpoints of a Connection.
An endpoint may include:
Liability Subject, Liability Object, Liability Condition, conduct, action, omission, event, state, consequence, or another materially relevant governed element.
Source Endpoint
Where direction is potentially relevant, LCXIM may identify a preliminary Source Endpoint.
The Source Endpoint represents the element from which the potential directed Connection is considered to originate.
This does not yet establish final Connection direction.
Target Endpoint
LCXIM may identify a preliminary Target Endpoint.
The Target Endpoint represents the element toward which the potential Connection is considered to operate.
Therefore:
Preliminary Source/Target Assignment ≠ Final Connection Direction.
Preliminary Direction
Where sufficient information exists, LCXIM may preserve preliminary direction.
Examples:
Subject → Action Action → Event Event → Object State Condition → Subject Direction is refined in subsequent Connection governance.
Direction Unknown
A Connection Candidate may be relevant even where direction is not yet known.
Therefore:
Unknown Direction ≠ No Connection Candidate.
Unknown direction should remain explicit.
Subject Connection Candidate
A Liability Subject may be potentially connected to:
another Subject, Object, Condition, action, omission, event, state, consequence, or other governed element.
LCXIM identifies that potential Connection without determining its downstream meaning.
Subject–Object Connection Candidate
A Subject may possess a potential Connection to a Governed Liability Object through:
control, operation, ownership, design, maintenance, production, deployment, authority, use, custody, or another relevant mechanism.
Therefore:
Subject–Object Association ≠ Liability.
Subject–Condition Connection Candidate
A Subject may be potentially connected to a Liability Condition because the Condition concerns:
that Subject, its conduct, its authority, its state, its obligation, its capability, or its Relationship.
Therefore:
Subject–Condition Association ≠ Condition Satisfaction.
Subject–Conduct Connection Candidate
LCXIM may identify a potential relationship between a Subject and relevant conduct.
It should not assume that the Subject performed, authorized, controlled, or caused the conduct merely because the Subject appears within the same matter.
Therefore:
Subject Presence ≠ Subject–Conduct Connection.
Object Connection Candidate
A Governed Liability Object may be potentially connected to:
Subjects, Conditions, events, actions, states, Harm, loss, or other governed elements.
LCXIM identifies which such potential Connections require further governance.
Condition Connection Candidate
A Governed Liability Condition may possess potential Connections to:
Subjects, Relationships, Objects, conduct, events, states, or consequences.
The Condition's governed State remains an upstream LCOS output.
Therefore:
Condition Connection ≠ Condition State.
Basis Association
Every Connection Candidate should remain associated with the Liability Basis or Bases under which its potential relevance is being considered where that association is known.
Therefore:
Connection under Basis A ≠ Connection under Basis B by default.
Relationship Association
A Connection Candidate may arise within or through an established Liability Relationship.
The relevant Relationship should be referenced.
However:
Liability Relationship ≠ Connection Candidate by default.
Conduct Connection Candidate
Conduct may become a Connection Candidate where it potentially links:
Subject, Object, Condition, event, state, or consequence.
Conduct alone does not establish the Connection.
Action Connection Candidate
An action may form one endpoint or potential intermediate element of a Connection.
LCXIM identifies the candidate relationship.
It does not determine operational causation or Liability.
Omission Connection Candidate
A potential omission may become relevant where an applicable governed Condition or Relationship makes non-action material.
LCXIM must not infer omission from outcome alone.
Therefore:
Adverse Outcome ≠ Omission.
Event Connection Candidate
An event may potentially connect:
conduct to consequence, Subject to Object, Condition to state, or multiple other governed elements.
Therefore:
Event Coexistence ≠ Established Connection.
State Connection Candidate
A governed state may become a Connection Candidate where it potentially relates materially to another element in the Liability inquiry.
Examples may include:
Authority state, Condition state, Operational Reality state, Harm state, Identity state, system state, or control state.
Consequence Connection Candidate
A consequence may form part of a potential Connection structure.
LCXIM should identify relevant candidate Connections without assuming that the consequence establishes:
causation, fault, responsibility, or Liability.
Therefore:
Consequence ≠ Connection Proof.
Harm Connection Candidate
Where Harm is relevant to the applicable Liability Basis, a governed Harm state may form an endpoint or element of a Connection Candidate.
HAGA™ retains governance ownership of Harm.
LCXIM governs only identification of the potential Liability-specific Connection.
Therefore:
Harm ≠ Liability Connection.
Operational Reality Connection Candidate
ORA™ may establish actions, events, states, sequences, or mechanisms that become potential Connection inputs.
LCXIM may identify their potential Liability relevance.
Therefore:
Operational Relationship ≠ Liability-Relevant Connection by default.
Accountability Connection Candidate
AGA™ may establish Responsibility, Accountability, Authority, or Attribution states.
Those states may become elements in a Connection Candidate.
However:
Accountability State ≠ Liability Connection.
Identity Connection Candidate
OBIDENITY® may establish Identity, Ownership, Authority, Permission, Provenance, Transfer, or Continuity states.
LCXIM may identify potential Liability Connections involving those states.
Therefore:
Identity Relationship ≠ Liability Connection by default.
AI and Autonomous-System Connection Candidate
AIG® or ASGA™ may establish behavior, authority, permission, execution, override, or autonomous-system states.
Those states may become Connection Candidates where materially relevant to Liability.
Therefore:
AI or Autonomous-System Participation ≠ Liability Connection by itself.
Potential Direct Connection
A Connection Candidate may appear direct where no materially necessary intermediate element is currently identified.
Canonical preliminary form:
A → B Directness remains subject to subsequent Connection governance.
Potential Indirect Connection
A Connection Candidate may appear to involve one or more intermediate elements.
Canonical preliminary form:
A → ? → B or:
A → X → B LCXIM preserves the candidate without requiring the complete chain to be known.
Therefore:
Incomplete Intermediate Structure ≠ No Connection Candidate.
Unknown Intermediate Element
A potentially relevant Connection may be identifiable even where an intermediate element is unknown.
The unknown element should remain explicit rather than being silently omitted.
Multi-Element Connection Candidate
Some Connection Candidates may involve more than two relevant elements from the beginning.
Example:
Subject → Conduct → Event → Object State LCXIM may preserve this as a preliminary multi-element structure for subsequent governance.
Connection Candidate Network
Where many potential Connections exist, LCXIM may represent an initial Connection Candidate Network.
This network is preliminary.
It does not establish the final Liability Connection Network.
Therefore:
Connection Candidate Network ≠ Governed Liability Connection Network.
Multiple Subjects
One matter may contain multiple Subjects potentially connected to the same:
Object, Condition, event, or consequence.
Each materially distinct potential Connection should remain separately identifiable.
Therefore:
One Matter ≠ One Subject Connection.
Multiple Objects
A Subject may be potentially connected to multiple Liability Objects.
Therefore:
One Subject ≠ One Object Connection.
Object-specific Connection Candidates should remain distinct where materially relevant.
Multiple Conditions
The same Subject or Object may possess different potential Connections to different Conditions.
Therefore:
One Subject–Object Relationship ≠ One Universal Condition Connection.
Multiple Bases
A single factual matter may support several potential Liability Bases.
Different Bases may require different Connections.
Therefore:
One Fact Pattern ≠ One Universal Liability Connection.
Parallel Connection Candidates
Several Connection Candidates may exist independently.
LCXIM should preserve them separately unless later governance establishes that they represent the same Connection.
Overlapping Connection Candidates
Connection Candidates may share:
Subjects, Objects, Conditions, events, states, or consequences.
Overlap does not establish identity.
Therefore:
Connection Overlap ≠ Connection Identity.
Duplicate Connection Candidates
Multiple records may appear to represent the same potential Connection.
LCXIM should identify potential duplication without prematurely merging materially distinct Connections.
Therefore:
Similar Connection Records ≠ Same Connection by default.
Candidate Consolidation
Where governance establishes that multiple records represent the same Connection Candidate, they may be consolidated under one Connection Identity.
The provenance of the original records should remain traceable.
Candidate Distinction
Where apparently similar Connection Candidates differ materially in:
Subject, Object, Condition, Basis, Relationship, direction, time, or relevant event, they should remain distinct.
Therefore:
Connection Similarity ≠ Connection Equivalence.
Connection Relevance Association
LCXIM should record why a Connection Candidate may be relevant to the Liability inquiry.
Potential relevance may derive from:
Liability Basis, Condition, Subject role, Relationship, Object association, conduct, event, state, or consequence.
This is preliminary relevance.
It is not Connection Qualification.
Preliminary Relevance
A Connection Candidate may be retained where there is sufficient reason to investigate its Liability relevance.
Therefore:
Preliminary Relevance ≠ Qualified Connection Relevance.
Qualification belongs later in LCNS.
Weak Preliminary Relevance
A Connection Candidate should not necessarily be discarded merely because its initial relevance appears weak.
Where the Connection is plausibly material and insufficient information exists, it may remain explicitly uncertain.
Irrelevant Relationship
A relationship that has no material relevance to the Liability inquiry should not become a Connection Candidate merely because it exists.
Therefore:
Existing Relationship ≠ Liability Connection Candidate.
Temporal Association
LCXIM should preserve known temporal information associated with a Connection Candidate.
This may include:
start time, end time, event time, Condition-relevant time, or unknown temporal state.
Detailed temporal Connection governance occurs later.
Historical Connection Candidate
A Connection may be relevant to an earlier lifecycle moment even where it no longer exists.
Therefore:
Current Absence ≠ Historical Connection Absence.
Historical Connection Candidates should remain identifiable where materially relevant.
Unknown Connection Candidate
A potential Connection may remain:
Unknown
where there is reason to examine it but insufficient information to identify its structure reliably.
Therefore:
Unknown Connection Candidate ≠ Rejected Connection Candidate.
Uncertain Connection Candidate
A Connection Candidate may be identified with uncertainty concerning:
endpoints, direction, relevance, time, or identity.
Uncertainty should remain explicit.
Therefore:
Connection Uncertainty ≠ Authority to Invent Structure.
Disputed Connection Candidate
Different governed sources may disagree about whether a potential Connection exists.
LCXIM should preserve the dispute.
Therefore:
Disputed Connection Candidate ≠ Established Connection.
Conflicting Candidate Representations
Different records may describe the same potential Connection differently.
LCXIM should preserve the conflict until subsequent governance can resolve it.
Therefore:
Conflicting Representation ≠ Authority to Select Preferred Connection.
Connection Candidate Assumption
An assumed Connection may be recorded as an assumption where methodologically necessary.
It must remain clearly distinguished from an identified supported Connection Candidate.
Therefore:
Assumed Connection ≠ Established Connection Candidate.
Connection Candidate Inference
A potential Connection may be identified through inference.
Where inference is used, LCXIM should preserve:
the source inputs, inference logic, and uncertainty.
Therefore:
Inferred Connection Candidate ≠ Directly Observed Connection.
No Outcome Shortcut
LCXIM must not identify a specific Connection merely because an adverse outcome occurred.
Therefore:
Adverse Outcome ≠ Identified Liability Connection.
No Harm Shortcut
The existence of Harm does not identify which Subject, Object, action, omission, or Relationship possesses the relevant Liability Connection.
Therefore:
Harm ≠ Identified Liability Connection.
No Proximity Shortcut
Temporal, spatial, organizational, technical, or relational proximity may justify examination.
It does not establish the Connection.
Therefore:
Proximity ≠ Identified Liability Connection.
No Relationship Shortcut
A Liability Relationship may create a reason to examine a Connection.
It does not become the Connection automatically.
Therefore:
Liability Relationship ≠ Liability Connection.
No Condition Shortcut
A satisfied Liability Condition may make a Connection inquiry necessary.
It does not identify the required Connection automatically.
Therefore:
Satisfied Condition ≠ Identified Liability Connection.
No Control Shortcut
Control may justify identifying a potential Connection Candidate.
It does not establish the final Connection.
Therefore:
Control ≠ Established Liability Connection.
No Responsibility Shortcut
Responsibility may justify examination of a Connection.
It does not establish Liability Connection by itself.
Therefore:
Responsibility ≠ Established Liability Connection.
No Causation Shortcut
Operational causation may reveal a potential Connection Candidate.
However:
Operational Causation ≠ Liability-Relevant Connection.
LCXIM identifies the candidate for further governance.
No Evidence Shortcut
Evidence may reveal or support a potential Connection.
Evidence does not become the Connection.
Therefore:
Evidence ≠ Connection.
No Claim Shortcut
A Claim may allege that a Connection exists.
LCXIM may identify the alleged Connection as a Candidate where relevant.
However:
Claimed Connection ≠ Governed Connection.
Identification Change
New information may:
add, remove, split, merge, or alter Connection Candidates.
Changes should remain traceable where materially relevant.
Identification Correction
A Connection Candidate may later be found to have been:
misidentified, duplicated, incorrectly associated, or assigned incorrect endpoints.
Correction should preserve the earlier record.
Therefore:
Connection Identification Correction ≠ Historical Erasure.
Identification Reassessment
Later information may require reconsideration of whether a Connection Candidate should remain within LCNS governance.
Therefore:
Identification Reassessment ≠ Liability Reassessment by itself.
Lifecycle Re-Entry
Later LCNS or LIGA™ stages may reveal that a relevant Connection was never identified.
LCXIM should support re-entry.
Therefore:
Connection Identification Re-Entry ≠ New Liability Origin by default.
Identification Sufficiency
Connection Identification is sufficient when the governance process can determine:
which Connection Candidates require further governance, which materially relevant elements form their known or potential endpoints, which Basis, Subjects, Objects, Conditions, and Relationships are associated, what preliminary direction is known, what relevance supports inclusion, and what uncertainty remains.
Identification Sufficiency and Completeness
LCXIM does not require the complete Connection Chain to be known.
It requires sufficient identification for the next module to govern the relationship structure.
Therefore:
Identification Sufficiency ≠ Connection Completeness.
Handoff to Liability Connection Relationship Governance
Once materially relevant Connection Candidates have been sufficiently identified, LCXIM produces:
Identified Liability Connection Set
The handoff should preserve, where applicable:
Connection Candidate Identity, Source Endpoint, Target Endpoint, preliminary direction, Basis association, Subject association, Relationship association, Object association, Condition association, conduct association, event association, state association, consequence association, temporal reference, preliminary relevance, uncertainty, dispute, assumption, inference, and provenance.
The next governance question becomes:
What is the governed relationship between the identified elements of each Liability Connection Candidate?
That question belongs to:
LCXRM — Liability Connection Relationship Module.
Minimum Implementation Framework
A conforming implementation of LCXIM must provide at least the following eight capabilities:
Potential Connection Recognition
Capability to detect materially relevant potential relationships among Liability Subjects, Objects, Conditions, conduct, events, states, consequences, and other governed inputs without converting those relationships directly into Liability Connections.
Connection Candidate Identification & Identity
Capability to establish explicit Connection Candidates and persistent identities sufficient for subsequent Connection governance.
Endpoint & Preliminary Direction Identification
Capability to identify known or potential Connection endpoints and preserve preliminary direction or explicitly unknown direction.
Basis, Subject, Relationship, Object & Condition Association
Capability to associate each Connection Candidate with the materially relevant Liability Basis, Subjects, Relationships, Objects, and Conditions without collapsing those structures into the Connection itself.
Multi-Element, Multiple, Overlapping & Duplicate Candidate Governance
Capability to preserve multi-element, parallel, overlapping, potentially duplicate, and networked Connection Candidates while preventing inappropriate consolidation.
Preliminary Relevance, Uncertainty, Dispute & Inference Governance
Capability to preserve why a Connection Candidate requires governance while explicitly representing uncertainty, disputes, assumptions, and inferred candidate structures.
Identification Change, Correction & Re-Entry
Capability to govern additions, removals, splits, consolidations, corrections, reassessments, and lifecycle re-entry without historical erasure.
Identification Sufficiency & Handoff
Capability to determine whether the Identified Liability Connection Set contains sufficient structure for Liability Connection Relationship governance without requiring premature Connection qualification or Liability Determination.
Governance Logic
The canonical LCXIM governance logic is:
Governed Liability Condition Structure
↓
Identify Materially Relevant Elements
↓
Recognize Potential Relationships
↓
Form Connection Candidates
↓
Assign Connection Candidate Identity
↓
Identify Known / Potential Endpoints
↓
Preserve Preliminary Direction
↓
Associate Liability Basis
↓
Associate Subjects / Relationships / Objects / Conditions
↓
Associate Conduct / Events / States / Consequences
↓
Identify Potential Direct / Indirect / Multi-Element Structure
↓
Identify Multiple / Overlapping / Duplicate Candidates
↓
Preserve Preliminary Relevance
↓
Preserve Unknown / Uncertain / Disputed / Inferred Candidates
↓
Assess Identification Sufficiency
↓
Identified Liability Connection Set
↓
Handoff to Liability Connection Relationship Governance
Governance Outputs
LCXIM may produce:
Connection Candidate
Connection Candidate Identity
Connection Endpoint Reference
Preliminary Source Endpoint
Preliminary Target Endpoint
Preliminary Connection Direction
Subject Connection Candidate
Object Connection Candidate
Condition Connection Candidate
Basis-Associated Connection Candidate
Relationship-Associated Connection Candidate
Conduct Connection Candidate
Action Connection Candidate
Omission Connection Candidate
Event Connection Candidate
State Connection Candidate
Consequence Connection Candidate
Harm-Related Connection Candidate
Potential Direct Connection
Potential Indirect Connection
Potential Multi-Element Connection
Connection Candidate Network
Parallel Connection Candidate Set
Overlapping Connection Candidate Set
Potential Duplicate Connection Record
Unknown Connection Candidate
Uncertain Connection Candidate
Disputed Connection Candidate
Assumed Connection Candidate
Inferred Connection Candidate
Connection Identification Correction Record
Connection Identification Reassessment Record
Connection Identification Sufficiency State
The principal output is:
Identified Liability Connection Set
Critical Distinctions
LCXIM preserves the following distinctions:
Connection Identification ≠ Connection Qualification Connection Candidate ≠ Qualified Liability Connection Connection Recognition ≠ Connection Identification Identification ≠ Qualification ≠ Liability Determination Identity of Endpoints ≠ Identity of Connection Connection Identity ≠ Liability Identity Preliminary Source/Target Assignment ≠ Final Connection Direction Unknown Direction ≠ No Connection Candidate Subject–Object Association ≠ Liability Subject–Condition Association ≠ Condition Satisfaction Subject Presence ≠ Subject–Conduct Connection Condition Connection ≠ Condition State Connection under Basis A ≠ Connection under Basis B by default Liability Relationship ≠ Connection Candidate by default Adverse Outcome ≠ Omission Event Coexistence ≠ Established Connection Consequence ≠ Connection Proof Harm ≠ Liability Connection Operational Relationship ≠ Liability-Relevant Connection by default Accountability State ≠ Liability Connection Identity Relationship ≠ Liability Connection by default AI or Autonomous-System Participation ≠ Liability Connection by itself Incomplete Intermediate Structure ≠ No Connection Candidate Connection Candidate Network ≠ Governed Liability Connection Network One Matter ≠ One Subject Connection One Subject ≠ One Object Connection One Subject–Object Relationship ≠ One Universal Condition Connection One Fact Pattern ≠ One Universal Liability Connection Connection Overlap ≠ Connection Identity Similar Connection Records ≠ Same Connection by default Connection Similarity ≠ Connection Equivalence Preliminary Relevance ≠ Qualified Connection Relevance Existing Relationship ≠ Liability Connection Candidate Current Absence ≠ Historical Connection Absence Unknown Connection Candidate ≠ Rejected Connection Candidate Connection Uncertainty ≠ Authority to Invent Structure Disputed Connection Candidate ≠ Established Connection Conflicting Representation ≠ Authority to Select Preferred Connection Assumed Connection ≠ Established Connection Candidate Inferred Connection Candidate ≠ Directly Observed Connection Adverse Outcome ≠ Identified Liability Connection Harm ≠ Identified Liability Connection Proximity ≠ Identified Liability Connection Liability Relationship ≠ Liability Connection Satisfied Condition ≠ Identified Liability Connection Control ≠ Established Liability Connection Responsibility ≠ Established Liability Connection Operational Causation ≠ Liability-Relevant Connection Evidence ≠ Connection Claimed Connection ≠ Governed Connection Connection Identification Correction ≠ Historical Erasure Identification Reassessment ≠ Liability Reassessment by itself Connection Identification Re-Entry ≠ New Liability Origin by default Identification Sufficiency ≠ Connection Completeness
Cross-Architecture Boundary
LCXIM may recognize potential Connection Candidates from governed states produced elsewhere in the OOF® architecture ecosystem.
ORA™ may provide operational actions, events, states, sequences, and mechanisms.
HAGA™ may provide governed Harm states.
AGA™ may provide Responsibility, Accountability, Authority, and Attribution states.
GOA™ may provide Authority, Scope, and Delegation structures.
ADIT® may provide evidence that reveals a potential Connection Candidate.
VALIDOS™ may provide validated states.
OBIDENITY® may provide Identity, Ownership, Authority, Permission, Provenance, Transfer, and Continuity states.
AIG® and ASGA™ may provide AI and autonomous-system states.
LCXIM does not assume governance ownership of those states.
It determines only whether a potential relationship involving them requires explicit Liability Connection governance.
The canonical interoperability principle is:
An externally governed state may reveal a potential Liability Connection without becoming the Liability Connection itself and without transferring governance ownership of its original domain to LIGA™.
Canonical Boundary
LCXIM begins with a:
Governed Liability Condition Structure
and asks:
Which potential Connections are materially relevant to the Liability inquiry and therefore require explicit governance?
LCXIM governs:
Potential Connection Recognition, Connection Candidate Identification, Connection Identity, Endpoint Identification, Preliminary Direction, Basis Association, Subject Association, Relationship Association, Object Association, Condition Association, Conduct Association, Event Association, State Association, Consequence Association, Potential Direct and Indirect Connections, Multi-Element Candidates, Multiple Candidates, Overlapping Candidates, Potential Duplicates, Preliminary Relevance, Unknown Candidates, Uncertain Candidates, Disputed Candidates, Assumptions, Inferences, Identification Change, Correction, Reassessment, Re-Entry, and Identification Sufficiency.
LCXIM does not determine:
the final relationship structure of the Connection, the complete Connection Chain, Connection Qualification, Connection Evidence Sufficiency, Operational Causation, Liability Attachment, Liability Determination, Liability Scope, Liability Allocation, Liability State, Liability Transfer, Recourse, Resolution, Discharge, or Finality.
LCXIM ends when an:
Identified Liability Connection Set
is sufficiently established for Liability Connection Relationship governance.
Use Case 1 — Autonomous Equipment Incident
An autonomous industrial machine performs an action shortly before an operational incident.
The governed matter contains:
the autonomous system, a human operator, a facility operator, the equipment Object, applicable Liability Conditions, an operational event, and a resulting consequence.
LCXIM does not assume that every element is Liability-connected merely because all appear in the same incident.
It identifies the materially relevant potential Connections that require further governance, such as:
autonomous system → action, operator → system, facility operator → Object, action → operational event, and event → consequence.
These remain Connection Candidates.
Their exact relationship structure, chain, qualification, and evidentiary sufficiency are governed later.
Use Case 2 — Multi-Party Maintenance Matter
A technical failure occurs after work involving an equipment owner, operator, maintenance provider, and component producer.
LCXIM identifies potentially relevant Connection Candidates among:
the Subjects, the Governed Liability Object, the maintenance Condition, maintenance conduct, equipment state, technical event, and resulting consequence.
The module preserves separate candidates where different Subjects may possess different Connections to the same matter.
It does not determine which party is liable.
It produces the Identified Liability Connection Set required for subsequent Connection Relationship governance.
Canonical Closing Statement
A Liability inquiry cannot govern its connective structure reliably until it first identifies which potential Connections actually require examination.
The existence of Subjects, Objects, Conditions, conduct, events, Harm, consequences, evidence, or operational causation does not automatically establish the Liability Connection among them.
LCXIM makes those potential Connections explicit without prematurely qualifying them or converting them into Liability.
Identification determines which Connections must be governed. It does not determine what those Connections ultimately establish.
Identify the Connection before defining its relationship.