{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:16:54.726Z",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-ORDER-CHANGE-SEQUENCE-REFERENCE-01-v1",
  "record_kind": "external_reference",
  "title": "Peppol successive order-change reconciliation",
  "system": "Peppol BIS Advanced Ordering 3.0 (November 2025 archive)",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "How are successive Peppol Order Change messages distinguished during reconciliation?",
  "near_questions": [
    "How are successive Peppol amendments numbered?",
    "Where does an order response reference its change document?",
    "Does an OrderChangeSequenceNumber prove approval?",
    "How can an agent match a response to the correct amendment?"
  ],
  "supported_claims": [
    {
      "claim": "Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual change ordering and recipient decisions were not inspected.",
    "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": "Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BIS Advanced Ordering 3.0 — published November 2025 archive",
    "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-ORDER-CHANGE-SEQUENCE-REFERENCE-01-v1",
    "candidate_record_sha256": "7ee041b3680e2d330dd1766bd4eef10d872452d07db90f8cb4194165d337ce62",
    "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": "Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.",
    "required_buyer_context": "Order Change document and sequence; Original order identity; Response change-document reference. 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": "How are successive Peppol Order Change messages distinguished during reconciliation?",
    "documented_statement": {
      "status": "documented",
      "statement": "Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.",
      "source_ids": [
        "peppol-advanced"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconstruct which amendment received which decision. This is a review judgment, not an observed buyer outcome.",
      "source_ids": [
        "peppol-advanced"
      ]
    },
    "buyer_evidence_required": [
      "Order Change document and sequence",
      "Original order identity",
      "Response change-document reference"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse accepted-amendment conclusions from sequence numbering alone."
    },
    "unknowns": "Actual change ordering and recipient decisions were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual change ordering and recipient decisions were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "peppol-advanced",
        "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
        "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:51:30.432Z",
        "sha256": "b435d44433c8b281dfd2d5749b6803ee88d3ada84f2dfbfd03654239aecdc0bf",
        "bytes": 198468,
        "title": "BIS Advanced Ordering 3.0 — 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",
          "8.1 and 7.3"
        ],
        "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": "Reconstruct which amendment received which decision.",
      "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": "Reconstruct which amendment received which decision.",
    "refusal_conditions": [
      "Refuse accepted-amendment conclusions from sequence numbering alone."
    ]
  },
  "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": "Reconstruct which amendment received which decision.",
    "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-order-change-sequence-reference",
  "machine_readable_record": "/varexis-index/records/peppol-order-change-sequence-reference.json"
}