PNT & Timing
Sovereign PNT
Reference material for resilient positioning, navigation, timing, assurance, and continuity questions.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt.
Digital Easements · Reference Map
One map of LJP's published technical references.
Digital Easements is LJP's public index and crosswalk of its published reference assets. Each package stays independently published and canonical. The name is descriptive, not a legal easement.
Use it to find published packages, compare their reference materials, and follow the evidence behind their technical descriptions.
A reference map, not a replacement.
What you can inspect
Published package references, available domain records, source citations, verified machine-readable files, and related public simulations.
Not a service
Digital Easements is not a live operating service or a control plane.
Not an authority
It is not a standards authority or governing body.
Not a property interest
It is not a legal easement and does not replace canonical package websites.
Published package index
Inspect the canonical reference for each package.
This index is generated from the repository-managed public publication catalog. Package sites remain independently published and canonical.
NTN & Space
Unified NTN
Coordinated identity for payload roles, links, coverage geometry, and non-terrestrial architecture.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt.
FR3 Engineering
FR3 Engineering Foundation
Reference material for upper-mid-band propagation, modeling, emulation, and evaluation questions.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt; FR3 Exploration.
Compute Fabric
AI Interconnect & Compute Fabric
Reference identity for connectivity, workload placement, transport, and distributed-compute relationships.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt; Fabric Corridor.
AI Economics
AI Economics Foundation
Reference material separating AI usage, cost allocation, pricing, and commercial-performance questions.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt.
Industrial Policy
Industrial Policy for AI
A viewpoint-neutral reference framework for AI productive capacity and economic-transition questions.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt.
Agent / Capability Systems
End-to-End Intent
An expressed desired outcome whose interpretation, fulfilment, and reporting can span relevant management domains and layers.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt; End-to-End Intent.
6G Sensing / ISAC
6G Sensing Fabric
A public reference spanning semantic identities for sensing participants, arrangements, requirements, capabilities, information, performance, results, and evidence.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt; Sensing Corridor.
Energy & Compute
Grid-to-Inference
A semantic reference for relating grid conditions, advanced-nuclear program context, and compute demand without treating any one layer as operational authority.
Available public evidence: Reference site, namespace.json, ontology.jsonld, llms.txt.
Why this reference structure matters
Built for careful evaluation, not assumed authority.
Verified, not assumed.
Each published reference is checked against its cited sources. Where there is no adopted definition, the page says so rather than implying standards adoption or endorsement.
The research is the asset.
The value is the organized, cross-checked technical vocabulary and evidence behind a name, not a registration alone.
Early, neutral positioning.
Some categories are still forming. A neutral, independently held reference can support discussion without presenting LJP as a standards authority, competing vendor, or representative of a third party.
A durable reference asset.
Unlike a spent campaign, a reference can be developed, licensed, or transferred over time. It gives teams a shared external point of reference when they choose to use one.
A starting point, not finished analysis.
Organized citations can shorten early scoping and research, but they do not replace a buyer's technical, legal, commercial, or standards analysis.
One buyer, one transaction.
Each offered namespace is intended for one acquirer under an agreement that states the included assets and rights.
Limited operational downside.
Acquisition does not require integration, infrastructure change, or an operating dependency; the relevant commitments are defined in the transaction.
Optionality, honestly priced.
Value depends on how a technology and its terminology develop. A reference is an option for a specific category, not a guarantee of adoption, demand, or outcome.
Readable now, legible later.
The material is written for people first and uses clear structure and verified per-package records so automated systems can interpret the published evidence without overstating what is available.
Evidence method
Four plain publication commitments.
Each term states its sources
Where a term is not defined by an adopted standard, its description should make that distinction clear.
Packages remain independent
Each published package retains its own canonical site and reference materials.
Public files support independent review
Technical reviewers can inspect available records and source references.
Transaction scope depends on the agreement
A sale or license may include different assets and rights. The agreement identifies exactly what is included.
Evidence classifications describe individual terms and source relationships, not LJP's commercial credibility or portfolio value.
Technical Resources for Reviewers
Only verified resources are listed.
JSON-LD is linked data expressed as JSON; Turtle is a compact RDF syntax; SKOS is a vocabulary model; PROV-O is a provenance model; and llms.txt is a descriptive text file. Their presence does not guarantee software ingestion or discovery.
Machine-readable resource availability
Machine-readable resources, where published, are maintained by the applicable canonical domain or package site. Available resources may be identified through their direct links in the package index or LJP Library records. Digital Easements does not currently publish separate site-wide Turtle, JSON, JSON-LD, or llms.txt resources. Links to machine-readable resources should be interpreted according to the format and availability of the resource actually returned.
Reviewing a package for your organization?
Email LJP to request a package brief. Packages may be sold or licensed. The agreement states exactly what is included.
Request a Package Brief