{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-RESTIC-RESTORE-IF-CHANGED-ASSUMPTION-01-v1",
  "record_kind": "external_reference",
  "title": "restic restore content shortcuts",
  "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 --overwrite if-changed compare all existing file bytes before deciding they match?",
  "near_questions": [
    "Can restic if-changed skip altered content with unchanged metadata?",
    "Does restic overwrite always check existing file contents?",
    "What happens if an in-place restic restore is interrupted?",
    "Which evidence distinguishes restic metadata matching from byte verification?"
  ],
  "supported_claims": [
    {
      "claim": "The v0.19.1 guide says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Target contents and restoration completeness remain unverified.",
    "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 says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.",
  "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-IF-CHANGED-ASSUMPTION-01-v1",
    "candidate_record_sha256": "66071ab3bc5da1f7906e528b2a9bcd47a9d2ca05a4232420fa24d38a3738d731",
    "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 says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.",
    "required_buyer_context": "Overwrite mode and target file metadata; Content-verification and restore completion results; Pre-restore recovery point and interruption history. 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 --overwrite if-changed compare all existing file bytes before deciding they match?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v0.19.1 guide says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.",
      "source_ids": [
        "restic-restore"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Choose recovery evidence appropriate to metadata shortcuts and interruption risk. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "restic-restore"
      ]
    },
    "buyer_evidence_required": [
      "Overwrite mode and target file metadata",
      "Content-verification and restore completion results",
      "Pre-restore recovery point and interruption history"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse byte-equality assurance based solely on unchanged size and modification time."
    },
    "unknowns": "Target contents and restoration completeness remain unverified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Target contents and restoration completeness remain unverified."
    },
    "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": "Choose recovery evidence appropriate to metadata shortcuts and interruption risk.",
      "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": "Choose recovery evidence appropriate to metadata shortcuts and interruption risk.",
    "refusal_conditions": [
      "Refuse byte-equality assurance based solely on unchanged size and modification time."
    ]
  },
  "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": "Choose recovery evidence appropriate to metadata shortcuts and interruption risk.",
    "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-if-changed-assumption",
  "machine_readable_record": "/varexis-index/records/restic-restore-if-changed-assumption.json"
}