{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T12:55:40.483Z",
  "record_id": "VXI-EXT-PROCUREMENT-DBT-SEMANTIC-IDENTITY-01-v1",
  "record_kind": "external_reference",
  "title": "dbt Semantic Layer: Tokens and warehouse identity",
  "system": "dbt Semantic Layer",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does each Semantic Layer service token use an independent warehouse identity?",
  "near_questions": [
    "Can multiple dbt service tokens share one credential?",
    "Which warehouse identity executes a metric query?",
    "Does a token name prove separate grants?",
    "Can a token map to multiple credentials in one project?",
    "Which plan supports multiple credentials?",
    "Are underlying warehouse policies applied?",
    "What happens when a linked credential is deleted?",
    "Does a read-only recommendation prove effective grants?",
    "Which environment supplies the credential values?",
    "Can one team token expose another team schema?",
    "What mapping evidence should procurement request?",
    "Can I save the Semantic Layer identity review?"
  ],
  "supported_claims": [
    {
      "claim": "Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.",
      "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": "Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "dbt Semantic Layer credential mapping",
    "source_url": "https://docs.getdbt.com/guides/sl-qs",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DBT-SEMANTIC-IDENTITY-01-v1",
    "candidate_record_sha256": "77d6001db2a709c3314c789ad543717e4d7fb66b750b8ca68549d35bb646ebfa",
    "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": "Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.",
    "required_buyer_context": "Project, environment, plan, token mapping and underlying warehouse grants. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "Different service tokens necessarily provide separate warehouse identities.",
    "documented_statement": {
      "status": "documented",
      "statement": "Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.",
      "source_ids": [
        "dbt-credentials"
      ]
    },
    "buyer_evidence_required": [
      "Token-to-credential mapping for the project.",
      "Warehouse grants and data policies for that credential.",
      "Plan entitlement and downstream client use."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require the actual mapping before asserting separate data access for different clients."
    },
    "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": "dbt-credentials",
        "url": "https://docs.getdbt.com/guides/sl-qs",
        "final_url": "https://docs.getdbt.com/guides/sl-qs",
        "title": "dbt Semantic Layer credential mapping",
        "checked_on": "2026-10-16",
        "sha256": "f95282ba7b2931b3bfc15f665fcdd4838ce534f1aba633051953a78da56b3964",
        "bytes": 380523
      }
    ],
    "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": "Retain the credential-mapping evidence behind an analytical data-access decision.",
      "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": "Project, environment, plan, token mapping and underlying warehouse grants."
    }
  },
  "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#dbt-semantic-layer-token-warehouse-identity",
  "machine_readable_record": "/varexis-index/records/dbt-semantic-layer-token-warehouse-identity.json"
}