{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:16:54.726Z",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-AB-VALIDATION-STATE-01-v1",
  "record_kind": "external_reference",
  "title": "Peppol receipt without validation",
  "system": "Peppol BIS Message Level Response 3.0 (November 2025 archive)",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an AB Message Level Response establish that Peppol conformance validation ran?",
  "near_questions": [
    "Does Peppol MLR AB mean validation passed?",
    "How do AB and AP differ in a technical response?",
    "What explanation accompanies a Peppol MLR rejection?",
    "Can acknowledged Peppol documents still be unvalidated?"
  ],
  "supported_claims": [
    {
      "claim": "In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Whether the recipient ran a validator is unobserved.",
    "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": "In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BIS Message Level Response 3.0 — published November 2025 archive",
    "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-AB-VALIDATION-STATE-01-v1",
    "candidate_record_sha256": "ddcf90224055888f62c5db92552fecd3167dd61acd41eb613aaa6ea7c81ff094",
    "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": "In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.",
    "required_buyer_context": "Response code; Referenced envelope; Validation outcome and rejection description. 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": "Does an AB Message Level Response establish that Peppol conformance validation ran?",
    "documented_statement": {
      "status": "documented",
      "statement": "In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.",
      "source_ids": [
        "peppol-mlr"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Separate successful receipt from completed document validation. This is a review judgment, not an observed buyer outcome.",
      "source_ids": [
        "peppol-mlr"
      ]
    },
    "buyer_evidence_required": [
      "Response code",
      "Referenced envelope",
      "Validation outcome and rejection description"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a passed-validation conclusion from AB alone."
    },
    "unknowns": "Whether the recipient ran a validator is unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Whether the recipient ran a validator is unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "peppol-mlr",
        "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/",
        "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:51:30.448Z",
        "sha256": "e9ed0f5509414c85119a6b09b0e927ed2a979a7bac29584a74b231e832399e57",
        "bytes": 100435,
        "title": "BIS Message Level Response 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–2.2",
          "6.2",
          "6.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": "Separate successful receipt from completed document validation.",
      "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": "Separate successful receipt from completed document validation.",
    "refusal_conditions": [
      "Refuse a passed-validation conclusion from AB 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": "Separate successful receipt from completed document validation.",
    "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-mlr-ab-validation-state",
  "machine_readable_record": "/varexis-index/records/peppol-mlr-ab-validation-state.json"
}