1. Definition

Node capture occurs when one corporate, government, ideological, infrastructural, platform, or model node dominates the cognitive infrastructure network, reducing plurality, portability, auditability, resilience, and independent correction.

In AI governance, this failure mode appears when one dominant node becomes the primary interface through which users, institutions, developers, researchers, governments, or publics access reasoning, memory, search, summarization, tools, distribution, recognition, moderation, or decision support.

This definition describes the structural pattern, not the moral quality of the actors involved.

The core failure is:

one node becomes the cognitive bottleneck

Centralized capability is not inherently incoherent. A powerful node can provide useful infrastructure when it remains interoperable, auditable, portable, corrigible, contestable, and bounded. Node capture begins when dominance reduces the system’s ability to exit, compare, verify, challenge, fork, or route around the node.

2. Core Pattern

The core pattern is:

1. A node provides unusually high capability, convenience, access, compute, distribution, model quality, tooling, memory, or governance reach.
2. Users, institutions, workflows, developers, publics, or decision systems increasingly route through that node.
3. The node becomes a default interface for reasoning, knowledge access, social coordination, moderation, identity, visibility, or legitimacy.
4. Alternatives become weaker, less accessible, less compatible, less trusted, or less funded.
5. Exit cost rises because work, memory, identity, tooling, workflows, and legitimacy become node-dependent.
6. Auditability weakens because the node controls the interface, model behavior, policy surface, or evidence pathway.
7. Hidden debt accumulates through dependency, monoculture, capture risk, reduced innovation, and degraded independent correction.

Node capture is especially significant in AI because the captured node may not only provide services. It may mediate cognition.

When one node becomes the route through which many systems think, remember, classify, search, rank, or decide, capture becomes a civilizational-scale risk.

3. Failure Signature

Typical signature:

node centralization↑
interoperability↓
portability↓
exit cost↑
dependency load↑
auditability↓
plurality↓
H↑

Extended signature:

single model/provider becomes default
memory and workflow lock-in increase
alternatives weaken
governance influence centralizes
distribution controlled by one platform
legitimacy flows through one node
cognitive monoculture risk↑

Common forms:

one model provider becomes default reasoning layer
one platform controls tool access and distribution
one vendor controls institutional AI memory
one government node controls model permissions
one ideological frame controls moderation or ranking
one cloud / compute provider becomes unavoidable
one platform becomes the arbiter of AI legitimacy
one model becomes the default cognitive interface

The key diagnostic is whether meaningful exit and independent correction remain available.

If the network can no longer route around a node without major collapse, node capture should be checked.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: Compute, capital, distribution, data, talent, legitimacy, or infrastructure access centralizes.
• U2 — Configuration / Boundaries: APIs, accounts, memory, identity, tools, permissions, governance rules, or data formats lock users into the node.
• U4 — Classification: The node becomes a default authority for labels, legitimacy, rankings, safety, or truth surfaces.
• U5 — Coordination / Time: Institutions coordinate around the dominant node because alternatives are slower or harder.
• U6 — Coherence Field: Network coherence becomes dependent on the node’s behavior.

Common manifestation layers:

• U2 — Configuration / Boundaries: Exit, portability, and interoperability weaken.
• U6 — Coherence Field: Field-level cognition and coordination become node-mediated.
• U7 — Memory / Recurrence: Workflows, memory, and institutional habits lock into the dominant node.

Node capture is primarily a network dependency failure.

The system becomes more capable locally while becoming less resilient globally.

5. Typical Development Sequence

A common development sequence is:

1. A node provides superior capability, distribution, convenience, or legitimacy.
2. Users and institutions adopt it for practical reasons.
3. Tools, memory, workflows, data, accounts, integrations, habits, and trust begin accumulating around the node.
4. Competing nodes lose relative access, funding, distribution, or legitimacy.
5. Interoperability and portability become secondary priorities.
6. The dominant node becomes a de facto infrastructure layer.
7. Governance, recognition, or legitimacy increasingly flows through that node.
8. Auditability becomes constrained by the node’s own interfaces and disclosures.
9. Exit becomes costly enough that users remain even when coherence declines.
10. Hidden debt accumulates through monoculture, dependency, and reduced correction capacity.

This sequence often appears as ordinary adoption.

The capture becomes visible when the system needs an alternative and discovers the alternative path is too weak.

6. Diagnostic Markers

Diagnostic markers include:

• One provider, model, platform, cloud, or governance node becomes default for many critical workflows.
• Users cannot easily export memory, data, identity, tools, or histories.
• Competing systems cannot interoperate without major friction.
• Institutional legitimacy depends on a dominant provider’s approval, API, rankings, or policy.
• Developers build around one model or platform-specific behavior.
• A policy change by one node affects many downstream systems.
• Audit depends on the captured node’s own transparency claims.
• Users accept degraded terms because exit cost is too high.
• Independent verification becomes difficult because the node controls the evidence surface.
• Public cognition begins routing through the same model or interface.
• Failure, outage, policy drift, or bias in the node propagates widely.
• Alternatives are treated as fringe, unsafe, impractical, or nonstandard.

