{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-MPP-PAYMENT-METHOD-SETTLEMENT-SEMANTICS-01-v1",
  "record_kind": "external_reference",
  "title": "MPP method selection and settlement assumptions",
  "system": "Machine Payments Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does switching MPP payment methods preserve the same verification and settlement behavior?",
  "near_questions": [
    "Does the MPP envelope define one settlement procedure for every payment method?",
    "Who defines verification for a selected MPP method?",
    "Do metered sessions settle every request as a separate payment?",
    "Can an agent reuse refund assumptions after switching payment methods?"
  ],
  "supported_claims": [
    {
      "claim": "MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal settlement finality, refund rights or cross-session spending caps",
    "The actual method implementation and any cross-session budget enforcement are not established by the common envelope.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Protocol overview | MPP",
    "source_url": "https://mpp.dev/protocol/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MPP-PAYMENT-METHOD-SETTLEMENT-SEMANTICS-01-v1",
    "candidate_record_sha256": "eb9b0c81cde7fcdf408fb8b81b93379e09f9155f3d2aa9092128a68b10b6defa",
    "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": "MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.",
    "required_buyer_context": "Negotiated payment method, intent and specification version; Method-specific verification and settlement evidence; Applicable recovery, refund and aggregate budget policy. 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-24",
    "claim_to_check": "Does switching MPP payment methods preserve the same verification and settlement behavior?",
    "documented_statement": {
      "status": "documented",
      "statement": "MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.",
      "source_ids": [
        "mpp-protocol",
        "mpp-sessions"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review the selected method and intent before applying previous settlement, recovery or spending assumptions.",
      "source_ids": [
        "mpp-protocol",
        "mpp-sessions"
      ]
    },
    "buyer_evidence_required": [
      "Negotiated payment method, intent and specification version",
      "Method-specific verification and settlement evidence",
      "Applicable recovery, refund and aggregate budget policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not carry settlement, refund or global spending-limit assumptions across methods without supporting evidence."
    },
    "unknowns": "The actual method implementation and any cross-session budget enforcement are not established by the common envelope.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The actual method implementation and any cross-session budget enforcement are not established by the common envelope."
    },
    "evidence_sources": [
      {
        "source_id": "mpp-protocol",
        "url": "https://mpp.dev/protocol/",
        "final_url": "https://mpp.dev/protocol/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:55.047Z",
        "sha256": "d2dec7ff4cb5cb7ce170bde0ab0826ffa15fcc1aa44e821900f5a1aca8196be0",
        "bytes": 259178,
        "title": "Protocol overview | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Challenge/credential/receipt flow",
          "Method-specific verification",
          "Authentication and policy status"
        ]
      },
      {
        "source_id": "mpp-sessions",
        "url": "https://mpp.dev/intents/session",
        "final_url": "https://mpp.dev/intents/session",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:47.115Z",
        "sha256": "3af63e0d0c9ec2d5a118bb584a2b48b12f4f709340198dd56d7a999b4c284fed",
        "bytes": 186245,
        "title": "Session intent for metered payments | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Method-specific sessions and settlement"
        ]
      }
    ],
    "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 unsupported financial assumptions when an agent changes payment rails.",
      "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 documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid unsupported financial assumptions when an agent changes payment rails.",
    "refusal_conditions": [
      "Do not carry settlement, refund or global spending-limit assumptions across methods without supporting evidence."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "payments",
    "classification_label": "Agent Payments, Authority & Transaction Evidence",
    "topic_id": "payments",
    "buyer_intent": "Avoid unsupported financial assumptions when an agent changes payment rails.",
    "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#mpp-payment-method-settlement-semantics",
  "machine_readable_record": "/varexis-index/records/mpp-payment-method-settlement-semantics.json"
}
