{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-MPP-EXPIRY-AND-METHOD-SPECIFIC-PROOF-VERIFICATION-01-v1",
  "record_kind": "external_reference",
  "title": "MPP expiry and payment-proof verification",
  "system": "Machine Payments Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an MPP server accept a caller payment assertion after the challenge expired merely because it was signed earlier?",
  "near_questions": [
    "Must an MPP server check challenge expiry after a credential is signed?",
    "Can a submitted transaction hash replace payment verification?",
    "Which checks precede accepting an MPP credential?",
    "Does rejecting an expired challenge prove no money moved?"
  ],
  "supported_claims": [
    {
      "claim": "MPP credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A signature timestamp or caller receipt overriding challenge validity",
    "Whether a payment occurred despite rejected access and what recovery applies depend on the payment method and service.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MPP credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Credentials | MPP",
    "source_url": "https://mpp.dev/protocol/credentials",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MPP-EXPIRY-AND-METHOD-SPECIFIC-PROOF-VERIFICATION-01-v1",
    "candidate_record_sha256": "805147daf0869a5698ae0fd854abca0107f58c7d4a28598f2f8f3bfcc725e4f0",
    "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 credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.",
    "required_buyer_context": "Outstanding challenge and verification-time expiry; Method-specific verified proof and expected terms; Replay state and prior processing result. 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": "Can an MPP server accept a caller payment assertion after the challenge expired merely because it was signed earlier?",
    "documented_statement": {
      "status": "documented",
      "statement": "MPP credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.",
      "source_ids": [
        "mpp-credentials",
        "mpp-protocol"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Treat the current challenge validity and verified method outcome as release conditions, independent of the caller assertion.",
      "source_ids": [
        "mpp-credentials",
        "mpp-protocol"
      ]
    },
    "buyer_evidence_required": [
      "Outstanding challenge and verification-time expiry",
      "Method-specific verified proof and expected terms",
      "Replay state and prior processing result"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse delivery from an expired challenge or unverified caller assertion; reconcile any actual payment separately."
    },
    "unknowns": "Whether a payment occurred despite rejected access and what recovery applies depend on the payment method and service.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Whether a payment occurred despite rejected access and what recovery applies depend on the payment method and service."
    },
    "evidence_sources": [
      {
        "source_id": "mpp-credentials",
        "url": "https://mpp.dev/protocol/credentials",
        "final_url": "https://mpp.dev/protocol/credentials",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:47.032Z",
        "sha256": "f14610819c48bd308c745f3496a9cd900b9f7779ee090f86581d5079269bde74",
        "bytes": 211806,
        "title": "Credentials | 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": [
          "Outstanding challenge and expiration verification",
          "Replay prevention",
          "Separate application authorization"
        ]
      },
      {
        "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"
        ]
      }
    ],
    "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": "Keep delivery fail-closed while preserving a path to reconcile uncertain payment.",
      "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": "Keep delivery fail-closed while preserving a path to reconcile uncertain payment.",
    "refusal_conditions": [
      "Refuse delivery from an expired challenge or unverified caller assertion; reconcile any actual payment separately."
    ]
  },
  "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": "Keep delivery fail-closed while preserving a path to reconcile uncertain payment.",
    "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-expiry-and-method-specific-proof-verification",
  "machine_readable_record": "/varexis-index/records/mpp-expiry-and-method-specific-proof-verification.json"
}
