{
  "capabilityNamespaces": [
    {
      "definition": "The capacity of a positioning, navigation, and timing architecture to sustain, recover, or adapt its required functions when sources, environments, or dependencies are disrupted or degraded.",
      "deploymentStatus": "active",
      "directAnswer": "Resilient PNT is the ability of a PNT-dependent system to maintain an acceptable service, operate within defined degradation, or recover to a required state when signals, sources, data, or supporting infrastructure are disrupted or manipulated. The required behavior must be defined for the mission and verified against relevant threats and failure conditions.",
      "id": "https://resilientpnt.ai/#resilient-pnt",
      "name": "Resilient PNT",
      "publicationStatus": "published",
      "questionOwned": "How does required PNT service continue through disruption or degradation?",
      "relationshipContext": "Resilient PNT is closest to Assured PNT because both are mission-conditioned outcomes. Resilience focuses on continuity and recovery during adversity; assurance focuses on the evidence supporting confidence that the result remains fit for use.",
      "relationshipPresentation": {
        "closest_related": "assuredpnt.ai",
        "difference": "Resilient PNT asks how required service continues or recovers during adversity; Assured PNT asks what evidence supports confidence that the resulting PNT is fit for the mission.",
        "relationship": "Resilience requirements define expected behavior under disruption, while assurance evaluates whether the evidence and controls justify relying on that behavior.",
        "see_also": [
          "navigationintegrity.com",
          "pntfusion.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/resilient-pnt",
      "url": "https://resilientpnt.ai/",
      "whyItMatters": "A receiver can be accurate in normal conditions yet fail operationally when a source is blocked, jammed, spoofed, unavailable, or internally compromised. Buyers therefore need explicit continuity, degradation, detection, recovery, and reporting requirements rather than a generic resilience label."
    },
    {
      "definition": "The disciplined evaluation of whether positioning, navigation, and timing information is sufficiently dependable for a stated mission, operating condition, and decision context.",
      "deploymentStatus": "active",
      "directAnswer": "Assured PNT is a mission-specific confidence judgment supported by evidence that PNT information, sources, equipment, and operating controls satisfy defined requirements under expected conditions and credible threats. Assurance depends on what must be trusted, for which decision, and with what verification; it is not created by attaching the word assured to a product.",
      "id": "https://assuredpnt.ai/#assured-pnt",
      "name": "Assured PNT",
      "publicationStatus": "published",
      "questionOwned": "What supports confidence that PNT is fit for the intended mission?",
      "relationshipContext": "Assured PNT is closest to Navigation Integrity because both concern justified reliance. Integrity focuses on the trustworthiness and alerting status of navigation information; assurance combines that evidence with mission requirements, operating conditions, cybersecurity, governance, and other controls.",
      "relationshipPresentation": {
        "closest_related": "navigationintegrity.com",
        "difference": "Assured PNT is the broader mission-confidence judgment; Navigation Integrity addresses whether navigation information and its status support continued use or require qualification or rejection.",
        "relationship": "Integrity evidence can support assurance, but assurance also considers mission requirements, operating conditions, resilience, cybersecurity, governance, and other evidence.",
        "see_also": [
          "resilientpnt.ai",
          "pntfusion.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/assured-pnt",
      "url": "https://assuredpnt.ai/",
      "whyItMatters": "Availability alone does not establish that PNT information is authentic, sufficiently accurate, timely, protected, or appropriate for a decision. Technical, operational, cybersecurity, safety, and acquisition teams need an explicit evidence basis for reliance."
    },
    {
      "definition": "The architectural combination of multiple positioning, navigation, and timing sources or observations to support a more complete mission-relevant PNT result.",
      "deploymentStatus": "active",
      "directAnswer": "PNT Fusion combines measurements, estimates, or status from multiple authorized sources into a coherent PNT result or decision input. A sound fusion design accounts for source independence, uncertainty, integrity, timing, failure modes, and the possibility that one source can contaminate the result; the appropriate method depends on the mission and architecture.",
      "id": "https://pntfusion.com/#pnt-fusion",
      "name": "PNT Fusion",
      "publicationStatus": "published",
      "questionOwned": "How can multiple PNT sources be organized into a coherent result?",
      "relationshipContext": "PNT Fusion is closest to Opportunistic PNT. Opportunistic PNT expands the candidate source set; fusion determines how qualified inputs from dedicated and non-dedicated sources may contribute to a coherent result.",
      "relationshipPresentation": {
        "closest_related": "opportunisticpnt.com",
        "difference": "PNT Fusion governs how qualified inputs are combined; Opportunistic PNT identifies non-dedicated signals, observations, or features that might become candidate inputs.",
        "relationship": "Opportunistic sources may expand a fusion architecture, while fusion must still evaluate their uncertainty, independence, integrity, timing, legality, and failure behavior.",
        "see_also": [
          "navigationintegrity.com",
          "assuredpnt.ai"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/pnt-fusion",
      "url": "https://pntfusion.com/",
      "whyItMatters": "Adding sources does not automatically improve resilience or assurance. Sources may share common dependencies, disagree, arrive at different rates, or fail in correlated ways, so buyers must evaluate how inputs are qualified, combined, isolated, and reported."
    },
    {
      "definition": "The degree to which navigation information and its associated status can be relied upon for a stated use, including the ability to identify when that reliance may no longer be appropriate.",
      "deploymentStatus": "active",
      "directAnswer": "Navigation integrity concerns whether navigation information is trustworthy for a stated operation and whether the user receives a timely indication when it should not be used. The required error bounds, alerting behavior, monitoring, and response depend on the application; integrity is distinct from accuracy and availability.",
      "id": "https://navigationintegrity.com/#navigation-integrity",
      "name": "Navigation Integrity",
      "publicationStatus": "published",
      "questionOwned": "When should navigation information be trusted, qualified, or rejected?",
      "relationshipContext": "Navigation Integrity is closest to Assured PNT. Integrity supplies evidence about the correctness and status of navigation information; assurance determines whether the combined evidence is sufficient for mission reliance.",
      "relationshipPresentation": {
        "closest_related": "assuredpnt.ai",
        "difference": "Navigation Integrity addresses the trustworthiness and alerting status of navigation information; Assured PNT is the broader mission judgment about whether PNT is fit for reliance.",
        "relationship": "Integrity monitoring and status can provide essential assurance evidence, while assurance also considers continuity, cybersecurity, operating context, procedures, and other controls.",
        "see_also": [
          "pntfusion.com",
          "resilientpnt.ai"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/navigation-integrity",
      "url": "https://navigationintegrity.com/",
      "whyItMatters": "Incorrect navigation information can be more hazardous than unavailable information because a system may continue acting on a plausible but misleading result. Buyers must therefore specify acceptable risk, monitoring, alerting, and operational response for the intended use."
    },
    {
      "definition": "The use of signals, observations, or environmental features not dedicated solely to PNT as potential contributors to positioning, navigation, or timing.",
      "deploymentStatus": "active",
      "directAnswer": "Opportunistic PNT uses signals, observations, or environmental features created for another purpose as potential positioning, navigation, or timing inputs. Examples can include communications broadcasts or natural phenomena, but each candidate source must be evaluated for access, stability, observability, legality, uncertainty, integrity, and operational availability.",
      "id": "https://opportunisticpnt.com/#opportunistic-pnt",
      "name": "Opportunistic PNT",
      "publicationStatus": "published",
      "questionOwned": "Which non-dedicated sources may contribute useful PNT context?",
      "relationshipContext": "Opportunistic PNT is closest to PNT Fusion. It identifies possible non-dedicated inputs; fusion addresses how qualified sources may be incorporated without allowing an uncertain or compromised input to dominate the result.",
      "relationshipPresentation": {
        "closest_related": "pntfusion.com",
        "difference": "Opportunistic PNT identifies non-dedicated candidate sources; PNT Fusion addresses qualification and combination of multiple sources into a coherent result.",
        "relationship": "An opportunistic source becomes useful only when an architecture can observe, characterize, authorize, and integrate it without overstating its stability or integrity.",
        "see_also": [
          "resilientpnt.ai",
          "navigationintegrity.com"
        ]
      },
      "role": "capability-namespace",
      "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/opportunistic-pnt",
      "url": "https://opportunisticpnt.com/",
      "whyItMatters": "Non-dedicated sources may provide useful context where conventional PNT is obstructed or denied, but they are not controlled as navigation services and may change without notice. Their value depends on disciplined qualification rather than assumed availability."
    }
  ],
  "credibilityBoundary": "Implementation-neutral public orientation; no certification, endorsement, regulatory determination, or performance guarantee.",
  "editorialModel": "2.2",
  "lastModified": "2026-07-31",
  "manifestType": "ljp.public-package-namespace",
  "manifestVersion": "1.0",
  "package": {
    "authorityContext": "NIST treats PNT dependence as a risk-management issue for systems and critical infrastructure, while GPS.gov consolidates United States policy and resilience guidance for responsible PNT use. LJP uses those sources to bound the technical problem; neither source defines or endorses this package.",
    "authorityReferences": [
      {
        "applies_to": "sovereignpnt.com",
        "document_id": "NIST IR 8323 Revision 1",
        "evidence_role": "supporting_source",
        "id": "nist-ir-8323r1-package",
        "organization": "National Institute of Standards and Technology",
        "public_authorized": true,
        "publication_context": "Published January 31, 2023",
        "relevance": "Provides a risk-management framework for identifying PNT-dependent assets, managing disruption and manipulation risk, and developing organization-specific PNT profiles.",
        "scope_note": "NIST guidance is authoritative for its stated risk-management scope; the LJP package organization remains editorial.",
        "title": "Foundational PNT Profile: Applying the Cybersecurity Framework for the Responsible Use of PNT Services",
        "url": "https://www.nist.gov/publications/foundational-pnt-profile-applying-cybersecurity-framework-responsible-use-positioning"
      },
      {
        "applies_to": "sovereignpnt.com",
        "document_id": "Official GPS.gov resilience resource",
        "evidence_role": "supporting_source",
        "id": "gpsgov-responsible-use-package",
        "organization": "National Coordination Office for Space-Based Positioning, Navigation, and Timing",
        "public_authorized": true,
        "publication_context": "Official United States government resource",
        "relevance": "Summarizes United States policy and resources addressing critical-infrastructure dependence, disruption, manipulation, verification, and responsible PNT use.",
        "scope_note": "The source provides policy and resilience context and does not define or endorse the LJP package.",
        "title": "Resilience Through Responsible Use of PNT",
        "url": "https://www.gps.gov/resilience-through-responsible-use-pnt"
      }
    ],
    "definition": "An implementation-neutral reference framework for evaluating control, resilience, assurance, source diversity, and integrity across positioning, navigation, and timing dependencies.",
    "deploymentStatus": "active",
    "domainContext": "Sovereign PNT & Resilient Timing is a framework for governing an organization's dependence on positioning, navigation, and precise time. It separates five decisions: continuity through disruption, mission assurance, multi-source fusion, navigation integrity, and use of non-dedicated sources.",
    "id": "https://sovereignpnt.com/#sovereign-pnt",
    "name": "Sovereign PNT & Resilient Timing",
    "namespaceName": "Sovereign PNT",
    "publicationStatus": "published",
    "relationshipContext": "Resilient PNT defines the continuity objective. Assured PNT frames confidence against mission conditions and evidence. PNT Fusion addresses combination of multiple sources or observations. Navigation Integrity addresses whether information and status support continued use. Opportunistic PNT identifies non-dedicated sources that may expand the available source environment. These capabilities interact, but none is a substitute for the others.",
    "role": "canonical-package-namespace",
    "semanticRecord": "https://digitaleasements.com/ontology/v1/concept/sovereign-pnt-resilient-timing",
    "url": "https://sovereignpnt.com/",
    "whyItMatters": "GPS and other PNT services are embedded in critical infrastructure and operational systems, yet their signals and data can be disrupted, degraded, or manipulated. Separating continuity, assurance, fusion, integrity, and alternative-source questions helps buyers define requirements and evidence without assuming that one source or product resolves every dependency."
  },
  "principle": "Publish the map, not the machine.",
  "publicResources": {
    "buyerWalkthrough": "https://sovereignpnt.com/storyboard",
    "llms": "https://sovereignpnt.com/llms.txt",
    "namespaceManifest": "https://sovereignpnt.com/namespace.json",
    "ontology": "https://sovereignpnt.com/ontology.jsonld",
    "overview": "https://sovereignpnt.com/",
    "robots": "https://sovereignpnt.com/robots.txt",
    "sitemap": "https://sovereignpnt.com/sitemap.xml"
  },
  "publisher": {
    "contact": "support@ljpassetgroup.com",
    "id": "https://ljpassetgroup.com/#org",
    "name": "LJP Asset Group LLC",
    "url": "https://ljpassetgroup.com/"
  },
  "supportingNamespaces": [
    {
      "definition": "Infrastructure context for the facilities, services, references, and governance that support navigation.",
      "domain": "navigationinfrastructure.com",
      "id": "https://sovereignpnt.com/#sovereign-pnt/navigation-infrastructure",
      "name": "Navigation Infrastructure",
      "publicationStatus": "reference-only",
      "role": "supporting-namespace"
    },
    {
      "definition": "Focused context for continuity and risk reduction around global navigation satellite system dependence.",
      "domain": "gnssresilience.com",
      "id": "https://sovereignpnt.com/#sovereign-pnt/gnss-resilience",
      "name": "GNSS Resilience",
      "publicationStatus": "reference-only",
      "role": "supporting-namespace"
    },
    {
      "definition": "Context for navigation architectures that may draw from more than one orbital regime.",
      "domain": "multiorbitnavigation.com",
      "id": "https://sovereignpnt.com/#sovereign-pnt/multi-orbit-navigation",
      "name": "Multi-Orbit Navigation",
      "publicationStatus": "reference-only",
      "role": "supporting-namespace"
    },
    {
      "definition": "Aviation-specific context for positioning, navigation, timing, assurance, and continuity.",
      "domain": "aviationpnt.com",
      "id": "https://sovereignpnt.com/#sovereign-pnt/aviation-pnt",
      "name": "Aviation PNT",
      "publicationStatus": "reference-only",
      "role": "supporting-namespace"
    },
    {
      "definition": "Autonomous-system context for dependable positioning, navigation, and timing.",
      "domain": "autonomouspnt.com",
      "id": "https://sovereignpnt.com/#sovereign-pnt/autonomous-pnt",
      "name": "Autonomous PNT",
      "publicationStatus": "reference-only",
      "role": "supporting-namespace"
    }
  ],
  "version": "2.2.1"
}
