{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-9-tranche-59-v1", "route_id": "agentic_reviewed_rar_returned_grant", "record_id": "VXI-EXT-PROCUREMENT-RAR-RETURNED-GRANT-01-v1", "question": "Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?", "answer": "RFC 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-RAR-RETURNED-GRANT-01-v1", "url": "/varexis-index/records/rar-returned-grant.json", "content_sha256": "fa6a619b28d92a2262310e39192aeb4d13d975a747d3f0294820de0de09022e9", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T20:55:19.974986+00:00", "record_id": "VXI-EXT-PROCUREMENT-RAR-RETURNED-GRANT-01-v1", "record_kind": "external_reference", "title": "OAuth RAR requested terms and returned grant", "system": "IETF RFC 9396", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?", "near_questions": [ "Does requesting a RAR payment authorize that amount?", "Which authorization_details describe the issued access token?", "Can consent reduce requested OAuth RAR permissions?", "May returned RAR details contain additional information?" ], "supported_claims": [ { "claim": "RFC 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Compare the actual token grant with the intended transaction using the applicable RAR type. The server may omit values; the fictitious payment example is not a universal payment schema or settlement proof.", "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 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "IETF RFC 9396", "source_url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "checked_on": "2026-10-25", "candidate_record_id": "VXI-EXT-PROCUREMENT-RAR-RETURNED-GRANT-01-v1", "candidate_record_sha256": "902e13b9fffc561d8312845527a1924ee9aa75ecaf4c4216aae06fc661bddc67", "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 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.", "required_buyer_context": "Requested and returned authorization_details; Applicable RAR type semantics; Actual token grant and intended transaction. 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": "Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?", "documented_statement": { "status": "documented", "statement": "RFC 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.", "source_ids": [ "rfc9396" ] }, "review_inference": { "status": "review_inference", "statement": "Compare the returned authorization details with the requested transaction before using the token. This is a documentation-review judgment, not an observed deployment outcome.", "source_ids": [ "rfc9396" ] }, "buyer_evidence_required": [ "Requested and returned authorization_details", "Applicable RAR type semantics", "Actual token grant and intended transaction" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse buyer-specific assurance from documentation alone. Compare the actual token grant with the intended transaction using the applicable RAR type. The server may omit values; the fictitious payment example is not a universal payment schema or settlement proof." }, "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": "rfc9396", "url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "final_url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "status": 200, "captured_at_utc": "2026-10-25T20:04:28.371Z", "sha256": "d6a8f032d8a585daae1c33a8c7b6e539d199f886ec8cc1c7898436f7f2eed29c", "bytes": 65926, "title": "IETF RFC 9396", "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": [ "Sections 3, 7 and 7.1", "Section 2.2", "Section 6.1", "Section 3.1", "Section 3.2", "Section 5", "Section 12" ], "version_context": "Fixed IETF RFC 9396 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": "Compare the returned authorization details with the requested transaction before using the token.", "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 Sections 3, 7 and 7.1 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval." }, "buyer_relevance": "Compare the returned authorization details with the requested transaction before using the token.", "refusal_conditions": [ "Refuse buyer-specific assurance from documentation alone. Compare the actual token grant with the intended transaction using the applicable RAR type. The server may omit values; the fictitious payment example is not a universal payment schema or settlement proof." ] }, "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": "Compare the returned authorization details with the requested transaction before using the token.", "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#rar-returned-grant", "machine_readable_record": "/varexis-index/records/rar-returned-grant.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": "a7bb67ed63f58948f05546a054b0e4e5b9f01a8b8073ac8072dae3b987adbe83" }