{
  "capability": {
    "authorityContext": "DHS defines outcome-based resilience behavior and levels for PNT user equipment, while NIST frames PNT disruption and manipulation within organizational risk management. LJP does not convert those sources into a certification or universal resilience score.",
    "authorityReferences": [
      {
        "applies_to": "resilientpnt.ai",
        "document_id": "Resilient PNT Conformance Framework",
        "id": "dhs-resilient-pnt-framework",
        "organization": "U.S. Department of Homeland Security Science and Technology Directorate",
        "public_authorized": true,
        "relevance": "Provides source-agnostic, outcome-based resilience levels and expected behaviors for PNT user equipment.",
        "scope_note": "The framework applies to its stated user-equipment scope and does not certify the LJP namespace.",
        "title": "Resilient Positioning, Navigation, and Timing Conformance Framework",
        "url": "https://www.dhs.gov/sites/default/files/publications/2020_12_resilient_pnt_conformance_framework.pdf"
      },
      {
        "applies_to": "resilientpnt.ai",
        "document_id": "NIST IR 8323 Revision 1",
        "id": "nist-ir-8323r1-resilience",
        "organization": "National Institute of Standards and Technology",
        "public_authorized": true,
        "publication_context": "Published January 31, 2023",
        "relevance": "Connects identification, protection, detection, response, and recovery activities to organizational PNT risk.",
        "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"
      }
    ],
    "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."
  },
  "credibilityBoundary": "Implementation-neutral public orientation; no certification, endorsement, regulatory determination, or performance guarantee.",
  "editorialModel": "2.2",
  "lastModified": "2026-07-30",
  "manifestType": "ljp.public-capability-namespace",
  "manifestVersion": "1.0",
  "package": {
    "deploymentStatus": "active",
    "id": "https://sovereignpnt.com/#sovereign-pnt",
    "name": "Sovereign PNT & Resilient Timing",
    "namespaceName": "Sovereign PNT",
    "publicationStatus": "published",
    "role": "canonical-package-namespace",
    "url": "https://sovereignpnt.com/"
  },
  "peerCapabilityNamespaces": [
    {
      "name": "Assured PNT",
      "url": "https://assuredpnt.ai/"
    },
    {
      "name": "PNT Fusion",
      "url": "https://pntfusion.com/"
    },
    {
      "name": "Navigation Integrity",
      "url": "https://navigationintegrity.com/"
    },
    {
      "name": "Opportunistic PNT",
      "url": "https://opportunisticpnt.com/"
    }
  ],
  "principle": "Publish the map, not the machine.",
  "publicResources": {
    "llms": "https://resilientpnt.ai/llms.txt",
    "namespaceManifest": "https://resilientpnt.ai/namespace.json",
    "ontology": "https://resilientpnt.ai/ontology.jsonld",
    "overview": "https://resilientpnt.ai/",
    "robots": "https://resilientpnt.ai/robots.txt",
    "sitemap": "https://resilientpnt.ai/sitemap.xml"
  },
  "publisher": {
    "contact": "support@ljpassetgroup.com",
    "id": "https://ljpassetgroup.com/#org",
    "name": "LJP Asset Group LLC",
    "url": "https://ljpassetgroup.com/"
  },
  "version": "2.2.0"
}