{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-VELERO-FILESYSTEM-BACKUP-NONATOMIC-01-v1",
  "record_kind": "external_reference",
  "title": "Velero live-filesystem consistency",
  "system": "Velero v1.18.4",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Velero File System Backup capture all files at a single atomic point in time?",
  "near_questions": [
    "Is Velero File System Backup a single point-in-time snapshot?",
    "Can files change while Velero FSB reads them?",
    "What consistency evidence is needed for a Velero filesystem recovery?",
    "Does a successful Velero FSB transfer prove database recoverability?"
  ],
  "supported_claims": [
    {
      "claim": "The v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Application consistency and recoverability were not tested.",
    "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 v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Velero v1.18.4 — file-system-backup",
    "source_url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/file-system-backup.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-VELERO-FILESYSTEM-BACKUP-NONATOMIC-01-v1",
    "candidate_record_sha256": "f4f3c9e9227c10a8ef6b4193fdc1265dce7e7c5718fc186278d31e7967a63150",
    "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 v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.",
    "required_buyer_context": "Application write and quiescence conditions; Volume backup method and per-volume results; Application-level recovery validation. 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 Velero File System Backup capture all files at a single atomic point in time?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.",
      "source_ids": [
        "velero-file-system-backup"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Determine whether a backup is coherent enough for the intended application recovery. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "velero-file-system-backup"
      ]
    },
    "buyer_evidence_required": [
      "Application write and quiescence conditions",
      "Volume backup method and per-volume results",
      "Application-level recovery validation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse an atomic or application-consistent snapshot claim from File System Backup success alone."
    },
    "unknowns": "Application consistency and recoverability were not tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Application consistency and recoverability were not tested."
    },
    "evidence_sources": [
      {
        "source_id": "velero-file-system-backup",
        "url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/file-system-backup.md",
        "final_url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/file-system-backup.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:29:01.991Z",
        "sha256": "eac7a7da06432d8c97e6eea957d4892e29be3d479fa6100128dea518ef1c08d0",
        "bytes": 40736,
        "title": "Velero v1.18.4 — file-system-backup",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. Repository Apache-2.0 licence reviewed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "File System Backup; pros and cons",
          "Relationship with Volume Snapshots",
          "Repository credentials before first backup"
        ],
        "version_context": "Released Velero v1.18.4 (2026-09-28); pinned vmware-tanzu/velero revision 4ee1e79a7aed367fd9b767b8219ec65bd0c96892. 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": "Determine whether a backup is coherent enough for the intended application recovery.",
      "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": "Determine whether a backup is coherent enough for the intended application recovery.",
    "refusal_conditions": [
      "Refuse an atomic or application-consistent snapshot claim from File System Backup 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": "Determine whether a backup is coherent enough for the intended application recovery.",
    "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#velero-filesystem-backup-nonatomic",
  "machine_readable_record": "/varexis-index/records/velero-filesystem-backup-nonatomic.json"
}