{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-VELERO-EXISTING-RESOURCE-UPDATE-VOLUME-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Velero existing resources and volume data",
  "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 existing-resource-policy update restore the data in an existing persistent volume?",
  "near_questions": [
    "Does Velero update an existing PVC data when restoring its spec?",
    "Can a Velero resource patch fail without failing the restore?",
    "Do Velero restore labels prove volume data was recovered?",
    "Which evidence separates Kubernetes resource update from Velero data restoration?"
  ],
  "supported_claims": [
    {
      "claim": "The v1.18.4 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual volume recovery and application consistency 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 v1.18.4 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Velero v1.18.4 — restore-reference",
    "source_url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/restore-reference.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-VELERO-EXISTING-RESOURCE-UPDATE-VOLUME-BOUNDARY-01-v1",
    "candidate_record_sha256": "ce9be4a4cfdee36f68dbc791b1f3b690d4225fe9051b8c95723c9932be5ebc7e",
    "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 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.",
    "required_buyer_context": "Restore policy and existing PVC/PV inventory; Patch warnings and per-resource outcomes; Volume restore mechanism and content 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 existing-resource-policy update restore the data in an existing persistent volume?",
    "documented_statement": {
      "status": "documented",
      "statement": "The v1.18.4 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.",
      "source_ids": [
        "velero-restore-reference"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Separate resource-definition reconciliation from volume-content recovery. The required reconciliation is a review judgment; no buyer deployment was inspected.",
      "source_ids": [
        "velero-restore-reference"
      ]
    },
    "buyer_evidence_required": [
      "Restore policy and existing PVC/PV inventory",
      "Patch warnings and per-resource outcomes",
      "Volume restore mechanism and content validation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse volume-recovery approval from resource update or restore labels alone."
    },
    "unknowns": "Actual volume recovery and application consistency are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual volume recovery and application consistency are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "velero-restore-reference",
        "url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/restore-reference.md",
        "final_url": "https://raw.githubusercontent.com/vmware-tanzu/velero/4ee1e79a7aed367fd9b767b8219ec65bd0c96892/site/content/docs/main/restore-reference.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:29:02.915Z",
        "sha256": "7bbcc5a34916d2911b558531ec8dbf91f7c407594a060598f0f38f298c204bc6",
        "bytes": 26951,
        "title": "Velero v1.18.4 — restore-reference",
        "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": [
          "Restore existing resource policy",
          "ServiceAccount exception to default restore policy",
          "Restore status field of objects"
        ],
        "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": "Separate resource-definition reconciliation from volume-content 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": "Separate resource-definition reconciliation from volume-content recovery.",
    "refusal_conditions": [
      "Refuse volume-recovery approval from resource update or restore labels 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": "Separate resource-definition reconciliation from volume-content 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-existing-resource-update-volume-boundary",
  "machine_readable_record": "/varexis-index/records/velero-existing-resource-update-volume-boundary.json"
}