{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-22T23:52:06.542Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPLOY-KEY-OFFBOARDING-RESIDUAL-ACCESS-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub deploy keys: Member removal leaves repository credentials active",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does removing a GitHub user revoke repository deploy keys that the user created?",
  "near_questions": [
    "Can a GitHub deploy key survive its creator's removal?",
    "Do repository deploy keys expire when a developer leaves?",
    "What separate credential check is needed during GitHub offboarding?",
    "Does deleting a GitHub collaborator remove deployment SSH access?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof that a particular key was copied, used or revoked",
    "Equivalence with GitHub App tokens, personal tokens or SSH agent forwarding",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "GitHub deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Managing deploy keys",
    "source_url": "https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys",
    "checked_on": "2026-10-22",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPLOY-KEY-OFFBOARDING-RESIDUAL-ACCESS-01-v1",
    "candidate_record_sha256": "f7abe13c40890365836d3f68605f38d46bbcb0e61f7368fb21326273e1fa1a1a",
    "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 deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.",
    "required_buyer_context": "Repository deploy-key identifiers and read or write settings; Key custody and systems holding the private credential; Member-removal and separate key-removal 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-22",
    "claim_to_check": "Does removing a GitHub user revoke repository deploy keys that the user created?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.",
      "source_ids": [
        "github-deploy-keys"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Removing membership and removing repository credentials are separate offboarding actions.",
      "source_ids": [
        "github-deploy-keys"
      ]
    },
    "buyer_evidence_required": [
      "Repository deploy-key identifiers and read or write settings",
      "Key custody and systems holding the private credential",
      "Member-removal and separate key-removal evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a complete-offboarding claim based only on membership removal while deploy-key status is unresolved."
    },
    "unknowns": "The buyer key inventory, private-key copies and effective post-offboarding access are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer key inventory, private-key copies and effective post-offboarding access are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "github-deploy-keys",
        "url": "https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys",
        "final_url": "https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys",
        "title": "Managing deploy keys",
        "checked_on": "2026-10-22",
        "captured_at_utc": "2026-10-22T23:48:43.304Z",
        "version_context": "Rolling GitHub.com documentation; repository deploy keys, not GitHub App or personal tokens.",
        "sha256": "0b3b1a6be86efae31444d6b4c624277dbf28afd176a48efc31aebba1b0c8a681",
        "bytes": 212444,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Deploy keys",
          "Cons of deploy keys"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "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": "Close deployment access that can survive an employee or agent-owner offboarding.",
      "free": "Complete review, sources, practical questions 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 the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Close deployment access that can survive an employee or agent-owner offboarding.",
    "refusal_conditions": [
      "Refuse a complete-offboarding claim based only on membership removal while deploy-key status is unresolved."
    ]
  },
  "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": "Close deployment access that can survive an employee or agent-owner offboarding.",
    "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-deploy-key-offboarding-residual-access",
  "machine_readable_record": "/varexis-index/records/github-deploy-key-offboarding-residual-access.json"
}
