{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-ROVO-HOSTED-LLM-PROCESSOR-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Rovo: Hosted-model selection changes the processor boundary",
  "system": "Rovo",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Rovo no-training commitment restrict processing to our single approved external LLM provider?",
  "near_questions": [
    "Can Rovo be locked to one external LLM supplier?",
    "What changes when Atlassian-hosted LLMs are enabled?",
    "Is the hosted-model option per site or organisation?",
    "Does no training prevent third-party inference processing?",
    "Which Rovo model-routing evidence belongs in procurement?",
    "Does hosted LLM processing remove every cloud hosting provider?"
  ],
  "supported_claims": [
    {
      "claim": "Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Absence of cloud hosting subprocessors or independent verification of processing paths",
    "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": "Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Atlassian-hosted LLMs",
    "source_url": "https://support.atlassian.com/organization-administration/docs/atlassian-hosted-llms/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ROVO-HOSTED-LLM-PROCESSOR-BOUNDARY-01-v1",
    "candidate_record_sha256": "cda5a7352c4c8d7f59789ce15265411c5f02149bd83671659239302a1e797fe5",
    "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": "Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.",
    "required_buyer_context": "The organisation plan and hosted-LLM setting. Approved processing suppliers and scope. Current feature availability and configuration 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 a Rovo no-training commitment restrict processing to our single approved external LLM provider?",
    "documented_statement": {
      "status": "documented",
      "statement": "Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.",
      "source_ids": [
        "atlassian-hosted"
      ]
    },
    "buyer_evidence_required": [
      "The organisation plan and hosted-LLM setting.",
      "Approved processing suppliers and scope.",
      "Current feature availability and configuration evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not equate a no-training commitment with exclusive use of the buyer-approved external model provider."
    },
    "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": "atlassian-hosted",
        "url": "https://support.atlassian.com/organization-administration/docs/atlassian-hosted-llms/",
        "final_url": "https://support.atlassian.com/organization-administration/docs/atlassian-hosted-llms/",
        "title": "Atlassian-hosted LLMs",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:01:58.993Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "ee453420a835270be0a102bec854bf698850bdd38c5bc62e41c3adf7f061f4ab",
        "bytes": 468948,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does a Rovo no-training commitment restrict processing to our single approved external LLM provider?"
        ]
      }
    ],
    "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 supplier-review owner must identify whether the actual model-routing configuration matches approved subprocessors.",
      "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 organisation plan and hosted-LLM setting. Approved processing suppliers and scope. Current feature availability and configuration evidence."
    },
    "buyer_relevance": "A supplier-review owner must identify whether the actual model-routing configuration matches approved subprocessors.",
    "refusal_conditions": [
      "Do not equate a no-training commitment with exclusive use of the buyer-approved external model provider."
    ]
  },
  "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 supplier-review owner must identify whether the actual model-routing configuration matches approved subprocessors.",
    "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#rovo-hosted-llm-processor-boundary",
  "machine_readable_record": "/varexis-index/records/rovo-hosted-llm-processor-boundary.json"
}
