{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-7-tranche-57-v1",
  "route_id": "agentic_reviewed_peppol_despatch_multiple_order_binding",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-DESPATCH-MULTIPLE-ORDER-BINDING-01-v1",
  "question": "Can one Peppol Despatch Advice be assumed to belong to a single purchase order?",
  "answer": "A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.",
  "records": [
    {
      "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-DESPATCH-MULTIPLE-ORDER-BINDING-01-v1",
      "url": "/varexis-index/records/peppol-despatch-multiple-order-binding.json",
      "content_sha256": "8d3580365d9883cd1662b1789a3f720a39876560d5f9cbdee797453b77f42370",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-25T00:16:54.726Z",
        "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-DESPATCH-MULTIPLE-ORDER-BINDING-01-v1",
        "record_kind": "external_reference",
        "title": "Peppol despatch across purchase orders",
        "system": "Peppol BIS Despatch Advice 3.1 (November 2025 archive)",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can one Peppol Despatch Advice be assumed to belong to a single purchase order?",
        "near_questions": [
          "Can one Peppol despatch advice cover several orders?",
          "Can a purchase order have multiple shipping notices?",
          "Where are order references in a combined despatch?",
          "How should an agent reconcile consolidated shipments?"
        ],
        "supported_claims": [
          {
            "claim": "A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Actual shipment consolidation and receipt quantities were not verified.",
          "No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.",
          "Applies to the cited published profile; current deployment and release applicability require separate verification.",
          "Buyer deployment testing, live runtime enforcement, certification or permission to act",
          "Expanded capabilities or licences for existing INDEX executables"
        ],
        "public_summary": "A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "BIS Despatch Advice 3.1 — published November 2025 archive",
          "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/30-despatchadvice/",
          "checked_on": "2026-10-25",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-DESPATCH-MULTIPLE-ORDER-BINDING-01-v1",
          "candidate_record_sha256": "560314722fd0cbadb191f6d20cf86953d6ccb0137320039bcb2bd86ee4bf42a3",
          "method": "Primary documentation reviewed for the published bounded statement.",
          "deployment_tested_by_varexis": false,
          "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
        },
        "answer_policy": {
          "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
          "bounded_answer": "A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.",
          "required_buyer_context": "Despatch identifier and lines; Line-level purchase-order references; Other notices for the same order. Buyer deployment not inspected.",
          "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
        },
        "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
        "decision_profile": {
          "schema": "varexis-vendor-evidence-review/1",
          "review_status": "documentation_review_only",
          "checked_on": "2026-10-25",
          "claim_to_check": "Can one Peppol Despatch Advice be assumed to belong to a single purchase order?",
          "documented_statement": {
            "status": "documented",
            "statement": "A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.",
            "source_ids": [
              "peppol-despatch"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Avoid attributing a combined shipment to one order. This is a review judgment, not an observed buyer outcome.",
            "source_ids": [
              "peppol-despatch"
            ]
          },
          "buyer_evidence_required": [
            "Despatch identifier and lines",
            "Line-level purchase-order references",
            "Other notices for the same order"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Refuse a one-message-one-order assumption without checking references."
          },
          "unknowns": "Actual shipment consolidation and receipt quantities were not verified.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "Actual shipment consolidation and receipt quantities were not verified."
          },
          "evidence_sources": [
            {
              "source_id": "peppol-despatch",
              "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/30-despatchadvice/",
              "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/30-despatchadvice/",
              "status": 200,
              "captured_at_utc": "2026-10-24T23:51:30.453Z",
              "sha256": "535f94a8a1388bbfd098d8e7f89160738f230f8ecc3bd6192d8a5e2a42347c49",
              "bytes": 154505,
              "title": "BIS Despatch Advice 3.1 — published November 2025 archive",
              "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
              "rights_review": "Original factual paraphrase only. CEN/OpenPeppol reserve rights in their BIS documents. Raw captures remain private; no document, schema, code or modified standard is redistributed or relicensed.",
              "checked_on": "2026-10-25",
              "capture_status": 200,
              "claim_review_completed": true,
              "reviewed_sections": [
                "2.1",
                "6.2",
                "7.2"
              ],
              "version_context": "Explicit published November 2025 archive. The current root index is labelled DEV 2026-Q2 despite the official listing linking it; archived-profile applicability to a current deployment is not established."
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
          "paid_value": {
            "decision_context": "Avoid attributing a combined shipment to one order.",
            "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
            "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
            "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
            "excluded": [
              "Fresh vendor research",
              "Continuous monitoring or change alerts",
              "Testing the buyer configuration",
              "Private evidence or vendor certification"
            ],
            "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
          },
          "revalidation": {
            "trigger": "A saved purchase does not recheck the source or buyer configuration.",
            "specific_watch": "Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction."
          },
          "buyer_relevance": "Avoid attributing a combined shipment to one order.",
          "refusal_conditions": [
            "Refuse a one-message-one-order assumption without checking references."
          ]
        },
        "niche": {
          "niche_id": "agent-authority-action-evidence",
          "label": "Agent Authority & Action Evidence",
          "classification_id": "audit",
          "classification_label": "Audit, Provenance & Evidence Accountability",
          "topic_id": "audit",
          "buyer_intent": "Avoid attributing a combined shipment to one order.",
          "comparison_role": "supplementary_discovery"
        },
        "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
        "service_route": {
          "request_guide": "/varexis-index/request.html",
          "request_workflow": "/varexis-index/request-workflow.json",
          "service_id": "single_request",
          "service_routes_url": "/varexis-index/service-routes.json",
          "payment_required": true,
          "availability_endpoint": "/api/index/capabilities",
          "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
          "checkout_url": "/index-access"
        },
        "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
        "human_page": "/varexis-index/catalog.html#peppol-despatch-multiple-order-binding",
        "machine_readable_record": "/varexis-index/records/peppol-despatch-multiple-order-binding.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "059047484874ef970c0466d1d3f4ea16bdc38125033fefb745ab602ca5755395"
}