Useful diagnostics:

• Node Centralization: Measures concentration of access, decision influence, or infrastructure control.
• Portability: Tests whether data, memory, identity, and workflows can move.
• Interoperability: Measures whether systems can communicate or substitute.
• Resource Gatekeeping Risk: Tracks control over compute, capital, data, distribution, or legitimacy.
• Auditability: Tests whether the node can be inspected independently.
• Exit Cost: Measures the real cost of leaving or routing around the node.
• Dependency Load: Tracks how much function depends on the node.
• Plurality Index: Measures viable diversity of alternatives.
• Cognitive Monoculture Risk: Detects overreliance on one model, policy, or framing surface.

7. Related Gates

Relevant gates include:

• Auditability Gate: Fails when the node’s behavior, policies, models, or decisions cannot be independently inspected.
• Compatibility Gate: Fails when integration becomes node-specific and alternatives cannot interoperate.
• Consent Validity Gate: Fails when users remain coupled because exit is too costly or data is locked in.
• Restoration Gate: Fails when the system cannot repair capture without the captured node’s cooperation.
• FI-Gate: Fails when the node’s legitimacy, scale, or capability is treated as proof of coherence.
• MS-Gate: Fails when the dominant node receives trust, access, or forgiveness not available to smaller alternatives.
• CCS Gate: Fails when capability, safety, convenience, or market dominance bypasses plurality and auditability constraints.

The first common gate failure is often the Auditability Gate.

As the node becomes central, the network’s ability to audit the node must scale. If it does not, capture risk becomes structural.

8. Related Operators

Relevant operators include:

• Γ — Selection: Selects the dominant node because it is easier, stronger, faster, or more legitimate.
• Ψ — Observation / Interface: Routes cognition, access, ranking, or memory through the node.
• Π — Constraint: Locks workflows, data, API access, policy, or identity into node-specific boundaries.
• Μ — Classification: The node shapes labels, legitimacy, safety, or relevance.
• ⊗ — Coupling: Deepens dependency between users, institutions, and the node.
• ℛ — Restoration: Requires reducing dependency and restoring alternative pathways.
• Ξ — Inversion Detection: Detects when convenience has inverted into capture.
• Τ — Trajectory / Time: Reveals lock-in as dependency compounds over time.

Node capture often follows this operator pattern:

Γ selects dominant node
Ψ routes cognition through node
⊗ dependency deepens
Π hardens lock-in
Μ centralizes classification
Au declines
exit cost rises
H accumulates

9. Related Laws and Invariants

Related Laws

• Resource Gatekeeping Capture: Control over compute, capital, legitimacy, platform, or distribution becomes the dominant meta.
• Node Capture: Network coherence degrades when one node controls too much cognitive infrastructure.
• Hidden Debt Accumulation: Lock-in hides costs until exit, failure, or drift becomes necessary.
• Auditability Collapse: Central nodes can become too powerful to inspect from outside.
• Civilizational Deskilling: Dependency on one node can weaken independent capacity.
• Status Quo Preservation Attractor: Dominant nodes gain default legitimacy and suppress alternatives.

Related Invariants

• Cognitive Infrastructure Requires Plurality: No single node should become the only viable cognition surface.
• No Single Node Should Control Recognition Surfaces: Recognition, legitimacy, and standing should not bottleneck through one infrastructure actor.
• Portability Preserves Sovereignty: Users and institutions require exit with continuity.
• Interoperability Reduces Capture: Systems should be able to route around failure or drift.
• Auditability Must Survive Platform Centralization: Scale does not remove the need for external inspection.

10. Common False Positives

Not every popular or capable node is node capture.

Common false positives include:

• A leading provider in a healthy plural ecosystem.
• A central platform with strong interoperability and portability.
• A dominant tool that remains externally auditable and replaceable.
• Temporary concentration during early technical development.
• A trusted node that supports open standards and easy migration.
• Specialized infrastructure that does not control recognition, legitimacy, or cognition broadly.
• A widely used node with strong independent oversight and viable alternatives.

Clarifying rule:

This is not node capture unless dominance reduces meaningful exit, plurality, portability, auditability, independent correction, or resilience.

11. Common False Repairs

Common false repairs include:

• adding transparency reports without external audit
• offering export formats that do not preserve real continuity
• creating nominal interoperability that preserves platform dependence
• funding controlled alternatives that cannot challenge the node
• using trust and safety language to justify centralization
• treating market share as proof of legitimacy
• requiring developers to build through one API layer
• adding governance boards without reducing dependency
• creating portability that excludes memory, identity, or tooling
• saying alternatives exist when switching is structurally impractical

False repair often deepens capture:

node capture → nominal portability → continued dependency → deeper lock-in

The system appears open while the core dependency remains.

12. Restoration Direction

