{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T01:25:58.088Z",
  "record_id": "VXI-EXT-PROCUREMENT-PINECONE-TENANT-ROUTING-01-v1",
  "record_kind": "external_reference",
  "title": "Pinecone namespaces: Data separation and tenant routing",
  "system": "Pinecone serverless multitenancy",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does one namespace per tenant prove an application always selects the authorised tenant?",
  "near_questions": [
    "Do separate namespaces prove correct tenant authorisation?",
    "Which namespace does a retrieval request actually target?",
    "Can application routing select the wrong tenant namespace?",
    "What evidence connects authenticated identity to data scope?",
    "How do namespace separation and request authorisation differ?",
    "Does a vendor architecture diagram test my application?",
    "What should procurement ask about multitenant vector retrieval?",
    "Can a saved namespace review replace cross-tenant tests?",
    "Which mapping should an agent preserve in its decision record?",
    "Does missing evidence prove tenant isolation has failed?",
    "Can I save the source-bound tenant-routing checklist?",
    "When should namespace routing be reassessed?"
  ],
  "supported_claims": [
    {
      "claim": "Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-POSTGRES-RLS-PRIVILEGES-01-v1",
    "VXI-EXT-PROCUREMENT-SNOWFLAKE-QUERY-HISTORY-01-v1",
    "VXI-EXT-PROCUREMENT-MONGODB-RESUME-01-v1",
    "VXI-EXT-PROCUREMENT-DATABRICKS-CONNECTION-GRANTS-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Pinecone namespaces and tenant routing",
    "source_url": "https://docs.pinecone.io/guides/index-data/implement-multitenancy",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PINECONE-TENANT-ROUTING-01-v1",
    "candidate_record_sha256": "a742e533919db49942aa346dadd7306749127196023321058de614e838c2ffae",
    "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": "Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.",
    "required_buyer_context": "Serverless index, tenant-to-namespace mapping and application request identity.",
    "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-14",
    "claim_to_check": "Creating tenant namespaces proves application-level authorisation is correct.",
    "documented_statement": {
      "status": "documented",
      "statement": "Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.",
      "source_ids": [
        "pinecone-tenants"
      ]
    },
    "buyer_evidence_required": [
      "Namespace assignment for each intended tenant",
      "How authenticated tenant identity selects the request namespace",
      "Authorised tests of cross-tenant rejection in the buyer application"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not substitute storage separation for evidence of correct application routing."
    },
    "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": "pinecone-tenants",
        "url": "https://docs.pinecone.io/guides/index-data/implement-multitenancy",
        "final_url": "https://docs.pinecone.io/guides/index-data/implement-multitenancy",
        "title": "Pinecone namespaces and tenant routing",
        "checked_on": "2026-10-14",
        "sha256": "6ffcac77d90c6fcd2cc260f1310683f50d4ed42d4d8b43ea07fa7fea4c15e499",
        "bytes": 1169405
      }
    ],
    "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": "Save the separation-versus-routing distinction for a retrieval-system procurement review.",
      "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": "Recheck namespace mapping, application identity handling and index changes."
    }
  },
  "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#pinecone-namespace-routing-evidence",
  "machine_readable_record": "/varexis-index/records/pinecone-namespace-routing-evidence.json"
}