{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T19:34:16.969Z",
  "record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-R2-LIFECYCLE-EXPIRATION-OBSERVED-DELETION-01-v1",
  "record_kind": "external_reference",
  "title": "Cloudflare R2: Lifecycle expiry and observed removal differ",
  "system": "Cloudflare R2",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an R2 lifecycle rule prove that all targeted objects were deleted immediately?",
  "near_questions": [
    "Does an R2 x-amz-expiration timestamp prove the object is gone?",
    "How quickly do changed R2 lifecycle rules affect existing objects?",
    "Can an R2 bucket temporarily show the previous lifecycle rule?",
    "Are unfinished multipart uploads covered by the same object expiry evidence?"
  ],
  "supported_claims": [
    {
      "claim": "Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Guaranteed exact deletion time, physical erasure or removal from all copies",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Object lifecycles · Cloudflare R2 docs",
    "source_url": "https://developers.cloudflare.com/r2/buckets/object-lifecycles/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-R2-LIFECYCLE-EXPIRATION-OBSERVED-DELETION-01-v1",
    "candidate_record_sha256": "20e678e53964f8968f4b25a1b444fd205e6262a7c5b26aae486bc6480a15c24f",
    "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": "Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.",
    "required_buyer_context": "Bucket, rule filters, enabled actions and change timestamps. Matching object inventory, expiry metadata and later retrieval/listing outcomes. Separate multipart-upload inventory and other copies or retention constraints. 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-18",
    "claim_to_check": "Does an R2 lifecycle rule prove that all targeted objects were deleted immediately?",
    "documented_statement": {
      "status": "documented",
      "statement": "Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.",
      "source_ids": [
        "r2-lifecycle"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A rule or elapsed expiry timestamp does not establish completed deletion of the intended inventory.",
      "source_ids": [
        "r2-lifecycle"
      ]
    },
    "buyer_evidence_required": [
      "Bucket, rule filters, enabled actions and change timestamps.",
      "Matching object inventory, expiry metadata and later retrieval/listing outcomes.",
      "Separate multipart-upload inventory and other copies or retention constraints."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse immediate or complete deletion claims based solely on configured lifecycle rules."
    },
    "unknowns": "Actual object absence, inventory completeness and external copies are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual object absence, inventory completeness and external copies are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "r2-lifecycle",
        "url": "https://developers.cloudflare.com/r2/buckets/object-lifecycles/",
        "final_url": "https://developers.cloudflare.com/r2/buckets/object-lifecycles/",
        "title": "Object lifecycles · Cloudflare R2 docs",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T19:20:56.353Z",
        "version_context": "Rolling official documentation captured 2026-10-18; exact response hash retained, no pinned release implied.",
        "sha256": "130c4efd86551aefa39af835e50b69039e81f2d3c2507f8d9f997000caa9e172",
        "bytes": 144032,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Behavior"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.",
    "paid_value": {
      "decision_context": "Identify residual resources before closing a data-retention or exit decision.",
      "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 rule filters, existing-object migration and actual state after changes."
    },
    "buyer_relevance": "Identify residual resources before closing a data-retention or exit decision.",
    "refusal_conditions": [
      "Refuse immediate or complete deletion claims based solely on configured lifecycle rules."
    ]
  },
  "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": "Identify residual resources before closing a data-retention or exit decision.",
    "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#cloudflare-r2-lifecycle-expiration-observed-deletion",
  "machine_readable_record": "/varexis-index/records/cloudflare-r2-lifecycle-expiration-observed-deletion.json"
}
