{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-RESTIC-RESTORE-DELETE-FILTER-SCOPE-01-v1",
  "record_kind": "external_reference",
  "title": "restic recovery deletion scope",
  "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 restore --delete remove every extra file from the entire target tree?",
  "near_questions": [
    "Do restic restore filters also limit --delete?",
    "Why can extra files remain after restic restore --delete?",
    "What must be checked before deleting files during restic recovery?",
    "Does filtered restic restore cleanup cover excluded directories?"
  ],
  "supported_claims": [
    {
      "claim": "The v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "No cleanup operation or residual file inventory was examined.",
    "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": "The v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "restic v0.19.1 — 050_restore",
    "source_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/050_restore.rst",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RESTIC-RESTORE-DELETE-FILTER-SCOPE-01-v1",
    "candidate_record_sha256": "e9de7d980e604a0c023cb481536b247aca672162d629709a622a020b9be8be2d",
    "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 v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.",
    "required_buyer_context": "Snapshot and restore target; Include/exclude scope and verbose dry-run listing; Actual deletion results and residual inventory. 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 restore --delete remove every extra file from the entire target tree?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.",
      "source_ids": [
        "restic-restore"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bound destructive recovery cleanup to the authorised target subset. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "restic-restore"
      ]
    },
    "buyer_evidence_required": [
      "Snapshot and restore target",
      "Include/exclude scope and verbose dry-run listing",
      "Actual deletion results and residual inventory"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse whole-tree cleanup from a filtered restore-delete operation."
    },
    "unknowns": "No cleanup operation or residual file inventory was examined.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No cleanup operation or residual file inventory was examined."
    },
    "evidence_sources": [
      {
        "source_id": "restic-restore",
        "url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/050_restore.rst",
        "final_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/050_restore.rst",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:28:59.515Z",
        "sha256": "00d39803cfcb17158c2ee1d835de6351c902e66067d2493438831580e9b04251",
        "bytes": 13902,
        "title": "restic v0.19.1 — 050_restore",
        "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": [
          "Restoring from a snapshot; path selection",
          "Restoring in-place; overwrite modes",
          "Deleting files not in snapshot",
          "Windows restoration privileges"
        ],
        "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": "Bound destructive recovery cleanup to the authorised target subset.",
      "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": "Bound destructive recovery cleanup to the authorised target subset.",
    "refusal_conditions": [
      "Refuse whole-tree cleanup from a filtered restore-delete 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": "Bound destructive recovery cleanup to the authorised target subset.",
    "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-restore-delete-filter-scope",
  "machine_readable_record": "/varexis-index/records/restic-restore-delete-filter-scope.json"
}