{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T16:34:01.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-CLONE-SHARED-PARTITION-RETENTION-01-v1",
  "record_kind": "external_reference",
  "title": "Snowflake clones and shared partition retention",
  "system": "Snowflake",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a transient clone retain shared Snowflake micro-partitions after its permanent source table is dropped?",
  "near_questions": [
    "Can a Snowflake clone preserve data after the original table is dropped?",
    "Can a transient clone delay shared bytes entering Fail-safe?",
    "Does zero-copy cloning create a separately exported archive?",
    "Why must clone lineage appear in a deletion inventory?"
  ],
  "supported_claims": [
    {
      "claim": "Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Independent archive creation or complete erasure from source-table deletion",
    "Actual partition sharing, surviving clones and byte-level removal are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Working with Temporary and Transient Tables | Snowflake Documentation",
    "source_url": "https://docs.snowflake.com/en/user-guide/tables-temp-transient",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-CLONE-SHARED-PARTITION-RETENTION-01-v1",
    "candidate_record_sha256": "ef63ed0fb5275d3b7c96c83948ff56df3ba53b2d91259f931d0bccd3f50275dc",
    "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": "Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.",
    "required_buyer_context": "Source and clone identities, table types and lineage; Drop events and surviving clone inventory; Retention requirements and storage lifecycle observations. 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": "Can a transient clone retain shared Snowflake micro-partitions after its permanent source table is dropped?",
    "documented_statement": {
      "status": "documented",
      "statement": "Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.",
      "source_ids": [
        "snowflake-tables"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Include surviving clones and shared-storage dependencies when reconciling deletion and retained recovery data.",
      "source_ids": [
        "snowflake-tables"
      ]
    },
    "buyer_evidence_required": [
      "Source and clone identities, table types and lineage",
      "Drop events and surviving clone inventory",
      "Retention requirements and storage lifecycle observations"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject complete data-removal claims that ignore a surviving clone."
    },
    "unknowns": "Actual partition sharing, surviving clones and byte-level removal are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual partition sharing, surviving clones and byte-level removal are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "snowflake-tables",
        "url": "https://docs.snowflake.com/en/user-guide/tables-temp-transient",
        "final_url": "https://docs.snowflake.com/en/user-guide/tables-temp-transient",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:04.670Z",
        "sha256": "263e8804292cbbb15256ed77372661cc25c7f07808af9de9b46c7a8e2fcc78c7",
        "bytes": 150852,
        "title": "Working with Temporary and Transient Tables | Snowflake Documentation",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling official vendor documentation captured on 2026-10-24; account tier, service version, enabled features and buyer configuration require separate verification.",
        "reviewed_sections": [
          "Transient retention and no Fail-safe",
          "Shared clone micro-partitions"
        ]
      }
    ],
    "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": "Find retained data dependencies that a source-table deletion receipt misses.",
      "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 documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Find retained data dependencies that a source-table deletion receipt misses.",
    "refusal_conditions": [
      "Reject complete data-removal claims that ignore a surviving clone."
    ]
  },
  "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": "Find retained data dependencies that a source-table deletion receipt misses.",
    "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#snowflake-clone-shared-partition-retention",
  "machine_readable_record": "/varexis-index/records/snowflake-clone-shared-partition-retention.json"
}
