{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T13:19:39.838Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-OIDC-TOKEN-NOT-RESOURCE-GRANT-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub Actions: OIDC token requests and resource authority",
  "system": "GitHub Actions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does id-token: write give a GitHub workflow write permission over cloud resources?",
  "near_questions": [
    "Can the job request an ID token?",
    "Does that grant cloud writes?",
    "Which audience is expected?",
    "What subject was issued?",
    "Which provider trusts it?",
    "What conditions are checked?",
    "Which role is selected?",
    "What resource is targeted?",
    "Where is action permission granted?",
    "Was exchange actually observed?",
    "Is identity being confused with authority?",
    "Can I save the OIDC-grant review?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.",
      "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": "GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub: OpenID Connect reference",
    "source_url": "https://docs.github.com/en/actions/reference/security/oidc",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-OIDC-TOKEN-NOT-RESOURCE-GRANT-01-v1",
    "candidate_record_sha256": "805b52cbefe07495faa0cefd874d3d9807b510b0b6b24f21039f095653741c89",
    "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": "GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.",
    "required_buyer_context": "Workflow token permission, issued claims, provider trust and target resource. 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 id-token: write give a GitHub workflow write permission over cloud resources?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.",
      "source_ids": [
        "github-oidc"
      ]
    },
    "buyer_evidence_required": [
      "Workflow OIDC permission.",
      "Non-secret claim values and provider trust conditions.",
      "Provider role and resource-action permissions."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Separate identity-token issuance from the downstream authority granted after token exchange."
    },
    "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": "github-oidc",
        "url": "https://docs.github.com/en/actions/reference/security/oidc",
        "final_url": "https://docs.github.com/en/actions/reference/security/oidc",
        "title": "GitHub: OpenID Connect reference",
        "checked_on": "2026-10-17",
        "sha256": "026347ecb20916dc350f99a7d4268c2d460381b6100c221ef68e00b093128078",
        "bytes": 565113
      }
    ],
    "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": "Does id-token: write give a GitHub workflow write permission over cloud resources?",
      "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": "Workflow token permission, issued claims, provider trust and target resource."
    }
  },
  "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#github-oidc-token-request-not-cloud-permission",
  "machine_readable_record": "/varexis-index/records/github-oidc-token-request-not-cloud-permission.json"
}
