{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-CORTEX-PROCESSING-STORAGE-REGION-01-v1",
  "record_kind": "external_reference",
  "title": "Snowflake Cortex: Processing and storage geography differ",
  "system": "Snowflake Cortex",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Snowflake account storage residency prove Cortex inference stays in the same region?",
  "near_questions": [
    "Can Cortex process prompts outside the warehouse region?",
    "Which setting controls Snowflake cross-region inference?",
    "Does no remote persistence mean no cross-region transfer?",
    "What geography does ANY_REGION permit for inference?",
    "How do we review the account processing boundary?",
    "Can storage residency alone satisfy an inference-location requirement?"
  ],
  "supported_claims": [
    {
      "claim": "Snowflake describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof of the region used by a particular request or a legal residency determination",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "Snowflake describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Snowflake Cortex cross-region inference",
    "source_url": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cross-region-inference",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-CORTEX-PROCESSING-STORAGE-REGION-01-v1",
    "candidate_record_sha256": "055619387506f5cfb8448578b6b29f1444f2ff1b74c6d4761454507d2ef49316",
    "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 describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.",
    "required_buyer_context": "The account region and effective routing parameter. The model and permitted clouds or geographies. Applicable processing restrictions and request evidence. 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 Snowflake account storage residency prove Cortex inference stays in the same region?",
    "documented_statement": {
      "status": "documented",
      "statement": "Snowflake describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.",
      "source_ids": [
        "snowflake"
      ]
    },
    "buyer_evidence_required": [
      "The account region and effective routing parameter.",
      "The model and permitted clouds or geographies.",
      "Applicable processing restrictions and request evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not approve region-local processing without checking the effective account routing configuration."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "snowflake",
        "url": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cross-region-inference",
        "final_url": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cross-region-inference",
        "title": "Snowflake Cortex cross-region inference",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:01:58.685Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "4c4836765a85b40fd2f54bcd9d8af11c99b63856a0f01b6a87739f2320cd1563",
        "bytes": 145694,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does Snowflake account storage residency prove Cortex inference stays in the same region?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A data owner must approve inference locations independently of the warehouse storage location.",
      "free": "Complete review, practical questions, sources 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": "The account region and effective routing parameter. The model and permitted clouds or geographies. Applicable processing restrictions and request evidence."
    },
    "buyer_relevance": "A data owner must approve inference locations independently of the warehouse storage location.",
    "refusal_conditions": [
      "Do not approve region-local processing without checking the effective account routing configuration."
    ]
  },
  "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": "A data owner must approve inference locations independently of the warehouse storage location.",
    "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-cortex-processing-storage-region",
  "machine_readable_record": "/varexis-index/records/snowflake-cortex-processing-storage-region.json"
}
