Foundational PNT Profile
NIST — component or architectural context.
Definition
A bounded technical identity.
Resilient timing combines diverse time sources, monitoring, holdover, distribution, and recovery practices to reduce dependence on any single timing path.
Why it matters
Make the technical question explicit.
A timing architecture may need to continue operating through GNSS loss, network faults, source compromise, or local equipment failure without hiding degraded confidence.
Technical context
PNT / timing / resilience
This page provides a stable descriptive reference for the stated concept. Implementations, products, operating models, and applicable requirements remain context-specific and replaceable.
Evidence and terminology boundary
Evidence class C.
The cited authority supports component concepts or architectural context. It does not define this exact compound identity; LJP uses the phrase descriptively.
Machine-readable resources
Public identity resources
Namespace manifest · LLM summary · Robots policy · Sitemap
No ontology, API, agent card, MCP endpoint, or executable service is published. JSON-LD describes this page; it is not a formal vocabulary.
Credibility boundary
What this page does not claim.
The domain does not distribute time, provide holdover, or guarantee continuity during an outage.
This identity is not an agent, workload, sensor, control plane, runtime, operating platform, database, network, or standards authority. It is not an endorsement, certification, or conformance claim.
Library context
Portfolio discovery record
View the Library record. Licensing, stewardship, partnership or acquisition discussions welcome.