{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-7-tranche-57-v1", "route_id": "agentic_reviewed_peppol_mlr_envelope_reference_binding", "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-ENVELOPE-REFERENCE-BINDING-01-v1", "question": "Which identifier binds a Peppol Message Level Response to the business message it assessed?", "answer": "The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-ENVELOPE-REFERENCE-BINDING-01-v1", "url": "/varexis-index/records/peppol-mlr-envelope-reference-binding.json", "content_sha256": "c6d319a6bdaa73df2f0d9479a0ef052f609cfd557290ea883bd9cb0a5d91be84", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T00:16:54.726Z", "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-ENVELOPE-REFERENCE-BINDING-01-v1", "record_kind": "external_reference", "title": "Peppol technical response envelope binding", "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": "Which identifier binds a Peppol Message Level Response to the business message it assessed?", "near_questions": [ "Which ID links a Peppol MLR to its original message?", "Is an invoice number enough to match a technical response?", "Can an MLR cover several business documents?", "How are repeated invoice transmissions distinguished in Peppol responses?" ], "supported_claims": [ { "claim": "The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "The transport envelope and document association 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": "The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.", "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-ENVELOPE-REFERENCE-BINDING-01-v1", "candidate_record_sha256": "33d9b157e45defe206514324743c6d8dbce4fd0f131ec6f6410ecd4334852d9e", "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": "The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.", "required_buyer_context": "Original envelope instance identifier; MLR DocumentReference; Envelope-to-business-document association. 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": "Which identifier binds a Peppol Message Level Response to the business message it assessed?", "documented_statement": { "status": "documented", "statement": "The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.", "source_ids": [ "peppol-mlr" ] }, "review_inference": { "status": "review_inference", "statement": "Prevent a technical response being attributed to the wrong message instance. This is a review judgment, not an observed buyer outcome.", "source_ids": [ "peppol-mlr" ] }, "buyer_evidence_required": [ "Original envelope instance identifier", "MLR DocumentReference", "Envelope-to-business-document association" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse instance-level attribution without the referenced envelope mapping." }, "unknowns": "The transport envelope and document association were not inspected.", "unknown_finding": { "status": "unknown", "statement": "The transport envelope and document association were not inspected." }, "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": "Prevent a technical response being attributed to the wrong message instance.", "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": "Prevent a technical response being attributed to the wrong message instance.", "refusal_conditions": [ "Refuse instance-level attribution without the referenced envelope mapping." ] }, "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": "Prevent a technical response being attributed to the wrong message instance.", "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-envelope-reference-binding", "machine_readable_record": "/varexis-index/records/peppol-mlr-envelope-reference-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": "4a4a9ba466ad0971ab3e15f7ae2bddc95584157aaccaa1eb8520dfc849399dca" }