{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-RESTIC-KEEP-WITHIN-LATEST-ANCHOR-01-v1",
  "record_kind": "external_reference",
  "title": "restic retention window anchor",
  "system": "restic v0.19.1",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Is restic keep-within measured back from the time the retention job runs?",
  "near_questions": [
    "Why does restic keep-within retain an old backup set?",
    "Is the newest restic snapshot the retention-window anchor?",
    "Are future-dated restic snapshots removed by duration policies?",
    "Do restic daily retention counts represent consecutive calendar days?"
  ],
  "supported_claims": [
    {
      "claim": "The v0.19.1 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "The accuracy of snapshot timestamps and buyer policy applicability are unknown.",
    "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 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.",
  "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-KEEP-WITHIN-LATEST-ANCHOR-01-v1",
    "candidate_record_sha256": "07af3bc7f65aad71e7045190ae356a775652601ae1a7d20a25d685f6775519ff",
    "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 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.",
    "required_buyer_context": "Snapshot timestamps and clock context; Exact calendar or duration retention options; Selection output for the retention run. 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": "Is restic keep-within measured back from the time the retention job runs?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v0.19.1 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.",
      "source_ids": [
        "restic-forget"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Interpret a retention window against the documented snapshot-time basis. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "restic-forget"
      ]
    },
    "buyer_evidence_required": [
      "Snapshot timestamps and clock context",
      "Exact calendar or duration retention options",
      "Selection output for the retention run"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a wall-clock expiry conclusion based only on a keep-within duration."
    },
    "unknowns": "The accuracy of snapshot timestamps and buyer policy applicability are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The accuracy of snapshot timestamps and buyer policy applicability are unknown."
    },
    "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": "Interpret a retention window against the documented snapshot-time basis.",
      "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": "Interpret a retention window against the documented snapshot-time basis.",
    "refusal_conditions": [
      "Refuse a wall-clock expiry conclusion based only on a keep-within duration."
    ]
  },
  "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": "Interpret a retention window against the documented snapshot-time basis.",
    "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-keep-within-latest-anchor",
  "machine_readable_record": "/varexis-index/records/restic-keep-within-latest-anchor.json"
}