{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "targeted-tranche-74-v1",
  "route_id": "agentic_reviewed_oauth_exchange_scope_target_product",
  "record_id": "VXI-EXT-TARGETED74-OAUTH-EXCHANGE-SCOPE-TARGET-PRODUCT-01-v1",
  "question": "Does one scope list in a multi-target token exchange assign different scopes to different recipients?",
  "answer": "RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.",
  "records": [
    {
      "record_id": "VXI-EXT-TARGETED74-OAUTH-EXCHANGE-SCOPE-TARGET-PRODUCT-01-v1",
      "url": "/varexis-index/records/oauth-exchange-scope-target-product.json",
      "content_sha256": "2c999ec9c078ea96a87780a91abae1057a435641661268e07e0803951a7f55a6",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-11-05T03:25:13.644334+00:00",
        "record_id": "VXI-EXT-TARGETED74-OAUTH-EXCHANGE-SCOPE-TARGET-PRODUCT-01-v1",
        "record_kind": "external_reference",
        "title": "OAuth evidence — Scope across requested targets",
        "system": "IETF",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does one scope list in a multi-target token exchange assign different scopes to different recipients?",
        "near_questions": [
          "Are exchange scopes paired positionally with audiences?",
          "What rights are requested across multiple exchange targets?",
          "Can broad token exchange fail with invalid_target?",
          "Does requested scope prove the issued token has those rights?"
        ],
        "supported_claims": [
          {
            "claim": "RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
          "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
          "No expanded capabilities or licences for existing INDEX executables."
        ],
        "public_summary": "RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "IETF RFC 8693: OAuth 2.0 Token Exchange",
          "source_url": "https://www.rfc-editor.org/rfc/rfc8693.txt",
          "checked_on": "2026-11-05",
          "candidate_record_id": "VXI-EXT-TARGETED74-OAUTH-EXCHANGE-SCOPE-TARGET-PRODUCT-01-v1",
          "candidate_record_sha256": "8557bf6bb170cdde7ddd6bc3af951ceebd76a6512c861e6eb527efe302ebd536",
          "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 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.",
          "required_buyer_context": "Non-secret issuer, client and resource identity with applicable protocol/profile version; Relevant response fields, observation timestamps and correlation identifiers without credential values; Effective authorization or recovery policy and independent outcome evidence. 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",
          "applicability_status": "RFC 8693, January 2020, token exchange. Review capture 2026-11-05. Buyer deployment not inspected.",
          "checked_on": "2026-11-05",
          "claim_to_check": "Does one scope list in a multi-target token exchange assign different scopes to different recipients?",
          "documented_statement": {
            "status": "documented",
            "statement": "RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.",
            "source_ids": [
              "rfc8693"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access. The RFC 8707 record assesses recipient trust and bearer replay across resources. This RFC 8693 decision instead defines scope-target request semantics and prevents a positional-mapping error before issuance. Operational review inference; no deployment outcome was observed.",
            "source_ids": [
              "rfc8693"
            ]
          },
          "buyer_evidence_required": [
            "Non-secret issuer, client and resource identity with applicable protocol/profile version",
            "Relevant response fields, observation timestamps and correlation identifiers without credential values",
            "Effective authorization or recovery policy and independent outcome evidence"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access."
          },
          "unknowns": "Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "No buyer deployment or transaction was observed."
          },
          "evidence_sources": [
            {
              "source_id": "rfc8693",
              "url": "https://www.rfc-editor.org/rfc/rfc8693.txt",
              "final_url": "https://www.rfc-editor.org/rfc/rfc8693.txt",
              "captured_at_utc": "2026-11-05T03:21:14.536504+00:00",
              "status": 200,
              "content_type": "text/plain;charset=utf-8",
              "bytes": 63031,
              "sha256": "358d658014738bf4dc56c8aae2094ce716ede23b6d5a80488a7dc8e8d72da609",
              "title": "IETF RFC 8693: OAuth 2.0 Token Exchange",
              "publisher": "IETF",
              "checked_on": "2026-11-05",
              "capture_status": "captured_primary_documentation",
              "claim_review_completed": true,
              "hash_basis": "Raw HTTP response bytes retained privately; not deployment attestation.",
              "version_context": "RFC 8693, January 2020, token exchange. Fixed published RFC text; later profiles and deployed conformance require separate review.",
              "rights_disposition": "Original bounded factual paraphrase with IETF attribution. IETF Trust BCP 78 terms and contributor rights remain applicable. Full source capture remains private; no RFC text, code components or modified standard redistributed.",
              "reviewed_sections": [
                "4.1 act Actor Claim",
                "2.2.1 Successful Response",
                "2.1.1 Relationship between Resource Audience and Scope"
              ]
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
          "paid_value": {
            "decision_context": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
            "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
            "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
            "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
            "excluded": [
              "Fresh source research",
              "Native provider integration or schema support",
              "Live inspection or runtime enforcement",
              "Payment settlement or verified deletion",
              "Certification or expanded licences"
            ],
            "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
          },
          "revalidation": {
            "trigger": "Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included.",
            "specific_watch": "2.1.1 Relationship between Resource Audience and Scope"
          },
          "buyer_relevance": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
          "refusal_conditions": [
            "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
            "Do not infer deployment conformance, authority or successful outcomes from source documentation."
          ],
          "decision_context": {
            "operator": "Developer or reviewer assessing agent execution and evidence",
            "scenario": "Does one scope list in a multi-target token exchange assign different scopes to different recipients?",
            "consequence": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
            "confidence": "Primary-documentation support only; buyer demand and deployment outcomes unestablished."
          },
          "novelty_review": {
            "candidate_id": "TARGETED74-05",
            "disposition": "new_distinct",
            "nearest_record_id": "VXI-EXT-PROCUREMENT-RESOURCE-MULTIPLE-TRUST-01-v1",
            "nearest_record_url": "/varexis-index/records/resource-multiple-trust.json",
            "nearest_record_sha256": "f5262128a212acc018b1734dc893c3f9f1c11164db9c4261690cc4ab418d34d8",
            "material_distinction": "The RFC 8707 record assesses recipient trust and bearer replay across resources. This RFC 8693 decision instead defines scope-target request semantics and prevents a positional-mapping error before issuance.",
            "review_status": "Primary-source review and full adjacent-record comparison; no independent challenge claimed."
          },
          "optional_selection": {
            "guide_id": "delegated-agent-identity-continuity",
            "guide_url": "/index-guides/delegated-agent-identity-continuity",
            "guide_manifest": "/varexis-index/decision-guides.json",
            "checker": {
              "product_id": "agent-tool-admission",
              "price_gbp_excluding_vat": 49,
              "purchase_url": "/index-access?route=agentic_pack_tool_admission_v1",
              "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
              "benefit": "Optional local analysis of supported supplied declarations only; no native OAuth validator, credential inspection or provider integration is added."
            },
            "boundary": "This free record supports an evidence-selection decision. The existing checker does not diagnose these platforms, extract their logs or prove the documented condition occurred."
          },
          "exact_access": {
            "endpoint": "/mcp/catalogue",
            "tool": "get_publication_record",
            "arguments": {
              "record_id": "VXI-EXT-TARGETED74-OAUTH-EXCHANGE-SCOPE-TARGET-PRODUCT-01-v1"
            },
            "record_url": "/varexis-index/records/oauth-exchange-scope-target-product.json",
            "original_mcp_search": false,
            "paid_saved_retrieval": false
          }
        },
        "niche": {
          "niche_id": "targeted74-identity",
          "label": "Agent Identity, Credentials & Delegation",
          "classification_id": "identity",
          "classification_label": "Agent Identity, Credentials & Delegation",
          "topic_id": "identity",
          "buyer_intent": "Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.",
          "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#oauth-exchange-scope-target-product",
        "machine_readable_record": "/varexis-index/records/oauth-exchange-scope-target-product.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": "9f911359c27c8cf6bd47d880fd37aafcacb959296473ebb8c36097d515d42c4e"
}
