{
    "name": "Royal Courier Semantic Retrieval Corpus",
    "version": "0.6.1",
    "status": "public-draft",
    "updated": "2026-08-31",
    "canonical": "https://royalcourierinc.com/semantic-retrieval-corpus/",
    "base": "https://royalcourierinc.com/ai-data/",
    "publisher": {
        "name": "Royal Courier Inc.",
        "url": "https://royalcourierinc.com"
    },
    "purpose": "Public machine-readable transportation decision intelligence for retrieval, planning, entity understanding and question answering.",
    "decision_model": [
        "problem",
        "condition",
        "vehicle",
        "equipment",
        "handling",
        "service",
        "scenario",
        "answer_or_recommendation"
    ],
    "retrieval_model": [
        "passage",
        "concept",
        "relationship",
        "scenario",
        "question"
    ],
    "priority_order": [
        "safety",
        "required equipment and physical feasibility",
        "appropriate service type",
        "freight fit/loading/unloading feasibility",
        "damage risk",
        "deadline and customer preferences",
        "cost"
    ],
    "endpoints": [
        {
            "file": "services.json",
            "type": "application/json"
        },
        {
            "file": "vehicles.json",
            "type": "application/json"
        },
        {
            "file": "equipment.json",
            "type": "application/json"
        },
        {
            "file": "conditions.json",
            "type": "application/json"
        },
        {
            "file": "terminology.json",
            "type": "application/json"
        },
        {
            "file": "relationships.json",
            "type": "application/json"
        },
        {
            "file": "questions.jsonl",
            "type": "application/x-ndjson"
        },
        {
            "file": "problems.json",
            "type": "application/json"
        },
        {
            "file": "boundaries.json",
            "type": "application/json"
        },
        {
            "file": "decision-signals.json",
            "type": "application/json"
        },
        {
            "file": "scenarios.jsonl",
            "type": "application/x-ndjson"
        },
        {
            "file": "answer-passages.jsonl",
            "type": "application/x-ndjson"
        },
        {
            "file": "sources.json",
            "type": "application/json"
        }
    ],
    "public_boundary": "The corpus can explain capabilities, identify likely service paths, vehicles, equipment, conditions and handling considerations, flag missing information, estimate planning transit, and describe alternatives. It cannot independently bind pricing, promise availability, accept a shipment, guarantee ETA/deadline, approve hazardous or unsafe handling, make the final safety decision, dispatch a vehicle, expose private customer data, expose live capacity, or expose private dispatch/pricing logic.",
    "canonicality": "RoyalCourierInc.com is authoritative for current Royal Courier public service and corpus information. External repositories or publications are supplementary publication/version layers only.",
    "id": "royal-courier-semantic-retrieval-corpus",
    "entity": "Royal Courier Inc.",
    "canonical_base_url": "https://royalcourierinc.com/ai-data/",
    "documentation_url": "https://royalcourierinc.com/semantic-retrieval-corpus/",
    "company_url": "https://royalcourierinc.com/",
    "supersedes": [
        "0.5.0",
        "0.6.0"
    ],
    "release_note": "Consolidated release preserving v0.6 operational decision intelligence while restoring useful v0.5 terminology aliases, problem patterns, relationship semantics, provenance limitations, custody/authorization signals, and direct retrieval questions.",
    "design_principles": [
        "represent real transportation conditions rather than keyword permutations",
        "separate customer statements from verified conditions where relevant",
        "describe operational relationships without exposing proprietary dispatch or pricing logic",
        "use composable problem, condition, vehicle, equipment, handling, service, scenario, question, and answer concepts",
        "treat customer-requested vehicle or service labels as starting information rather than automatic operating instructions",
        "keep public planning guidance separate from final human acceptance, safety, pricing, availability, and dispatch decisions",
        "keep Royal Courier Inc. and Royal Expediting Inc. legally distinct while using Royal as ordinary customer-facing provider language when entity-specific attribution is unnecessary"
    ],
    "public_scope": [
        "service definitions",
        "general operational conditions",
        "equipment relationships",
        "vehicle relationships",
        "explicit concept relationships",
        "real customer questions",
        "customer problem patterns",
        "public service boundaries",
        "decision signals",
        "generic transportation scenarios",
        "handling considerations",
        "common failure conditions",
        "public-safe recovery scenarios",
        "terminology and aliases",
        "service boundaries",
        "retrieval passages",
        "planning transit heuristics",
        "human-review triggers",
        "source provenance and limitations"
    ],
    "excluded_private_information": [
        "customer identities",
        "customer-specific procedures",
        "pricing formulas",
        "margins",
        "private routing logic",
        "internal dispatch logic",
        "live capacity",
        "confidential shipment information",
        "proprietary exception thresholds",
        "detailed contingency tactics",
        "customer-specific rates or negotiated terms"
    ],
    "provenance": {
        "type": "operator-derived and website-grounded",
        "description": "Records are derived from Royal operating experience, a detailed 2026 operator interview, and Royal public reference infrastructure, then structured into public-safe machine-readable transportation decision intelligence.",
        "limitations": [
            "Operational circumstances vary shipment by shipment.",
            "Examples and planning references are descriptive rather than guarantees of availability, acceptance, price, equipment assignment, or deadline.",
            "Vehicle, liftgate, payload, door, platform, and handling capacities vary by individual equipment and must be confirmed.",
            "Customer-reported weights, dimensions, piece counts, contents, access conditions, and ready times are planning inputs until verified.",
            "Shipment-specific requirements must be confirmed before service.",
            "Private pricing, live capacity, customer data, and proprietary dispatch tactics are intentionally excluded."
        ]
    }
}