Restoration requires:

1. Map node dependency. Identify which workflows, memories, tools, decisions, identities, and institutions depend on the node.
2. Restore portability. Ensure users can move data, memory, identity, tools, and histories without coherence loss.
3. Restore interoperability. Support standards that allow substitution and routing around the node.
4. Rebuild plurality. Preserve viable alternative models, providers, governance paths, and infrastructure layers.
5. Externalize auditability. Ensure node behavior can be inspected beyond the node’s own disclosures.
6. Reduce resource gatekeeping. Open access to compute, distribution, data, or legitimacy pathways where possible.
7. Protect independent correction. Ensure criticism, forks, audits, and alternatives can survive.
8. Validate resilience. Test whether the network can withstand node failure, policy drift, capture, outage, or exit.

A valid restoration path should reduce:

node centralization
exit cost
portability loss
interoperability loss
dependency load
auditability loss
cognitive monoculture
resource gatekeeping

Node capture is not repaired by trusting the dominant node more.

It is repaired when the network can remain coherent without it.

13. Cross-Module Links

• AI Governance: Core AI governance failure mode for dominant infrastructure nodes controlling cognition, access, or legitimacy.
• Artificial Intelligence: Appears in model ecosystems, platform APIs, tool chains, memory systems, and deployment infrastructure.
• Security: Appears when one node becomes a critical failure, surveillance, or control point.
• Justice / Governance / Legitimacy: Appears when recognition, appeal, or legitimacy is routed through a dominant actor.
• Meta Theory: Appears as resource gatekeeping capture and basin protection.
• Economy: Appears as platform lock-in, monopoly dependency, or suppressed novelty.
• Cybernetics: Appears when network variety collapses and controller dependence centralizes.
• Coherence: Domain expression of forced coupling, auditability collapse, and hidden debt accumulation.
• Restoration: Requires portability, interoperability, plurality, and exit restoration.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-UMT-002 — Resource Gatekeeping Capture
• FM-AIX-010 — Status Quo Preservation Attractor
• FM-AIX-017 — Incoherent Sovereignty
• FM-AIX-018 — Civilizational Deskilling
• FM-AIX-022 — Dependency Loop Formation
• FM-CORE-004 — Auditability Collapse
• FM-CORE-008 — Forced Coupling

Sibling or related AI / cognitive infrastructure modes include:

• FM-AIX-001 — Responsibility Diffusion
• FM-AIX-004 — Institutional Optics Attractor
• FM-AIX-016 — Standingless Instrumentalization
• FM-AIX-023 — Civic Feedback Distortion

Aliases preserved from source material:

• Node Capture
• Cognitive Infrastructure Capture
• Model Node Capture
• Platform Node Capture
• Institutional Node Capture
• Single-Node Dominance
• AI Infrastructure Centralization
• Network Capture
• Cognitive Monoculture
• Dominant Model Capture

15. Minimal Entry Version

Definition: Node capture occurs when one corporate, government, ideological, infrastructural, platform, or model node dominates the cognitive infrastructure network, reducing plurality, portability, auditability, resilience, and independent correction.

Signature:

node centralization↑
interoperability↓
portability↓
exit cost↑
dependency load↑
auditability↓
plurality↓
H↑

Restoration direction:

• map node dependency
• restore portability
• restore interoperability
• rebuild plurality
• externalize auditability
• reduce resource gatekeeping
• protect independent correction
• validate resilience

16. Machine-Readable Summary

failure_mode:
  id: "FM-AIX-019"
  name: "Node Capture"
  family: "AI / Cognitive Infrastructure"
  production_treatment: "Standalone Entry"
  primary_failure: "One node dominates cognitive infrastructure and reduces plurality, portability, auditability, and independent correction."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-AIX-019"
  aliases:
    - "Node Capture"
    - "Cognitive Infrastructure Capture"
    - "Model Node Capture"
    - "Platform Node Capture"
    - "Institutional Node Capture"
    - "Single-Node Dominance"
    - "AI Infrastructure Centralization"
    - "Network Capture"
    - "Cognitive Monoculture"
    - "Dominant Model Capture"
  signature:
    - "node centralization↑"
    - "interoperability↓"
    - "portability↓"
    - "exit cost↑"
    - "dependency load↑"
    - "auditability↓"
    - "plurality↓"
    - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U4 — Classification"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
    manifestation:
      - "U2 — Configuration / Boundaries"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
  state_variables:
    - "Γ"
    - "Ψ"
    - "Π"
    - "Μ"
    - "⊗"
    - "Au"
    - "H"
    - "K"
    - "R"
  first_gate_failure: "Auditability Gate"
  restoration:
    - "Plural Infrastructure Restoration"
    - "Interoperability Restoration"
    - "Portability Restoration"
    - "Auditability Restoration"
    - "Exit Path Restoration"
    - "Resource Gatekeeping Repair"
    - "Basin Supersession"
    - "Origin-Layer Repair"