Liability Connection Standard (LCNS)
Liability Connection Standard (LCNS)
Architecture: LIGA™ — Liability Governance Architecture
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Parent Standard
Governed Space: Liability-Relevant Connection
Standard ID: LIGA-LCNS-001
Origin ID: OOF.PS.LIGA.06.00.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 Standard (LCNS) governs how Liability-relevant connections among Liability Subjects, Governed Liability Objects, Governed Liability Conditions, conduct, events, states, actions, omissions, relationships, consequences, and other materially relevant inputs are identified, structured, traced, qualified, and represented before Liability Determination.
LCNS establishes whether a sufficiently governed connection exists between the relevant elements of a potential Liability structure and preserves the nature, direction, chain, strength, uncertainty, and qualification of that connection.
LCNS does not determine Liability.
It governs the methodological connection structure required before Liability can proceed to Determination.
Liability-Relevant Connection ≠ Liability Determination.
Operational Role
The operational role of LCNS is:
to establish the governed connective structure through which Liability-relevant Subjects, Objects, Conditions, conduct, events, states, actions, omissions, and consequences can be related without converting those relationships directly into Liability.
LCOS establishes:
what Conditions govern the potential Liability structure and what their governed states are.
LCNS establishes:
how the relevant governed elements are connected for purposes of Liability evaluation.
LDS subsequently determines:
whether Liability can legitimately attach and be determined to exist.
Core Question
What sufficiently governed connection exists between the relevant Liability Subject, Liability Object, conditions, conduct, and other Liability-relevant inputs?
Position in the LIGA™ Governance Flow
The canonical LIGA™ Governance Flow is:
Liability Context → Liability Object → Liability Basis → Liability Relationships → Liability Conditions → Liability Connection → Liability Determination → Liability Scope & Allocation → Liability State & Change → Liability Transfer & Recourse → Liability Resolution & Discharge → Liability Continuity & Finality LCNS governs:
Liability Connection
Its principal upstream input is:
Governed Liability Condition Structure
Its principal downstream handoff is:
Governed Liability Connection Structure → Liability Determination
Canonical Transition
LCNS governs the transition:
Governed Liability Condition Structure → Connection Identification → Connection Relationship → Connection Chain → Connection Qualification → Evidence Association → Governed Liability Connection Structure The transition must preserve the distinction between:
connection, proof, causation, responsibility, accountability, and Liability.
Governed Space
LCNS governs:
Liability Connection Identification, Connection Identity, Connection Objects, Connection Subjects, Connection Relationships, Connection Direction, Connection Origin, Connection Endpoint, Connection Chain, Direct Connection, Indirect Connection, Intermediate Connection, Multi-Step Connection, Parallel Connection, Converging Connection, Diverging Connection, Connection Dependency, Connection Sequence, Connection Timing, Connection Continuity, Connection Qualification, Connection Relevance, Connection Sufficiency, Connection Strength where methodologically applicable, Connection Uncertainty, Connection Conflict, Connection Evidence Association, Connection Change, Connection Correction, Connection Reassessment, and Connection Readiness for Liability Determination.
Liability-Relevant Connection
A Liability-Relevant Connection is a governed relationship between two or more materially relevant elements whose relationship must be established before Liability Determination can legitimately evaluate whether Liability attaches.
The connected elements may include:
Liability Subjects, Liability Objects, Liability Conditions, actions, omissions, conduct, events, operational states, decisions, authority states, Harm states, consequences, or other governed inputs.
The existence of the Connection does not establish Liability.
Connection as a Distinct Governance Object
LCNS treats the Connection itself as a governed object.
It must be possible to determine:
what is connected, how it is connected, through what intermediate elements, in which direction, during which period, under which Liability Basis, and with what unresolved uncertainty.
Therefore:
Connected Elements ≠ Governed Connection by default.
Connection Identity
A materially distinct Liability-Relevant Connection should possess a stable governed identity.
Connection Identity allows:
multiple Connections to coexist, Connections to change, Connection chains to be reconstructed, and later Liability Determination to reference the precise Connection evaluated.
Therefore:
Connection Identity ≠ Liability Identity.
Connection Endpoints
Every Connection should identify its materially relevant endpoints.
An endpoint may be:
a Liability Subject, a Liability Object, a Condition, an action, an omission, an event, a state, a consequence, or another governed element.
Endpoints must remain explicit enough to prevent ambiguous connection claims.
Connection Origin and Endpoint
A Connection may possess:
an originating element, one or more intermediate elements, and a terminal element.
The architecture should preserve direction where direction matters.
Therefore:
Connection A → B ≠ Connection B → A by default.
Subject–Object Connection
A Liability Subject may possess a Liability-relevant Connection to a Governed Liability Object.
The Connection may arise through:
control, operation, ownership, authority, maintenance, design, production, deployment, decision, conduct, or another relevant structure.
The existence of such a Connection does not establish Liability.
Therefore:
Subject–Object Connection ≠ Liability.
Subject–Condition Connection
A Liability Subject may be connected to a Liability Condition because the Condition:
applies to the Subject, depends upon the Subject's state, concerns the Subject's action, or concerns the Subject's omission.
Therefore:
Subject–Condition Connection ≠ Condition Satisfaction.
The Condition State remains governed by LCOS.
Relationship–Condition Connection
A Condition may arise or operate through a particular Liability Relationship.
LCNS may govern the connection between:
Relationship, Condition, Subject, and Object.
However:
Liability Relationship ≠ Liability-Relevant Connection by default.
The Relationship may be one element within the Connection structure.
Conduct Connection
Conduct may form part of a Liability-Relevant Connection.
Conduct may include:
action, non-action, decision, instruction, operation, control, communication, intervention, or another materially relevant behavior.
Therefore:
Conduct ≠ Liability.
Action Connection
An action may connect a Subject to an Object, event, Condition, consequence, or other governed state.
LCNS identifies and structures that Connection.
It does not determine whether the action was wrongful, sufficient for Liability, or legally determinative.
Omission Connection
An omission may become Liability-relevant where an applicable governed structure makes non-action materially relevant.
LCNS must not infer an omission merely because an adverse outcome occurred.
Therefore:
No Action Observed ≠ Governed Omission by default.
Event Connection
An event may connect several Liability-relevant elements.
An event can be:
an input, intermediate state, transition, or consequence within a Connection chain.
Therefore:
Event ≠ Liability-Relevant Connection by itself.
The relevant relationships around the event must be governed.
State Connection
A governed state may become an element within a Liability Connection.
Examples may include:
Authority state, Operational Reality state, Condition state, Harm state, Identity state, system state, or another governed state.
Therefore:
Relevant State ≠ Liability-Relevant Connection by itself.
Consequence Connection
A consequence may form an endpoint or intermediate element within a Liability Connection.
However:
Consequence ≠ Liability.
and:
Consequence ≠ Liability-Relevant Connection by itself.
The connection between the consequence and other governed elements must be established.
Direct Connection
A Direct Connection exists where the relevant governed elements are connected without a materially necessary intermediate element for the specific Liability inquiry.
Canonical representation:
A → B Directness describes Connection structure.
It does not establish Liability strength or Liability itself.
Indirect Connection
An Indirect Connection exists where one or more materially relevant intermediate elements connect the endpoints.
Canonical representation:
A → X → B or:
A → X → Y → B Therefore:
Indirect Connection ≠ No Connection.
The chain must instead be explicitly governed.
Intermediate Element
An Intermediate Element is a materially relevant state, action, event, Subject, Object, Condition, mechanism, or other element situated within a Connection chain.
Intermediate elements should remain explicit where omission would materially distort the Connection.
Connection Chain
A Connection Chain represents a sequence of Liability-relevant connections linking governed elements.
Canonical representation:
Subject → Conduct → Operational Event → Condition-Relevant State → Consequence or another appropriate governed structure.
The chain should not be compressed where intermediate elements materially affect Liability evaluation.
Connection Chain and Liability
Even a complete Connection Chain does not establish Liability.
Therefore:
Complete Connection Chain ≠ Liability Determination.
The chain becomes an input to LDS.
Multi-Step Connection
A Liability-relevant matter may contain many sequential Connection steps.
Each materially distinct step should remain identifiable.
Therefore:
Multi-Step Connection ≠ Single Connection by default.
Parallel Connections
Several independent Connections may exist simultaneously.
Example:
Subject A → Object Subject B → Object Subject C → Condition These Connections should not be collapsed merely because they concern the same Liability matter.
Converging Connections
Multiple Connections may converge on one element.
Canonical representation:
A → X B → X C → X Convergence does not establish equal Liability relevance for all originating elements.
Diverging Connections
One element may connect to multiple downstream elements.
Canonical representation:
A → X A → Y A → Z Each branch may possess different relevance, evidence, uncertainty, and downstream significance.
Connection Network
A complex Liability matter may form a network rather than a linear chain.
A Connection Network may contain:
multiple Subjects, multiple Objects, multiple Conditions, multiple events, multiple actions, multiple consequences, and multiple intermediate states.
Therefore:
Liability Connection Network ≠ Single Liability Connection.
Relationship Network and Connection Network
The Liability Relationship Network established under LRS and the Connection Network established under LCNS are distinct.
Relationships describe the relevant relational structure.
Connections describe how materially relevant elements connect for Liability evaluation.
Therefore:
Liability Relationship Network ≠ Liability Connection Network.
Connection Direction
Direction should be preserved where it affects meaning.
A Connection may represent:
influence, control, action, transfer, dependency, sequence, contribution, or another directed relation.
Therefore:
Directionless Representation ≠ Sufficient Connection Representation where direction is material.
Connection Sequence
Where order matters, the Connection Chain should preserve sequence.
Therefore:
A → B → C ≠ A → C → B.
The same elements in a different order may represent a materially different Liability structure.
Temporal Connection
A Connection may depend upon timing.
LCNS should preserve:
when the originating state existed, when the intermediate event occurred, when the endpoint state occurred, and any materially relevant delay.
Therefore:
Temporal Proximity ≠ Liability-Relevant Connection by itself.
Temporal Separation
A long temporal separation does not automatically eliminate a Connection.
Likewise, close temporal proximity does not automatically establish one.
Therefore:
Temporal Distance ≠ Connection Absence by default.
Spatial Connection
Location may be relevant to a Connection where the applicable Liability structure requires it.
Spatial proximity alone does not establish a Liability-Relevant Connection.
Therefore:
Spatial Proximity ≠ Liability-Relevant Connection by default.
Dependency Connection
One state may depend upon another.
Where dependency is materially relevant to Liability evaluation, LCNS may represent it as a Connection.
Therefore:
Dependency ≠ Liability by itself.
Control Connection
Control may create a materially relevant Connection between a Subject and an Object, system, activity, or another Subject.
However:
Control Connection ≠ Liability Determination.
Control must remain distinguished from Liability.
Authority Connection
Authority may connect a Subject to:
a decision, activity, Object, system, or another Subject.
GOA™ may govern the underlying Authority.
LCNS governs only its Liability-relevant connective role.
Therefore:
Authority Connection ≠ Liability.
Responsibility Connection
AGA™ may establish Responsibility states.
LCNS may determine how a governed Responsibility state connects a Subject to a Liability-relevant matter.
Therefore:
Responsibility Connection ≠ Liability.
Accountability Connection
An Accountability state may form part of the Connection structure.
However:
Accountability ≠ Liability.
and:
Accountability Attribution ≠ Liability Connection Determination by default.
Identity Connection
Identity may be necessary to establish that a Subject, Object, action, state, or record belongs to the same governed entity across the Connection Chain.
OBIDENITY® may govern the Identity state.
Therefore:
Identity Continuity ≠ Liability-Relevant Connection by itself.
Harm Connection
A governed Harm state may become part of the Liability Connection structure where Harm is relevant to the applicable Liability Basis.
HAGA™ governs Harm.
LCNS governs only the Liability-specific Connection involving that Harm state.
Therefore:
Harm ≠ Liability.
and:
Harm Connection ≠ Liability Determination.
Harm-Producing Mechanism
A Harm-producing mechanism may become an intermediate element in a Liability Connection Chain.
The mechanism itself belongs to the architecture governing that operational mechanism.
LCNS governs its Liability-specific connective relevance.
Therefore:
Harm-Producing Mechanism ≠ Liability Connection Governance Ownership.
Physical Contact
Physical contact may be an operational mechanism relevant to a Connection.
It is not automatically:
Harm, Liability, or a Liability-Relevant Connection sufficient for Determination.
Therefore:
Physical Contact ≠ Harm ≠ Liability.
Operational Causation
Operational causation concerns how an event or state produced another event or state within Operational Reality.
ORA™ or another relevant operational architecture may govern that mechanism.
LCNS does not redefine operational causation.
Operational Causation and Liability Connection
Operational causation may become an input to Liability Connection governance.
However:
Operational Causation ≠ Liability-Relevant Connection.
The Liability-specific relevance of the causal structure must still be governed.
Factual Connection
A factual relationship may exist between two elements.
LCNS determines whether that relationship is materially relevant to the Liability inquiry.
Therefore:
Factual Connection ≠ Liability-Relevant Connection by default.
Liability-Relevant Connection
A Connection becomes Liability-relevant where its relationship to the applicable:
Liability Basis, Liability Subjects, Liability Object,
and Governed Liability Condition Structure
is sufficiently established to require consideration during Liability Determination.
This is the central qualification threshold of LCNS.
Connection Relevance
Connection Relevance asks:
Does this Connection materially affect whether Liability can later be determined under the applicable governed structure?
Relevance is not Liability.
Therefore:
Connection Relevance ≠ Liability Determination.
Connection Qualification
Connection Qualification determines whether an identified Connection possesses sufficient methodological characteristics to enter Liability Determination.
Qualification may consider:
identity, endpoints, direction, chain integrity, temporal relevance, Basis relevance, Condition relevance, Subject relevance, Object relevance, supporting inputs, uncertainty, and unresolved conflict.
Qualified Connection
A Qualified Liability Connection is sufficiently structured and supported to enter Liability Determination.
Therefore:
Qualified Liability Connection ≠ Established Liability.
Qualification concerns readiness for Determination.
Connection Strength
Where methodologically useful, LCNS may represent the relative strength of support for a Connection.
Strength must derive from explicit methodology.
It must not be used as an ungoverned intuitive score.
Therefore:
Connection Strength ≠ Liability Strength.
Connection Sufficiency
Connection Sufficiency asks whether the Connection structure contains enough governed information for Liability Determination to evaluate it reliably.
Sufficiency does not require certainty.
Therefore:
Connection Sufficiency ≠ Connection Certainty.
Connection Uncertainty
Uncertainty may concern:
Connection existence, identity, direction, intermediate elements, timing, scope, relevance, or supporting inputs.
LCNS should preserve uncertainty explicitly.
Therefore:
Connection Uncertainty ≠ No Connection.
Unknown Connection
Where the available governed information cannot determine whether a materially relevant Connection exists, the Connection may remain:
Unknown
rather than being forced into existence or absence.
Therefore:
Unknown Connection ≠ Absent Connection.
Disputed Connection
A Connection may be disputed where materially relevant sources support competing Connection representations.
LCNS should preserve:
the competing structures, supporting inputs, and unresolved points.
Therefore:
Disputed Connection ≠ Established Connection by default.
Connection Conflict
Different governed inputs may support incompatible Connection Chains.
Conflict should remain explicit until governed resolution is possible.
Therefore:
Connection Conflict ≠ Authority to Select the Preferred Chain.
Alternative Connection Chains
Several plausible Connection Chains may exist.
LCNS should preserve materially credible alternatives where the evidence does not support collapsing them into one.
Therefore:
Multiple Plausible Chains ≠ One Established Chain.
Competing Connections
Different Liability Bases may depend upon different Connection structures.
Therefore:
Connection under Basis A ≠ Connection under Basis B by default.
The architecture must preserve Basis-specific relevance.
Subject-Specific Connection
Different Subjects may possess different Connections to the same Object, Condition, event, or consequence.
Therefore:
Connection of Subject A ≠ Connection of Subject B.
This distinction is essential before later Liability allocation.
Relationship-Specific Connection
The same Subject may possess different Connections through different Liability Relationships.
Therefore:
Connection through Relationship A ≠ Connection through Relationship B by default.
Object-Specific Connection
Connections should remain specific to the relevant Liability Object where multiple Objects exist.
Therefore:
Connection to Object A ≠ Connection to Object B by default.
Condition-Specific Connection
A Subject may be connected differently to different Conditions.
Therefore:
Connection to Condition A ≠ Connection to Condition B by default.
Satisfied Conditions should not be collapsed into one general Subject connection.
Connection and Condition Satisfaction
A satisfied Condition may exist without a sufficient Liability-Relevant Connection.
Therefore:
Condition Satisfaction ≠ Connection Satisfaction.
Likewise:
Connection ≠ Condition Satisfaction.
Connection and Basis
The Liability Basis establishes why Liability may potentially exist.
LCNS establishes the relevant connective structure under that Basis.
Therefore:
Liability Basis ≠ Liability-Relevant Connection.
Connection and Relationship
A Liability Relationship may make a Connection possible or relevant.
It does not establish the Connection automatically.
Therefore:
Liability Relationship ≠ Liability-Relevant Connection.
Connection and Liability Object
The Liability Object defines the governed matter.
The Connection defines how Subjects and other relevant elements relate to that matter for Liability evaluation.
Therefore:
Liability Object ≠ Liability Connection.
Connection and Harm
The existence of Harm does not establish who or what is Liability-connected to it.
Therefore:
Established Harm ≠ Established Liability-Relevant Connection.
Connection and Loss
Loss may exist without establishing the relevant Liability Connection.
Therefore:
Loss ≠ Liability-Relevant Connection.
Connection and Damage
Damage may form part of the governed matter but does not itself establish the Liability Connection.
Therefore:
Damage ≠ Liability-Relevant Connection.
Connection and Fault
Fault may be relevant under some Liability Bases.
It does not substitute for Connection governance.
Therefore:
Fault ≠ Liability-Relevant Connection by default.
Connection and Breach
A Breach may be relevant to the Connection structure.
However:
Breach ≠ Liability-Relevant Connection by itself.
The relationship between the Breach and other governed elements must still be established.
Connection and Responsibility
Responsibility may be relevant to a Connection.
However:
Responsibility ≠ Liability-Relevant Connection by itself.
Connection and Claim
A Claim may assert a Connection.
The assertion does not establish it.
Therefore:
Claimed Connection ≠ Governed Liability-Relevant Connection.
Connection and Payment
Payment may occur for reasons unrelated to Liability Determination.
Therefore:
Payment ≠ Liability-Relevant Connection by itself.
Connection and Admission
An admission may become a governed input where relevant.
However:
Admission ≠ Complete Liability Connection Structure by itself.
Evidence Association
LCNS may associate evidence with:
Connection existence, Connection endpoints, Connection direction, Connection chain, intermediate elements, timing, and qualification.
ADIT® governs evidence.
LCNS governs its association with the Liability Connection.
Evidence and Connection
Evidence supporting a Connection does not become the Connection itself.
Therefore:
Evidence ≠ Liability-Relevant Connection.
Evidence Quantity
More evidence does not automatically produce a stronger or sufficient Connection.
Therefore:
Evidence Volume ≠ Connection Sufficiency.
Relevance, quality, coherence, and relation to the Connection structure matter.
Missing Evidence
Missing evidence may create uncertainty.
It does not automatically establish absence of Connection.
Therefore:
Missing Evidence ≠ No Connection by default.
Conflicting Evidence
Conflicting evidence should remain visible in the Connection structure.
LCNS must not hide conflict by producing unsupported certainty.
Therefore:
Conflicting Evidence ≠ Authority to Manufacture Connection Certainty.
Validated Inputs
VALIDOS™ may validate inputs relevant to Connection governance.
A validated input may strengthen the basis for evaluating a Connection.
However:
Validated Input ≠ Qualified Liability Connection by itself.
Connection Provenance
A Connection representation should preserve provenance sufficient to determine:
where its elements originated, which sources support them, which transformations occurred, and how the current representation was formed.
Provenance supports Connection reconstructability.
Connection Change
A Connection may change because:
underlying reality changes, Relationships change, Conditions change, new evidence appears, earlier information is corrected, or a Connection Chain is reassessed.
Therefore:
Connection Change ≠ New Liability by default.
Connection Correction
A previously represented Connection may be incorrect.
Correction should preserve:
the earlier Connection representation, the corrected representation, reason, supporting inputs, and relevant time.
Therefore:
Connection Correction ≠ Historical Erasure.
Connection Reassessment
New information may require reassessment of:
Connection existence, direction, chain, relevance, or qualification.
Therefore:
Connection Reassessment ≠ Historical Rewrite.
Connection Versioning
Materially changed Connection structures may require versioning.
The system should distinguish:
Connection Identity, from:
Connection Version.
Therefore:
New Connection Version ≠ New Connection by default.
Historical Connection
Later Liability governance may need to reconstruct the Connection structure that existed or was known at an earlier time.
Therefore:
Current Connection ≠ Historical Connection by default.
Later Knowledge
A Connection may be discovered at T2 that was relevant at T1.
The architecture should distinguish:
Connection reality at T1, knowledge at T1, and discovery at T2.
Therefore:
Later Connection Knowledge ≠ Earlier Connection Knowledge.
Lifecycle Re-Entry
Later Liability stages may reveal:
a missing Connection, incorrect Connection Chain, incorrect qualification, missing intermediate element, or incorrect evidence association.
LCNS should support targeted lifecycle re-entry.
Therefore:
Connection Re-Entry ≠ New Liability Origin by default.
Upstream Re-Entry
Connection governance may reveal that an upstream structure is insufficient.
Examples:
incorrect Condition → LCOS, incorrect Relationship → LRS, incorrect Basis → LBS, incorrect Liability Object → LOS.
LCNS should return to the earliest materially affected governance space rather than manufacturing a Connection from defective upstream inputs.
No Causation Shortcut
LCNS rejects:
Causation → Liability Operational causation may be relevant, but Liability requires the complete governed structure.
Therefore:
Operational Causation ≠ Liability Determination.
No Harm Shortcut
LCNS rejects:
Harm → Assume Connection → Liability The relevant Connection must be established independently.
Therefore:
Harm ≠ Liability Connection ≠ Liability.
No Outcome Shortcut
An adverse outcome does not establish the Connection that produced or legally relates to it.
Therefore:
Adverse Outcome ≠ Liability-Relevant Connection.
No Proximity Shortcut
Temporal, spatial, organizational, technical, or relational proximity does not by itself establish a Liability-Relevant Connection.
Therefore:
Proximity ≠ Liability-Relevant Connection.
No Control Shortcut
Control may be relevant but does not itself establish the complete Connection required for Liability Determination.
Therefore:
Control ≠ Liability-Relevant Connection by itself.
No Relationship Shortcut
The existence of a Liability Relationship does not establish a sufficient Liability Connection.
Therefore:
Relationship ≠ Connection.
No Condition Shortcut
Even a fully satisfied Condition Set does not establish the required Connection.
Therefore:
Satisfied Conditions ≠ Liability-Relevant Connection.
No Evidence Shortcut
Strong evidence of one element does not establish the entire Connection Chain.
Therefore:
Evidence of Element A ≠ Evidence of Complete Connection Chain.
No Single-Actor Assumption
LCNS must not assume that one event, Harm, Object, or Condition connects to only one Subject.
A matter may contain:
multiple contributing Subjects, multiple independent Connections, or a Connection Network.
Therefore:
One Consequence ≠ One Liability-Relevant Subject Connection.
No Equal-Connection Assumption
Where multiple Subjects are connected to the same matter, their Connections may differ in:
type, direction, chain, timing, relevance, support, and uncertainty.
Therefore:
Shared Outcome ≠ Equal Connection.
Connection Network Integrity
In complex matters, LCNS should preserve the topology of the Connection Network sufficiently to avoid collapsing distinct chains.
This includes preserving:
nodes, edges, directions, intermediate elements, dependencies, and materially relevant temporal states.
Connection Chain Integrity
A Connection Chain possesses integrity when its materially relevant steps are:
identifiable, traceable, ordered where necessary, supported, and not silently replaced by assumptions.
Therefore:
Connection Chain Integrity ≠ Liability Determination.
Broken Connection Chain
A Connection Chain may contain a material gap.
A gap should remain explicit.
Therefore:
Broken Connection Chain ≠ Complete Liability-Relevant Connection.
The system should not bridge the gap through unsupported inference.
Partial Connection
Available governance may establish only part of a Connection.
The appropriate representation may be:
Partial Connection
rather than:
complete Connection, or no Connection.
Therefore:
Partial Connection ≠ Complete Connection.
Inferred Connection
A Connection may be inferred where the methodology permits inference from governed inputs.
The inference should preserve:
supporting inputs, inference logic, uncertainty, and qualification.
Therefore:
Inferred Connection ≠ Directly Established Connection.
Assumed Connection
An assumption should never be represented as an established Connection without qualification.
Therefore:
Assumed Connection ≠ Governed Connection.
Assumptions must remain explicit.
Connection Qualification State
LCNS may represent Connection qualification through states such as:
Qualified
Not Qualified
Partially Qualified
Pending
Unknown
Uncertain
Disputed
or another explicitly governed state.
These states concern Connection readiness.
They do not determine Liability.
Qualified ≠ Liable
The most important boundary of LCNS is:
Qualified Liability Connection ≠ Liability.
A Connection may be sufficiently governed and qualified while Liability still fails at Determination.
Not Qualified ≠ No Liability Under Every Basis
A Connection may fail qualification under one Basis while another Basis depends upon a different Connection structure.
Therefore:
Not Qualified under Basis A ≠ No Liability under Basis B.
Connection Readiness
Connection governance is ready for downstream Determination when materially relevant Connections are sufficiently:
identified, structured, chained, qualified, supported, temporally governed, and represented with unresolved uncertainty preserved.
Connection Readiness and Certainty
Readiness does not require absolute certainty.
It requires sufficient methodological structure for LDS to evaluate Liability Attachment and Determination.
Therefore:
Connection Readiness ≠ Connection Certainty.
Principal Output
The principal output of LCNS is:
Governed Liability Connection Structure
It may contain:
Connection identities, endpoints, directions, Connection Chains, Connection Networks, intermediate elements, Basis associations, Subject associations, Object associations, Condition associations, temporal structure, qualification states, supporting evidence associations, uncertainty, conflicts, alternative chains, and historical Connection states.
Governed Liability Connection Structure
The Governed Liability Connection Structure represents the Liability-specific connective structure necessary for Liability Determination.
It does not itself establish:
Liability Attachment, Liability existence, Liability Scope, Liability Allocation, or Liability State.
Therefore:
Governed Liability Connection Structure ≠ Liability Determination.
Handoff to Liability Determination
LCNS hands the Governed Liability Connection Structure to:
Liability Determination Standard (LDS)
LDS then asks:
Can Liability legitimately attach and be determined to exist on the established governed basis?
LCNS must not answer that question.
Governance Requirements
A conforming implementation of LCNS should:
identify materially relevant Connections explicitly;
assign stable Connection identities where necessary;
identify Connection endpoints;
preserve Connection direction where material;
preserve intermediate elements;
distinguish direct from indirect Connections;
represent Connection Chains and Networks;
preserve Basis-specific Connections;
preserve Subject-specific Connections;
preserve Object-specific Connections;
preserve Condition-specific Connections;
preserve temporal sequence and timing;
distinguish operational causation from Liability relevance;
distinguish factual Connection from Liability-Relevant Connection;
qualify Connection relevance explicitly;
associate supporting evidence without merging evidence and Connection;
preserve uncertainty, disputes, conflicts, and alternative chains;
preserve Connection changes and corrections;
support historical reconstruction and re-entry;
prohibit automatic conversion of Connection into Liability.
Governance Logic
The canonical LCNS governance logic is:
Governed Liability Condition Structure
↓
Identify Liability-Relevant Elements
↓
Identify Potential Connections
↓
Establish Connection Identity
↓
Establish Connection Endpoints
↓
Establish Direction
↓
Identify Intermediate Elements
↓
Construct Connection Chains
↓ Construct Connection Network where required ↓
Associate Liability Basis
↓
Associate Subjects
↓
Associate Liability Objects
↓
Associate Liability Conditions
↓
Preserve Temporal Structure
↓
Distinguish Operational Causation / Factual Connection / Liability-Relevant Connection
↓
Associate Evidence
↓
Evaluate Connection Relevance
↓
Evaluate Connection Qualification
↓
Preserve Partial / Unknown / Uncertain / Disputed Connections
↓
Preserve Alternative and Competing Chains
↓
Assess Connection Sufficiency
↓
Governed Liability Connection Structure
↓
Handoff to Liability Determination
Governance Outputs
LCNS may produce:
Liability Connection Identity
Connection Endpoint Set
Direct Liability Connection
Indirect Liability Connection
Intermediate Connection Element
Liability Connection Chain
Liability Connection Network
Parallel Connection Structure
Converging Connection Structure
Diverging Connection Structure
Subject-Specific Connection
Relationship-Specific Connection
Object-Specific Connection
Condition-Specific Connection
Basis-Specific Connection
Temporal Connection Structure
Connection Evidence Association
Connection Relevance State
Connection Qualification State
Partial Connection
Unknown Connection
Uncertain Connection
Disputed Connection
Alternative Connection Chain
Connection Conflict
Connection Correction Record
Connection Reassessment Record
Connection Version Record
Historical Connection Record
Connection Sufficiency State
The principal output is:
Governed Liability Connection Structure
Critical Distinctions
LCNS preserves the following distinctions:
Liability-Relevant Connection ≠ Liability Determination Connected Elements ≠ Governed Connection by default Connection Identity ≠ Liability Identity Connection A → B ≠ Connection B → A by default Subject–Object Connection ≠ Liability Subject–Condition Connection ≠ Condition Satisfaction Liability Relationship ≠ Liability-Relevant Connection by default Conduct ≠ Liability No Action Observed ≠ Governed Omission by default Event ≠ Liability-Relevant Connection by itself Relevant State ≠ Liability-Relevant Connection by itself Consequence ≠ Liability Indirect Connection ≠ No Connection Complete Connection Chain ≠ Liability Determination Multi-Step Connection ≠ Single Connection by default Liability Connection Network ≠ Single Liability Connection Liability Relationship Network ≠ Liability Connection Network Temporal Proximity ≠ Liability-Relevant Connection by itself Temporal Distance ≠ Connection Absence by default Spatial Proximity ≠ Liability-Relevant Connection by default Dependency ≠ Liability by itself Control Connection ≠ Liability Determination Authority Connection ≠ Liability Responsibility Connection ≠ Liability Accountability ≠ Liability Identity Continuity ≠ Liability-Relevant Connection by itself Harm ≠ Liability Harm Connection ≠ Liability Determination Operational Causation ≠ Liability-Relevant Connection Factual Connection ≠ Liability-Relevant Connection by default Connection Relevance ≠ Liability Determination Qualified Liability Connection ≠ Established Liability Connection Strength ≠ Liability Strength Connection Sufficiency ≠ Connection Certainty Connection Uncertainty ≠ No Connection Unknown Connection ≠ Absent Connection Disputed Connection ≠ Established Connection by default Connection Conflict ≠ Authority to Select the Preferred Chain Multiple Plausible Chains ≠ One Established Chain Connection under Basis A ≠ Connection under Basis B by default Connection of Subject A ≠ Connection of Subject B Connection through Relationship A ≠ Connection through Relationship B by default Connection to Object A ≠ Connection to Object B by default Connection to Condition A ≠ Connection to Condition B by default Condition Satisfaction ≠ Connection Satisfaction Connection ≠ Condition Satisfaction Liability Basis ≠ Liability-Relevant Connection Liability Relationship ≠ Liability-Relevant Connection Liability Object ≠ Liability Connection Established Harm ≠ Established Liability-Relevant Connection Loss ≠ Liability-Relevant Connection Damage ≠ Liability-Relevant Connection Fault ≠ Liability-Relevant Connection by default Breach ≠ Liability-Relevant Connection by itself Responsibility ≠ Liability-Relevant Connection by itself Claimed Connection ≠ Governed Liability-Relevant Connection Payment ≠ Liability-Relevant Connection by itself Evidence ≠ Liability-Relevant Connection Evidence Volume ≠ Connection Sufficiency Missing Evidence ≠ No Connection by default Validated Input ≠ Qualified Liability Connection by itself Connection Change ≠ New Liability by default Connection Correction ≠ Historical Erasure Connection Reassessment ≠ Historical Rewrite New Connection Version ≠ New Connection by default Current Connection ≠ Historical Connection by default Later Connection Knowledge ≠ Earlier Connection Knowledge Connection Re-Entry ≠ New Liability Origin by default Operational Causation ≠ Liability Determination Harm ≠ Liability Connection ≠ Liability Adverse Outcome ≠ Liability-Relevant Connection Proximity ≠ Liability-Relevant Connection Relationship ≠ Connection Satisfied Conditions ≠ Liability-Relevant Connection One Consequence ≠ One Liability-Relevant Subject Connection Shared Outcome ≠ Equal Connection Broken Connection Chain ≠ Complete Liability-Relevant Connection Partial Connection ≠ Complete Connection Inferred Connection ≠ Directly Established Connection Assumed Connection ≠ Governed Connection Qualified Liability Connection ≠ Liability Connection Readiness ≠ Connection Certainty Governed Liability Connection Structure ≠ Liability Determination
Cross-Architecture Relationship
LCNS may consume governed inputs from other OOF® architectures while preserving their governance ownership.
ORA™ — Operational Reality Architecture governs actual Operational Reality and operational mechanisms. LCNS governs their Liability-specific connective relevance.
HAGA™ — Harm Governance Architecture governs Harm throughout its lifecycle. LCNS may connect a governed Harm state to Liability-relevant Subjects, Objects, Conditions, and other inputs where Harm is relevant.
AGA™ — Accountability Governance Architecture governs Responsibility, Accountability, and Attribution structures.
LCNS may use those states as Connection inputs without converting Accountability into Liability.
GOA™ — Governance Architecture may provide Authority, Scope, and Delegation states relevant to Connection structures.
ADIT® — Continuous Audit & Evidence Governance Architecture governs evidence and auditability. LCNS governs evidence association with Connections.
VALIDOS™ — Validation Governance Architecture governs validation of relevant inputs. Validation does not determine the Liability Connection by itself.
OBIDENITY® — Origin-Bound Identity Governance Architecture may establish Identity, Ownership, Authority, Permission, Provenance, Transfer, and Continuity necessary to preserve Connection identity.
AIG® — AI Governance Architecture may provide AI behavior and governance states relevant to Liability Connection.
ASGA™ — Autonomous Systems Governance Architecture may provide autonomous action, authority, execution, permission, override, and operational states.
PGA™ — Prediction Governance Architecture may provide governed Prediction and reliance-related states where those states become Liability-relevant.
SIMULOS® — Simulation Governance Architecture may provide simulation outputs used as analytical inputs, but a Simulation Output does not establish a Liability Connection.
The canonical cross-architecture principle is:
An operational, factual, evidentiary, Harm-related, accountability-related, identity-related, or other externally governed relationship may become an input to Liability Connection governance, but LIGA™ governs only its Liability-specific connective relevance.
Canonical Boundary
LCNS begins when:
a Governed Liability Object exists, a Governed Liability Basis exists, a Governed Liability Relationship Structure exists, and a Governed Liability Condition Structure is sufficiently established for the Liability inquiry to determine the relevant connective structure.
LCNS governs:
Connection Identification, Connection Identity, Connection Endpoints, Connection Direction, Direct and Indirect Connections, Intermediate Elements, Connection Chains, Connection Networks, Connection Sequence, Temporal Connection, Subject-Specific Connection, Relationship-Specific Connection, Object-Specific Connection, Condition-Specific Connection, Basis-Specific Connection, Connection Relevance, Connection Qualification, Evidence Association, Connection Uncertainty, Connection Conflict, Alternative Chains, Connection Change, Correction, Reassessment, Versioning, Historical Connection, and Connection Sufficiency.
LCNS does not govern:
the operational mechanism itself where another architecture owns it, Harm itself, evidence itself, Accountability itself, Responsibility itself, Identity itself, Condition formation or Condition State except as upstream input, Liability Attachment, Liability Determination, Liability Scope, Liability Allocation, Liability State, Liability Transfer, Recourse, Resolution, Discharge, or Finality.
LCNS ends when a:
Governed Liability Connection Structure
is sufficiently established for Liability Determination.
Complete Lifecycle Relationship
LCNS occupies the sixth governance space in the complete LIGA™ lifecycle.
Its role is neither merely evidentiary nor terminal.
It converts the previously governed:
Context, Object, Basis, Relationships,
and Conditions
into an explicit connective structure suitable for Liability Determination.
The complete progression remains:
Liability Relevance → Liability Object → Potential Liability Basis → Liability Relationship Structure → Liability Condition Structure → Liability Connection Structure → Liability Attachment & Determination → Liability Scope & Allocation → Active Liability Governance → Liability Change → Transfer / Recourse → Resolution / Discharge → Continuity / Re-Entry → Finality Therefore:
Liability Connection ≠ Liability Lifecycle Completion.
Recursive Lifecycle Principle
A later LIGA™ stage may reveal that the Connection Structure is incomplete or incorrect.
Re-entry should target the earliest materially affected governance space.
Examples:
missing Condition → LCOS, incorrect Relationship → LRS, incorrect Basis → LBS, incorrect Object → LOS, incorrect Connection Chain → LCNS.
Re-entry must preserve historical governance.
Re-entry must not rewrite history.
Historical Integrity
LCNS must preserve the distinction between:
what Connection existed, what Connection was represented, what Connection was known, what evidence was available, and what was discovered later.
Therefore:
Connection Reality ≠ Connection Knowledge ≠ Connection Record by default.
This distinction is essential for later Liability Determination and historical reassessment.
Canonical Principle
The canonical principle of LCNS is:
A Liability-relevant fact does not become a Liability-Relevant Connection merely because it occurred near, before, after, or in relation to another fact. The connection must itself be governed.
And:
A governed Connection makes Liability determinable. It does not make Liability exist.
Closing Statement
Liability cannot be determined reliably by moving directly from Harm, loss, damage, conduct, breach, control, responsibility, proximity, or evidence to a Liability conclusion.
The connective structure between the relevant Subject, Object, Conditions, conduct, events, states, and consequences must first be made explicit, traceable, qualified, and reconstructable.
Operational causation may explain what happened.
Evidence may support what happened.
Relationships may explain who was connected to whom.
Conditions may establish what had to be true.
LCNS governs the distinct question of how those elements are connected for Liability evaluation.
Connection makes Liability determinable. Connection does not determine Liability.
Govern the Connection before determining the Liability.
Mahlad
Liability Connection Standard (LCNS)
Architecture:
LIGA™ — Liability Governance Architecture
Category:
Governance & Enforcement
Subcategory:
Liability Governance
Canonical Definition:
The Liability Connection Standard (LCNS) governs how Liability-relevant connections among Liability Subjects, Governed Liability Objects, Governed Liability Conditions, conduct, events, states, actions, omissions, consequences, and other materially relevant inputs are identified, structured, traced, qualified, and represented before Liability Determination. It establishes the governed connective structure required to determine whether materially relevant elements are sufficiently connected for subsequent Liability evaluation without converting that Connection into Liability itself.
Governed Space:
Liability-Relevant Connection
LCNS governs the methodological bridge between established Liability Conditions and Liability Determination. It distinguishes operational causation, factual relationships, proximity, evidence, and other relevant inputs from the specific Liability-Relevant Connection that must be established before Liability can legitimately proceed toward Determination.
A governed Connection makes Liability determinable. It does not make Liability exist.
→ View Standard