{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T09:34:59.110Z",
  "record_id": "VXI-EXT-PROCUREMENT-GMAIL-SCOPE-SEND-01-v1",
  "record_kind": "external_reference",
  "title": "Gmail: Sending does not require full mailbox access",
  "system": "Gmail API",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an agent that only sends Gmail messages need permission to read and delete the mailbox?",
  "near_questions": [
    "Can Gmail send without mailbox read access?",
    "Which scope permits sending only?",
    "Does draft management also allow sending?",
    "Why is full-mailbox scope requested?",
    "Does the task need permanent deletion?",
    "What scopes were actually granted?",
    "Can a send-only token read messages?",
    "Are draft and read requirements separate?",
    "Who approved mailbox disclosure?",
    "What functionality needs broader access?",
    "Is narrower scope sufficient?",
    "Can I save the least-privilege assessment?"
  ],
  "supported_claims": [
    {
      "claim": "Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Gmail: Choose API scopes",
    "source_url": "https://developers.google.com/workspace/gmail/api/auth/scopes",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GMAIL-SCOPE-SEND-01-v1",
    "candidate_record_sha256": "8b9a8db053274d021e53591abbd169e827cef210061dfa81cfc983e349b924ce",
    "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": "Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.",
    "required_buyer_context": "Intended mail operations, granted scopes and disclosure needs. Effective buyer configuration and operational results were 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-17",
    "claim_to_check": "Does an agent that only sends Gmail messages need permission to read and delete the mailbox?",
    "documented_statement": {
      "status": "documented",
      "statement": "Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.",
      "source_ids": [
        "gmail-scope"
      ]
    },
    "buyer_evidence_required": [
      "Operations actually required by the workflow.",
      "Granted token scopes rather than the consent request alone.",
      "Any separate need for reading, drafts or permanent deletion."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Request or use only permissions justified by the authorised communications task."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "gmail-scope",
        "url": "https://developers.google.com/workspace/gmail/api/auth/scopes",
        "final_url": "https://developers.google.com/workspace/gmail/api/auth/scopes",
        "title": "Gmail: Choose API scopes",
        "checked_on": "2026-10-17",
        "sha256": "261153e03029137dc659a216f3a1fb4cd7eafc93dbfded6be580abd9a4b58cf3",
        "bytes": 171585
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Retain the operation-to-scope justification for a communications supplier.",
      "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": "Intended mail operations, granted scopes and disclosure needs."
    }
  },
  "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#gmail-send-scope-versus-mailbox-read",
  "machine_readable_record": "/varexis-index/records/gmail-send-scope-versus-mailbox-read.json"
}
