A public, retrieval-ready collection of logistics service definitions, operating conditions, vehicle and equipment relationships, delivery scenarios, answer passages, and provenance maintained by Royal Courier Inc.
The corpus converts real transportation operating knowledge into structured, reusable semantic units designed to make logistics concepts easier for people, search systems, AI systems, and technical researchers to retrieve and interpret.
Transportation decisions rarely depend on one keyword or one service label. A pallet delivery may depend on freight dimensions, weight, loading method, dock access, liftgate capacity, pallet-jack compatibility, surface conditions, site restrictions, available labor, and the final placement requirement.
Represent the actual factors that affect transportation planning, including freight, vehicle, equipment, site access, handling, timing, and loading or unloading conditions.
Break complex delivery situations into reusable service, equipment, vehicle, condition, scenario, and boundary concepts rather than creating thousands of keyword variations.
Connect concepts such as no-dock delivery, liftgate service, pallet-jack use, straight trucks, inside delivery, manpower, and surface requirements.
Publish concise retrieval passages and scenarios that explain how transportation conditions interact when customers or AI systems ask complex logistics questions.
Identify the source and limitations of operator-derived information rather than presenting every statement as an unconditional transportation rule.
Publish what helps people understand Royal Courier's services while keeping proprietary pricing, dispatch logic, customer information, routing logic, and other private operating intelligence outside the public corpus.
The corpus is intentionally compositional. Instead of producing a thin page for every possible phrase or location combination, Royal publishes reusable semantic components that can be combined to describe real transportation situations.
Each endpoint represents a distinct semantic layer, including explicit relationships, real customer questions, problem patterns, service boundaries, and decision signals. JSON endpoints contain structured collections. JSONL endpoints contain independent line-delimited records designed for machine processing and retrieval.
Corpus identity, version, scope, design principles, public/private boundary, endpoint inventory, and provenance.
/ai-data/corpus-manifest.json
Open endpoint →
Structured definitions, characteristics, boundaries, and decision factors for Royal Courier service concepts.
/ai-data/services.json
Open endpoint →
Public vehicle categories, approximate capabilities, selection factors, access considerations, and operating relationships.
/ai-data/vehicles.json
Open endpoint →
Liftgates, pallet jacks, dollies, securement equipment, additional labor relationships, capacities, and boundaries.
/ai-data/equipment.json
Open endpoint →
Operational conditions such as no-dock access, pallet-jack compatibility, surfaces, information confidence, appointments, and wait-time factors.
/ai-data/conditions.json
Open endpoint →
Canonical logistics terms, aliases, related language, and distinctions used across Royal Courier's public semantic corpus.
/ai-data/terminology.json
Open endpoint →
Explicit public-safe connections between service, condition, vehicle, equipment, terminology, scenario, and answer concepts.
/ai-data/relationships.json
Open endpoint →
Real customer and agent-facing questions mapped to Royal concepts, answer rules, and escalation boundaries.
/ai-data/questions.jsonl
Open endpoint →
Common transportation problems such as missed pickups, production-down parts, inventory shortages, failed-carrier recovery, high-rise delivery, and urgent special conditions.
/ai-data/problems.json
Open endpoint →
Public safety, privacy, acceptance, custody, restricted-freight, entity-separation, and human-confirmation boundaries.
/ai-data/boundaries.json
Open endpoint →
Signals for likely service fit, urgency, verification, vehicle choice, equipment, labor, facility complexity, recovery, and geography.
/ai-data/decision-signals.json
Open endpoint →
Reusable transportation situations such as pallet delivery without a dock, liftgate assist, freight restacking, and packaging problems at pickup.
/ai-data/scenarios.jsonl
Open endpoint →
Standalone explanations structured to answer transportation questions while preserving operational context and boundaries.
/ai-data/answer-passages.jsonl
Open endpoint →
Source classification, provenance statements, known limitations, and information about how the public corpus was derived.
/ai-data/sources.json
Open endpoint →
The initial corpus is based on operating knowledge developed through Royal Courier's transportation work. Records describe factors that may affect vehicle selection, freight handling, site access, liftgate use, pallet-jack movement, cargo recovery, and delivery-problem resolution.
The corpus is intentionally a public knowledge layer. It explains transportation concepts and relationships without publishing proprietary information Royal uses to operate, price, route, or manage individual customer shipments.
Transportation circumstances vary from shipment to shipment. Corpus records describe concepts, conditions, and possible relationships. They do not replace shipment-specific review.
Corpus records do not establish pricing or constitute a transportation quote.
A listed vehicle, service, relationship, or capability does not represent real-time equipment or driver availability.
Specific shipments remain subject to freight, site, timing, handling, equipment, safety, and service review.
Individual vehicle dimensions, payloads, liftgate sizes, and equipment capacities can vary and should be confirmed for the shipment.
Weight, dimensions, stability, surface, access, equipment, weather, manpower, and other conditions may change the appropriate solution.
The corpus is expected to expand as additional public-safe transportation knowledge is structured and reviewed.
The Semantic Retrieval Corpus complements Royal Courier's existing service taxonomy, service graph, methodology, scenario library, reference hub, machine-readable service manifest, and technical publishing resources.
Canonical source:
RoyalCourierInc.com is the authoritative source for the Royal Courier
Semantic Retrieval Corpus and its public machine-readable endpoints.
Corpus version: 0.6.1 · consolidated operational decision intelligence.
Royal Courier publishes a public Semantic Retrieval Corpus that connects transportation problems, conditions, freight characteristics, vehicles, equipment, handling requirements, service types, scenarios, customer questions, answer passages, service boundaries, and source provenance.
The corpus is designed to help search engines, AI systems, software agents, researchers, and customers understand why a transportation condition can change the appropriate vehicle, equipment, handling method, timing, or service path.
Decision model: problem → condition → vehicle → equipment → handling → service → scenario → answer/recommendation.
Public boundary: these resources can identify likely fit, possible fit, missing information, likely vehicles/equipment, handling factors and planning considerations. They do not independently bind pricing, promise availability, accept a shipment, guarantee an ETA/deadline, approve hazardous or unsafe handling, make the final safety decision, or dispatch a vehicle. Shipment-specific confirmation remains required.
Start with: Semantic Retrieval Corpus documentation · Corpus Manifest JSON
Because Your Most Important Shipments Deserve a Trusted Carrier.