{
  "capabilityNamespaces": [
    {
      "definition": "A capability for coordinating compute resources, network conditions, and workload requirements across distributed AI infrastructure.",
      "deploymentStatus": "active",
      "directAnswer": "This namespace frames the coordination of compute, network, and workload context without prescribing a required implementation.",
      "governingQuestion": "How can compute and network context be coordinated for distributed AI workloads?",
      "id": "https://intelligentcomputefabric.com/#intelligent-compute-fabric",
      "name": "Intelligent Compute Fabric",
      "publicationStatus": "published",
      "relationshipContext": "Intelligent Compute Fabric is related to AI Workload Routing, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "aiworkloadrouting.com",
        "difference": "Intelligent Compute Fabric addresses a distinct architectural boundary from AI Workload Routing.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "datacenterinterconnect.ai",
          "aiopticalbackbone.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/intelligent-compute-fabric",
      "url": "https://intelligentcomputefabric.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "The connectivity and transport relationships that link data-center environments, compute clusters, and service locations.",
      "deploymentStatus": "active",
      "directAnswer": "This reference defines the interconnect evaluation boundary without prescribing a specific optical interface, carrier, or topology.",
      "governingQuestion": "How should distributed AI environments relate their data-center connectivity and transport boundaries?",
      "id": "https://datacenterinterconnect.ai/#datacenter-interconnect",
      "name": "Datacenter Interconnect",
      "publicationStatus": "published",
      "relationshipContext": "Datacenter Interconnect is related to AI Optical Backbone, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "aiopticalbackbone.com",
        "difference": "Datacenter Interconnect addresses a distinct architectural boundary from AI Optical Backbone.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "fibercontrolplane.com",
          "losslessfabric.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/datacenter-interconnect",
      "url": "https://datacenterinterconnect.ai/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "The optical transport context that supports high-capacity connectivity among AI infrastructure locations and compute environments.",
      "deploymentStatus": "active",
      "directAnswer": "This namespace isolates the optical-transport role supporting distributed AI infrastructure without defining a vendor architecture.",
      "governingQuestion": "What role can optical transport play between distributed AI infrastructure locations?",
      "id": "https://aiopticalbackbone.com/#ai-optical-backbone",
      "name": "AI Optical Backbone",
      "publicationStatus": "published",
      "relationshipContext": "AI Optical Backbone is related to Datacenter Interconnect, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "datacenterinterconnect.ai",
        "difference": "AI Optical Backbone addresses a distinct architectural boundary from Datacenter Interconnect.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "losslessfabric.com",
          "computeawareqos.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/ai-optical-backbone",
      "url": "https://aiopticalbackbone.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "The control and coordination context for fiber-based transport resources and their relationship to higher-layer infrastructure decisions.",
      "deploymentStatus": "active",
      "directAnswer": "This reference defines the control-layer boundary for fiber transport without prescribing a control-plane implementation.",
      "governingQuestion": "How can fiber transport coordination be related to AI infrastructure planning without prescribing a control implementation?",
      "id": "https://fibercontrolplane.com/#fiber-control-plane",
      "name": "Fiber Control Plane",
      "publicationStatus": "published",
      "relationshipContext": "Fiber Control Plane is related to AI Optical Backbone, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "aiopticalbackbone.com",
        "difference": "Fiber Control Plane addresses a distinct architectural boundary from AI Optical Backbone.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "computeawareqos.com",
          "aiandcommunication.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/fiber-control-plane",
      "url": "https://fibercontrolplane.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "An architectural concept for fabric behavior that seeks to preserve required traffic delivery characteristics under explicitly defined conditions.",
      "deploymentStatus": "active",
      "directAnswer": "This namespace frames delivery and congestion behavior without defining one mandatory transport or fabric design.",
      "governingQuestion": "Which delivery characteristics must a fabric preserve for the workload and operating context at hand?",
      "id": "https://losslessfabric.com/#lossless-fabric",
      "name": "Lossless Fabric",
      "publicationStatus": "published",
      "relationshipContext": "Lossless Fabric is related to Compute-Aware Quality of Service, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "computeawareqos.com",
        "difference": "Lossless Fabric addresses a distinct architectural boundary from Compute-Aware Quality of Service.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "aiandcommunication.com",
          "multimodaldatafusion.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/lossless-fabric",
      "url": "https://losslessfabric.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "An architectural concept for relating service treatment to workload and compute context without defining a universal quality-of-service policy.",
      "deploymentStatus": "active",
      "directAnswer": "This reference isolates the relationship between compute context and service treatment without defining a universal QoS policy.",
      "governingQuestion": "How can service treatment be evaluated in relation to compute and workload context?",
      "id": "https://computeawareqos.com/#compute-aware-quality-of-service",
      "name": "Compute-Aware Quality of Service",
      "publicationStatus": "published",
      "relationshipContext": "Compute-Aware Quality of Service is related to Lossless Fabric, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "losslessfabric.com",
        "difference": "Compute-Aware Quality of Service addresses a distinct architectural boundary from Lossless Fabric.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "multimodaldatafusion.com",
          "interconnectorchestration.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/compute-aware-qos",
      "url": "https://computeawareqos.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "An architectural namespace for the relationship between AI workloads, communication systems, and the infrastructure that connects them.",
      "deploymentStatus": "active",
      "directAnswer": "This namespace provides an implementation-neutral reference for evaluating AI workload and communication-system relationships.",
      "governingQuestion": "How should AI workload needs and communication-system context be considered together?",
      "id": "https://aiandcommunication.com/#ai-and-communication",
      "name": "AI and Communication",
      "publicationStatus": "published",
      "relationshipContext": "AI and Communication is related to Intelligent Compute Fabric, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "intelligentcomputefabric.com",
        "difference": "AI and Communication addresses a distinct architectural boundary from Intelligent Compute Fabric.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "interconnectorchestration.com",
          "aiworkloadrouting.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/ai-and-communication",
      "url": "https://aiandcommunication.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "An architectural concept for relating multiple data forms and sources in a common workload or decision context.",
      "deploymentStatus": "active",
      "directAnswer": "This reference frames the relationship among heterogeneous data forms without prescribing one fusion method or data architecture.",
      "governingQuestion": "How can multiple data forms be related without treating data fusion as a universal implementation pattern?",
      "id": "https://multimodaldatafusion.com/#multimodal-data-fusion",
      "name": "Multimodal Data Fusion",
      "publicationStatus": "published",
      "relationshipContext": "Multimodal Data Fusion is related to AI Workload Routing, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "aiworkloadrouting.com",
        "difference": "Multimodal Data Fusion addresses a distinct architectural boundary from AI Workload Routing.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "intelligentcomputefabric.com",
          "datacenterinterconnect.ai"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/multimodal-data-fusion",
      "url": "https://multimodaldatafusion.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "The coordination of interconnect relationships, service constraints, and operational intent across a distributed infrastructure environment.",
      "deploymentStatus": "active",
      "directAnswer": "This namespace defines the coordination boundary among interconnect relationships without prescribing a vendor orchestration platform.",
      "governingQuestion": "How can interconnect relationships be coordinated without prescribing a vendor control plane?",
      "id": "https://interconnectorchestration.com/#interconnect-orchestration",
      "name": "Interconnect Orchestration",
      "publicationStatus": "published",
      "relationshipContext": "Interconnect Orchestration is related to Fiber Control Plane, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "fibercontrolplane.com",
        "difference": "Interconnect Orchestration addresses a distinct architectural boundary from Fiber Control Plane.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "datacenterinterconnect.ai",
          "aiopticalbackbone.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/interconnect-orchestration",
      "url": "https://interconnectorchestration.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    },
    {
      "definition": "The architectural consideration of how AI workloads are directed among eligible compute, data, and network contexts.",
      "deploymentStatus": "active",
      "directAnswer": "This reference isolates workload placement and path-selection questions without defining one routing or scheduling method.",
      "governingQuestion": "How can workload placement and path choices be evaluated across distributed AI infrastructure?",
      "id": "https://aiworkloadrouting.com/#ai-workload-routing",
      "name": "AI Workload Routing",
      "publicationStatus": "published",
      "relationshipContext": "AI Workload Routing is related to Intelligent Compute Fabric, but each addresses a distinct architectural question.",
      "relationshipPresentation": {
        "closest_related": "intelligentcomputefabric.com",
        "difference": "AI Workload Routing addresses a distinct architectural boundary from Intelligent Compute Fabric.",
        "relationship": "The concepts can be evaluated together when their respective infrastructure roles are relevant.",
        "see_also": [
          "fibercontrolplane.com",
          "losslessfabric.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/ai-workload-routing",
      "url": "https://aiworkloadrouting.com/",
      "whyItMatters": "AI infrastructure choices depend on clear boundaries among infrastructure functions so that assumptions, interfaces, and evidence can be evaluated in context."
    }
  ],
  "credibilityBoundary": "Implementation-neutral public orientation; no certification, endorsement, regulatory determination, or performance guarantee.",
  "editorialModel": "2.2",
  "lastModified": "2026-08-06",
  "manifestType": "ljp.public-package-namespace",
  "manifestVersion": "1.0",
  "package": {
    "authorityContext": "Network Compute Fabric is a package-level architectural synthesis rather than a term governed by a single standards body. Its constituent capabilities carry different levels of institutional support. \"Artificial Intelligence and Communication\" appears directly in Recommendation ITU-R M.2160-0. Data Center Interconnect is directly represented in published OIF interoperability work. Multimodal Data Fusion appears directly in active IEEE standards development. Other namespaces either map to established underlying architectural functions or remain LJP-defined compound terms for which no institutional body currently defines the complete concept. Each capability page identifies its own authority basis, standards-development status, and evidentiary boundary.",
    "authorityReferences": [
      {
        "applies_to": "networkcomputefabric.com",
        "document_id": "draft-calabria-bmwg-ai-fabric-terminology-02",
        "id": "ai-fabric-terminology-id",
        "organization": "Internet Engineering Task Force Datatracker",
        "public_authorized": true,
        "relevance": "Active individual Internet-Draft describing terminology for Ethernet-based AI network fabrics, including RDMA, RoCEv2, UET, congestion, collectives, and topology.",
        "scope_note": "Work in progress with no formal IETF standing or endorsement; supports underlying technical convergence only.",
        "title": "Benchmarking Terminology for AI Network Fabrics",
        "url": "https://datatracker.ietf.org/doc/draft-calabria-bmwg-ai-fabric-terminology/02/"
      },
      {
        "applies_to": "networkcomputefabric.com",
        "document_id": "draft-calabria-bmwg-ai-fabric-training-bench-02",
        "id": "ai-training-fabric-methodology-id",
        "organization": "Internet Engineering Task Force Datatracker",
        "public_authorized": true,
        "relevance": "Active individual Internet-Draft describing benchmarking methods and KPIs for Ethernet-based AI training fabrics and their workload behavior.",
        "scope_note": "Work in progress with no formal IETF standing or endorsement; it does not define the LJP compound term.",
        "title": "Benchmarking Methodology for AI Training Network Fabrics",
        "url": "https://datatracker.ietf.org/doc/draft-calabria-bmwg-ai-fabric-training-bench/02/"
      }
    ],
    "definition": "A technical-reference package for relating network infrastructure, distributed compute, interconnect, optical transport, workload movement, and operational coordination for AI infrastructure.",
    "deploymentStatus": "active",
    "domainContext": "AI infrastructure depends on the relationship between network and compute fabric, interconnect, optical transport, workload movement, service treatment, data fusion, and operational coordination. This package keeps those roles distinct so an enterprise can evaluate the architecture without treating any one layer as the complete solution.",
    "id": "https://networkcomputefabric.com/#ai-interconnect-compute-fabric",
    "name": "Network Compute Fabric",
    "namespaceName": "AI Interconnect & Compute Fabric",
    "publicationStatus": "published",
    "relationshipContext": "Network Compute Fabric provides the package orientation. Intelligent Compute Fabric relates workload and resource context; Datacenter Interconnect and AI Optical Backbone address connectivity and transport; Fiber Control Plane and Interconnect Orchestration address coordination; Lossless Fabric and Compute-Aware Quality of Service address service behavior; AI and Communication, Multimodal Data Fusion, and AI Workload Routing address workload and information relationships. The sequence is a buyer-oriented architecture map, not an implementation order.",
    "role": "canonical-package-namespace",
    "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/network-compute-fabric",
    "url": "https://networkcomputefabric.com/",
    "whyItMatters": "Distributed AI workloads span compute placement, data movement, transport capacity, service behavior, and operational coordination. Decisions become difficult to compare when these architectural roles are collapsed into a single product or network claim."
  },
  "principle": "Publish the map, not the machine.",
  "publicResources": {
    "buyerWalkthrough": "https://networkcomputefabric.com/storyboard",
    "llms": "https://networkcomputefabric.com/llms.txt",
    "namespaceManifest": "https://networkcomputefabric.com/namespace.json",
    "ontology": "https://networkcomputefabric.com/ontology.jsonld",
    "overview": "https://networkcomputefabric.com/",
    "robots": "https://networkcomputefabric.com/robots.txt",
    "sitemap": "https://networkcomputefabric.com/sitemap.xml"
  },
  "publisher": {
    "contact": "support@ljpassetgroup.com",
    "id": "https://ljpassetgroup.com/#org",
    "name": "LJP Asset Group LLC",
    "url": "https://ljpassetgroup.com/"
  },
  "supportingNamespaces": [],
  "version": "2.2.1"
}