{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-RESTIC-RANDOM-SUBSET-COVERAGE-01-v1",
  "record_kind": "external_reference",
  "title": "restic sampled integrity coverage",
  "system": "restic v0.19.1",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Do repeated random restic data-subset checks guarantee that every pack has been inspected?",
  "near_questions": [
    "Will ten random ten-percent restic checks cover the whole repository?",
    "How does restic n/t checking differ from percentage sampling?",
    "What evidence supports full restic data-check coverage?",
    "Can repeated successful restic samples leave some packs unread?"
  ],
  "supported_claims": [
    {
      "claim": "The v0.19.1 guide allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual coverage of a changing buyer repository is not known.",
    "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 allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "restic v0.19.1 — 045_working_with_repos",
    "source_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/045_working_with_repos.rst",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RESTIC-RANDOM-SUBSET-COVERAGE-01-v1",
    "candidate_record_sha256": "cfeee916226688de62aebebaf54566b1c38daf3c7725c981d6a1ca41b31c3b95",
    "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 allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.",
    "required_buyer_context": "Subset mode and parameters for each run; Repository pack inventory and changes over the interval; Retained results for required partitions or full-data check. 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": "Do repeated random restic data-subset checks guarantee that every pack has been inspected?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v0.19.1 guide allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.",
      "source_ids": [
        "restic-repository"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Avoid converting successful random samples into an unsupported full-coverage claim. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "restic-repository"
      ]
    },
    "buyer_evidence_required": [
      "Subset mode and parameters for each run",
      "Repository pack inventory and changes over the interval",
      "Retained results for required partitions or full-data check"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse complete inspection coverage from repeated random-sample success alone."
    },
    "unknowns": "Actual coverage of a changing buyer repository is not known.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual coverage of a changing buyer repository is not known."
    },
    "evidence_sources": [
      {
        "source_id": "restic-repository",
        "url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/045_working_with_repos.rst",
        "final_url": "https://raw.githubusercontent.com/restic/restic/6aa3a516ce654808a1f28f9fa21e9b7c8e6e90bf/doc/045_working_with_repos.rst",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:28:59.322Z",
        "sha256": "56bfbe763b9cae005700f9472f73f69acaa28eea07d6fe258471af729ffffcd6",
        "bytes": 28606,
        "title": "restic v0.19.1 — 045_working_with_repos",
        "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": [
          "Checking integrity and consistency",
          "read-data-subset selection"
        ],
        "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": "Avoid converting successful random samples into an unsupported full-coverage claim.",
      "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": "Avoid converting successful random samples into an unsupported full-coverage claim.",
    "refusal_conditions": [
      "Refuse complete inspection coverage from repeated random-sample success alone."
    ]
  },
  "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": "Avoid converting successful random samples into an unsupported full-coverage claim.",
    "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-random-subset-coverage",
  "machine_readable_record": "/varexis-index/records/restic-random-subset-coverage.json"
}