{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T20:55:19.974986+00:00",
  "record_id": "VXI-EXT-PROCUREMENT-RESOURCE-MULTIPLE-TRUST-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth multiple-resource token issuance trust",
  "system": "IETF RFC 8707",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Is a multi-audience OAuth bearer token isolated from replay between its accepted recipients?",
  "near_questions": [
    "Should one OAuth bearer token target several unrelated APIs?",
    "Can one resource replay a multi-audience bearer token elsewhere?",
    "May the authorization server reject a multi-resource token request?",
    "Which trust assumption changes when OAuth resources share a token?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Retain only with the RFC8707 multi-resource issuance decision and its single-resource recommendation explicit. Do not claim this is a novel replay principle or extend it to sender-constrained tokens.",
    "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "IETF RFC 8707",
    "source_url": "https://www.rfc-editor.org/rfc/rfc8707.txt",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RESOURCE-MULTIPLE-TRUST-01-v1",
    "candidate_record_sha256": "53b850b0d673e30a8a9f68cdcbe3590db30a1bb9c4b00f29f4b22b7a76cd5540",
    "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": "RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.",
    "required_buyer_context": "Requested resource set; Recipient trust relationships; Actual audience and issuance 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-25",
    "claim_to_check": "Is a multi-audience OAuth bearer token isolated from replay between its accepted recipients?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.",
      "source_ids": [
        "rfc8707"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Assess mutual trust before issuing one bearer token to multiple recipients. This is a documentation-review judgment, not an observed deployment outcome.",
      "source_ids": [
        "rfc8707"
      ]
    },
    "buyer_evidence_required": [
      "Requested resource set",
      "Recipient trust relationships",
      "Actual audience and issuance policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse buyer-specific assurance from documentation alone. Retain only with the RFC8707 multi-resource issuance decision and its single-resource recommendation explicit. Do not claim this is a novel replay principle or extend it to sender-constrained tokens."
    },
    "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "rfc8707",
        "url": "https://www.rfc-editor.org/rfc/rfc8707.txt",
        "final_url": "https://www.rfc-editor.org/rfc/rfc8707.txt",
        "status": 200,
        "captured_at_utc": "2026-10-25T20:04:28.365Z",
        "sha256": "3b89844a938b9219571931b664ed4a7b380555a4dda1df4e9445a2f72188e76b",
        "bytes": 25698,
        "title": "IETF RFC 8707",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original factual paraphrase of the cited IETF RFC; IETF Trust and contributor rights remain applicable. No RFC text, code component or modified standard is redistributed.",
        "checked_on": "2026-10-25",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Section 2",
          "Section 2.1",
          "Section 2.2",
          "Section 3"
        ],
        "version_context": "Fixed IETF RFC 8707 publication; later applicable updates and actual implementation conformance require separate review."
      }
    ],
    "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": "Assess mutual trust before issuing one bearer token to multiple recipients.",
      "free": "Complete review, practical questions, sources 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 Section 3 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval."
    },
    "buyer_relevance": "Assess mutual trust before issuing one bearer token to multiple recipients.",
    "refusal_conditions": [
      "Refuse buyer-specific assurance from documentation alone. Retain only with the RFC8707 multi-resource issuance decision and its single-resource recommendation explicit. Do not claim this is a novel replay principle or extend it to sender-constrained tokens."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Assess mutual trust before issuing one bearer token to multiple recipients.",
    "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#resource-multiple-trust",
  "machine_readable_record": "/varexis-index/records/resource-multiple-trust.json"
}