{
  "capabilityNamespaces": [
    {
      "definition": "A semantic label for fleet-level responsibility organization across advanced-reactor program context; it is not reactor software.",
      "deploymentStatus": "active",
      "directAnswer": "By using Reactor OS only as a semantic framing layer for roles, interfaces, and decision context, while reserving all reactor protection, control, operating, and safety functions for licensed and qualified systems and personnel.",
      "governingQuestion": "How can a fleet-level conversation distinguish responsibility organization from plant control and safety functions?",
      "id": "https://reactoros.ai/#reactor-os",
      "name": "Reactor OS",
      "publicationStatus": "published",
      "relationshipContext": "Reactor OS can sit beside SMR Orchestration as a responsibility framing, but it neither assigns nor executes project, facility, or reactor actions.",
      "relationshipPresentation": {
        "closest_related": "smrorchestration.com",
        "difference": "Reactor OS frames responsibility context; SMR Orchestration frames a bounded program-sequencing conversation.",
        "relationship": "Both help a reviewer distinguish semantic coordination from regulated, operational, and engineering authority.",
        "see_also": [
          "nuclearsovereignty.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://reactoros.ai/",
      "whyItMatters": "The phrase can invite an unsafe category error if it is mistaken for a control-room, protection, operating, or safety product."
    },
    {
      "definition": "A semantic framing for sequencing conversations across a small-modular-reactor program without performing or directing the work.",
      "deploymentStatus": "active",
      "directAnswer": "It can map handoffs and decision dependencies as a semantic program view, while leaving licensing, engineering, commissioning, procurement, construction, and operating decisions to the parties with actual authority.",
      "governingQuestion": "What sequencing dependencies should a program discussion make visible without claiming project authority?",
      "id": "https://smrorchestration.com/#smr-orchestration",
      "name": "SMR Orchestration",
      "publicationStatus": "published",
      "relationshipContext": "It is closest to Reactor OS because both concern coordination language, but neither has plant, project, regulatory, or commercial authority.",
      "relationshipPresentation": {
        "closest_related": "reactoros.ai",
        "difference": "SMR Orchestration frames sequencing dependencies; Reactor OS frames responsibility organization.",
        "relationship": "Together they help expose where program language stops and qualified, accountable action begins.",
        "see_also": [
          "powerawarecompute.com",
          "nuclearsovereignty.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://smrorchestration.com/",
      "whyItMatters": "Advanced-reactor deployment involves distinct public, commercial, technical, and regulated tracks that should not be represented as one controllable workflow."
    },
    {
      "definition": "A semantic framing for considering compute demand in relation to power-system context without claiming to optimize either system.",
      "deploymentStatus": "active",
      "directAnswer": "By treating Power-Aware Compute as a vocabulary for asking what electricity, workload, location, and timing evidence would be relevant, while leaving dispatch, optimization, capacity planning, and service commitments outside the namespace.",
      "governingQuestion": "How can compute demand be discussed alongside power context without turning the discussion into a performance promise?",
      "id": "https://powerawarecompute.com/#power-aware-compute",
      "name": "Power-Aware Compute",
      "publicationStatus": "published",
      "relationshipContext": "Power-Aware Compute relates to Grid-to-Inference as a peer perspective on demand, not as a requirement imposed on a grid, generator, data center, or workload.",
      "relationshipPresentation": {
        "closest_related": "smrorchestration.com",
        "difference": "Power-Aware Compute frames demand-side questions; SMR Orchestration frames program-sequencing questions.",
        "relationship": "The peer terms support a bounded discussion of interfaces without prescribing grid dispatch, compute scheduling, or commercial outcomes.",
        "see_also": [
          "reactoros.ai"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://powerawarecompute.com/",
      "whyItMatters": "Compute and electricity-system narratives often overstate what a demand-aware framing can decide or guarantee."
    },
    {
      "definition": "An analytical label for examining strategic dependencies and resilience considerations in nuclear-related value chains.",
      "deploymentStatus": "active",
      "directAnswer": "By identifying dependencies, alternatives, governance choices, and evidence limits while avoiding claims that any country, firm, or program should pursue autarky or that a particular arrangement is strategically sufficient.",
      "governingQuestion": "How can strategic dependency be examined without reducing resilience to nationalism or self-sufficiency claims?",
      "id": "https://nuclearsovereignty.com/#nuclear-sovereignty",
      "name": "Nuclear Sovereignty",
      "publicationStatus": "published",
      "relationshipContext": "It relates to SMR Orchestration through external dependencies and to Grid-to-Inference through infrastructure context, while remaining a non-operational analytical lens.",
      "relationshipPresentation": {
        "closest_related": "smrorchestration.com",
        "difference": "Nuclear Sovereignty examines strategic dependencies; SMR Orchestration frames program-sequencing questions.",
        "relationship": "A program discussion may need to disclose dependencies, but dependency analysis does not direct a program or determine policy.",
        "see_also": [
          "powerawarecompute.com",
          "reactoros.ai"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://nuclearsovereignty.com/",
      "whyItMatters": "Nuclear supply, fuel-cycle, technology, and governance discussions can become imprecise when interdependence and resilience are framed as political slogans."
    }
  ],
  "credibilityBoundary": "Implementation-neutral public orientation; no certification, endorsement, regulatory determination, or performance guarantee.",
  "editorialModel": "2.2",
  "lastModified": "2026-08-17",
  "manifestType": "ljp.public-package-namespace",
  "manifestVersion": "1.0",
  "package": {
    "authorityContext": "DOE describes advanced-nuclear commercialization as a value-chain challenge. LJP uses that context only to frame a public semantic package; the source does not define or endorse these LJP terms.",
    "authorityReferences": [
      {
        "applies_to": "gridtoinference.com",
        "document_id": "LIFTOFF_DOE_Advanced-Nuclear",
        "id": "doe-advanced-nuclear-liftoff-2025",
        "organization": "U.S. Department of Energy",
        "public_authorized": true,
        "relevance": "Provides public value-chain context for advanced-nuclear commercialization.",
        "scope_note": "Context only; the source does not define or endorse LJP terminology.",
        "title": "Pathways to Commercial Liftoff: Advanced Nuclear",
        "url": "https://www.energy.gov/sites/default/files/2025-07/LIFTOFF_DOE_Advanced-Nuclear.pdf"
      }
    ],
    "definition": "A semantic reference for relating grid conditions, advanced-nuclear program context, and compute demand without treating any one layer as operational authority.",
    "deploymentStatus": "active",
    "domainContext": "The U.S. Department of Energy identifies electricity-demand growth and advanced-nuclear commercialization as cross-value-chain matters involving many stakeholders. This package provides a bounded vocabulary for discussing those relationships.",
    "id": "https://gridtoinference.com/#ai-power-infrastructure-layer",
    "name": "Grid-to-Inference",
    "namespaceName": "AI Power Infrastructure Layer",
    "publicationStatus": "published",
    "relationshipContext": "The package connects four peers without turning them into an execution sequence, product architecture, or authority hierarchy.",
    "role": "canonical-package-namespace",
    "semanticAuthority": "repository-governed-source",
    "url": "https://gridtoinference.com/",
    "whyItMatters": "Infrastructure discussions become less reliable when technical, regulated, commercial, and strategic questions are collapsed into a single claim. A shared semantic map keeps those questions distinguishable."
  },
  "principle": "Publish the map, not the machine.",
  "publicResources": {
    "buyerWalkthrough": "https://gridtoinference.com/storyboard",
    "llms": "https://gridtoinference.com/llms.txt",
    "namespaceManifest": "https://gridtoinference.com/namespace.json",
    "ontology": "https://gridtoinference.com/ontology.jsonld",
    "overview": "https://gridtoinference.com/",
    "robots": "https://gridtoinference.com/robots.txt",
    "sitemap": "https://gridtoinference.com/sitemap.xml"
  },
  "publisher": {
    "contact": "https://www.ljpassetgroup.com/contact/",
    "id": "ljp-asset-group",
    "name": "LJP Asset Group",
    "url": "https://www.ljpassetgroup.com/"
  },
  "supportingNamespaces": [],
  "version": "2.2.0"
}