{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T02:40:06.177Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-REPO-RESTORE-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub repository recovery: Fork networks and permissions matter",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does restoring a deleted GitHub repository restore its original access configuration?",
  "near_questions": [
    "Are team permissions restored with a GitHub repository?",
    "Can a non-empty fork network affect recovery?",
    "Is support recovery available on every plan?",
    "What deletion time determines eligibility?",
    "Can a repository take time to appear as restorable?",
    "Who may restore an organisation repository?",
    "What access settings need re-establishment?",
    "Does recovered content prove workflows are operational?",
    "Which fork relationship should procurement record?",
    "What evidence establishes the restored identity?",
    "When should complete recovery remain qualified?",
    "Can I save a repository recovery review?"
  ],
  "supported_claims": [
    {
      "claim": "The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.",
      "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": "The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-S3-REPLICATION-DELETION-01-v1",
    "VXI-EXT-PROCUREMENT-GCS-SOFTDELETE-01-v1",
    "VXI-EXT-PROCUREMENT-ATLAS-RESTORE-TARGET-01-v1",
    "VXI-EXT-PROCUREMENT-SNOWFLAKE-FAILSAFE-01-v1",
    "VXI-EXT-PROCUREMENT-D1-RESTORE-BOOKMARK-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub deleted repository recovery",
    "source_url": "https://docs.github.com/en/repositories/creating-and-managing-repositories/restoring-a-deleted-repository",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-REPO-RESTORE-01-v1",
    "candidate_record_sha256": "ed68d6e505259d6b2f9893d4706ffc2e35be519d977a8f364e18f213e413c359",
    "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": "The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.",
    "required_buyer_context": "GitHub: Deletion interval, fork network, plan and team permissions; buyer configuration and operational evidence are required.",
    "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-16",
    "claim_to_check": "Repository restoration recreates content and team access exactly as before.",
    "documented_statement": {
      "status": "documented",
      "statement": "The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.",
      "source_ids": [
        "github-restore"
      ]
    },
    "buyer_evidence_required": [
      "Deleted repository identity, timing and fork-network state.",
      "Plan and restoration path eligibility.",
      "Re-established team permissions and dependent workflow checks."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim complete service recovery from repository restoration alone."
    },
    "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-restore",
        "url": "https://docs.github.com/en/repositories/creating-and-managing-repositories/restoring-a-deleted-repository",
        "final_url": "https://docs.github.com/en/repositories/creating-and-managing-repositories/restoring-a-deleted-repository",
        "title": "GitHub deleted repository recovery",
        "checked_on": "2026-10-16",
        "sha256": "a83f9062ccf286cf4e5a9706f64c92492eac6dc60e383fd956890510bc729ef8",
        "bytes": 218465
      }
    ],
    "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 access and eligibility gaps behind a repository-recovery claim.",
      "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": "Deletion interval, fork network, plan and team permissions"
    }
  },
  "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-deleted-repository-restore-scope",
  "machine_readable_record": "/varexis-index/records/github-deleted-repository-restore-scope.json"
}