{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-RESTIC-FORGET-PRUNE-RESIDUAL-DATA-01-v1",
  "record_kind": "external_reference",
  "title": "restic forgotten snapshots and retained data",
  "system": "restic v0.19.1",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does restic forget immediately remove the backed-up file data from its repository?",
  "near_questions": [
    "Why is data still present after restic forget?",
    "Does restic prune remove data shared by a retained snapshot?",
    "What evidence separates snapshot removal from restic storage reclamation?",
    "Can deleting a restic snapshot prove backup erasure?"
  ],
  "supported_claims": [
    {
      "claim": "In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Underlying media erasure, provider replicas and other repositories are not established.",
    "No independently verified physical deletion, complete recovery, legal compliance or security assurance.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "restic v0.19.1 — 060_forget",
    "source_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/060_forget.rst",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RESTIC-FORGET-PRUNE-RESIDUAL-DATA-01-v1",
    "candidate_record_sha256": "987ab1051ce4dfaa25ee0700fdbd512e2374156776c2a7146de7f5c566119861",
    "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": "In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.",
    "required_buyer_context": "Snapshot IDs removed and snapshots retained; Successful prune evidence and remaining data references; Storage-provider residual-copy and erasure policy. 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-24",
    "claim_to_check": "Does restic forget immediately remove the backed-up file data from its repository?",
    "documented_statement": {
      "status": "documented",
      "statement": "In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.",
      "source_ids": [
        "restic-forget"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Separate logical retention decisions from actual backup-space reclamation. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "restic-forget"
      ]
    },
    "buyer_evidence_required": [
      "Snapshot IDs removed and snapshots retained",
      "Successful prune evidence and remaining data references",
      "Storage-provider residual-copy and erasure policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse physical-deletion evidence based solely on a successful forget operation."
    },
    "unknowns": "Underlying media erasure, provider replicas and other repositories are not established.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Underlying media erasure, provider replicas and other repositories are not established."
    },
    "evidence_sources": [
      {
        "source_id": "restic-forget",
        "url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/060_forget.rst",
        "final_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/060_forget.rst",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:28:59.717Z",
        "sha256": "444be0adec93ad92810a4c6b363d8a5a7b77d84c88879e38408b1a7ea2eff614",
        "bytes": 26823,
        "title": "restic v0.19.1 — 060_forget",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. Repository BSD-2-Clause licence reviewed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Removing snapshots and pruning unused data",
          "Retention policy grouping and filters",
          "Time-based retention and future timestamps",
          "Security considerations in append-only mode"
        ],
        "version_context": "Released restic v0.19.1 (2026-07-05); pinned restic/restic revision 6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf. Source documentation is not independent evidence of buyer deployment behaviour."
      }
    ],
    "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": "Separate logical retention decisions from actual backup-space reclamation.",
      "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 pinned source, deployed version, selection policy and retained operation results before relying on a current outcome."
    },
    "buyer_relevance": "Separate logical retention decisions from actual backup-space reclamation.",
    "refusal_conditions": [
      "Refuse physical-deletion evidence based solely on a successful forget operation."
    ]
  },
  "niche": {
    "niche_id": "enterprise-ai-data-custody-exit-assurance",
    "label": "Enterprise AI Data Custody & Exit Assurance",
    "classification_id": "custody",
    "classification_label": "AI Data Custody, Retention & Exit Assurance",
    "topic_id": "custody",
    "buyer_intent": "Separate logical retention decisions from actual backup-space reclamation.",
    "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#restic-forget-prune-residual-data",
  "machine_readable_record": "/varexis-index/records/restic-forget-prune-residual-data.json"
}