{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T16:14:30.674Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-APP-REFRESH-INVALIDATES-OLD-TOKEN-PAIR-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub Apps: Refresh invalidates the previous token pair",
  "system": "GitHub Apps",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an agent keep using its old GitHub App user token after refreshing the token pair?",
  "near_questions": [
    "Does GitHub App refresh leave the previous access token valid?",
    "How long can an unused GitHub App refresh token last?",
    "What happens when concurrent workers share an old token pair?",
    "When is user authorization needed again after refresh expiry?"
  ],
  "supported_claims": [
    {
      "claim": "For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Installation-token behavior, credential rotation execution or guaranteed uninterrupted service",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Refreshing user access tokens - GitHub Docs",
    "source_url": "https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/refreshing-user-access-tokens",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-APP-REFRESH-INVALIDATES-OLD-TOKEN-PAIR-01-v1",
    "candidate_record_sha256": "40e21f53dfce577052014e50548873056e3b481bddf7d995020310e3f3f777c9",
    "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": "For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.",
    "required_buyer_context": "Whether expiring user tokens are enabled. Refresh generation and atomic credential update. Worker rollout and reauthorization recovery 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",
    "checked_on": "2026-10-18",
    "claim_to_check": "Can an agent keep using its old GitHub App user token after refreshing the token pair?",
    "documented_statement": {
      "status": "documented",
      "statement": "For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.",
      "source_ids": [
        "github-refresh"
      ]
    },
    "buyer_evidence_required": [
      "Whether expiring user tokens are enabled.",
      "Refresh generation and atomic credential update.",
      "Worker rollout and reauthorization recovery evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not rely on the previous pair remaining usable after a refresh succeeds."
    },
    "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-refresh",
        "url": "https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/refreshing-user-access-tokens",
        "final_url": "https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/refreshing-user-access-tokens",
        "title": "Refreshing user access tokens - GitHub Docs",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T16:08:50.358Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "cbe6978b157b2b2289f05ec928e543b7f6f8875f7fd3f253434fd3cdf46f90a8",
        "bytes": 197041,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Can an agent keep using its old GitHub App user token after refreshing the token pair?"
        ]
      }
    ],
    "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": "Coordinate concurrent agent workers around token rotation and recovery.",
      "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": "Whether expiring user tokens are enabled. Refresh generation and atomic credential update. Worker rollout and reauthorization recovery evidence."
    },
    "buyer_relevance": "Coordinate concurrent agent workers around token rotation and recovery.",
    "refusal_conditions": [
      "Do not rely on the previous pair remaining usable after a refresh succeeds."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "identity",
    "classification_label": "Agent Identity, Credentials & Delegation",
    "topic_id": "identity",
    "buyer_intent": "Coordinate concurrent agent workers around token rotation and recovery.",
    "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#github-app-refresh-invalidates-old-token-pair",
  "machine_readable_record": "/varexis-index/records/github-app-refresh-invalidates-old-token-pair.json"
}
