> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connex.hybridsphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently Asked Questions (FAQ)

> Authoritative answers to common questions about CONNEX Cloud OS and the HybridSphere enterprise platform

## 01. Platform Overview & Vision

<AccordionGroup>
  <Accordion title="How does CONNEX Cloud OS differ from traditional AI chatbots?">
    **CONNEX Cloud OS** is not a simple conversational bot. It is an **Agentic Cloud Workspace Operating System** built for strategic enterprise decision-making and knowledge assetization:

    * **Full-Stack Cloud OS Capabilities:** Seamlessly integrates a virtual file system (VFS), real-time collaboration canvas (CoWorx), agent studio, and knowledge engine (Brain X).
    * **Deterministic Security Boundaries:** Statutory privacy compliance (Korea PIPA, US CCPA) and session security are strictly hardcoded with zero tolerance for probabilistic AI conjecture.
    * **Real-Time Knowledge Synchronization:** Synchronizes with Git repositories and the Mintlify global documentation portal to eliminate documentation obsolescence.
  </Accordion>

  <Accordion title="Who are the primary target users of the CONNEX platform?">
    CONNEX provides **dual-spectrum intelligence** spanning executive leadership to technical researchers:

    * **Executives & Strategy Teams:** High-density ERP/CRM/BI synthesis, M\&A due diligence, legal/tax brief drafting, and strategic decision support.
    * **R\&D & Engineering Teams:** Dynamic tool-chaining across 108+ APIs, MCP agent integration, and autonomous code synthesis.
    * **Personal & Family Life:** Children's educational roadmaps, family travel logistics, and intelligent day-to-day assistance.
  </Accordion>
</AccordionGroup>

***

## 02. Data Sovereignty & Security

<AccordionGroup>
  <Accordion title="How is physical isolation enforced between Korea (PIPA) and US (CCPA/GDPR) users?">
    CONNEX implements **strict physical database segregation across geographic regions**:

    * **Republic of Korea Jurisdiction (PIPA):** All identifiers, session tokens, and profiles for Korean users reside exclusively in the `accounts-kr` Firestore database in Seoul (`asia-northeast3`).
    * **US & Global Jurisdiction (CCPA/GDPR):** Data for international users resides in the `accounts-us` Firestore database in Iowa (`us-central1`).
    * **Zero Cross-Contamination:** Intercontinental loop queries are permanently banned. Requests route directly to the single database corresponding to the user's `home_country`.
  </Accordion>

  <Accordion title="What is the single-use UUIDv4 ticket handshake protocol?">
    To protect cross-domain single sign-on (SSO) transitions against replay attacks, CONNEX uses a **single-use ticket handshake**:

    * **Issuance:** The identity authority generates a cryptographically secure UUIDv4 ticket mapped in Redis with a **120-second TTL**.
    * **Immediate Burning:** The ticket is permanently deleted from Redis upon its first exchange request (`/api/v1/auth/exchange`).
    * **Replay Protection:** Re-submitting an already used ticket results in immediate rejection, completely mitigating packet interception risks.
  </Accordion>
</AccordionGroup>

***

## 03. Global Infrastructure & Performance SLAs

<AccordionGroup>
  <Accordion title="What are the platform latency and availability SLAs?">
    CONNEX guarantees ultra-low-latency authentication and streaming performance globally:

    * **Authentication SLA:** Auth verification completes globally in **under 300ms** by embedding authorization claims directly into cryptographically signed JWT tokens.
    * **Real-Time Bidirectional Streaming:** ASGI thin orchestrators maintain zero-delay WebSocket and SSE pipelines.
    * **GKE Gateway API:** Traffic is routed through modern GKE L7 External Managed Gateways with Google Certificate Manager SSL termination.
  </Accordion>
</AccordionGroup>

***

## 04. Agentic AI & Citation Fidelity

<AccordionGroup>
  <Accordion title="How does CONNEX eliminate AI hallucinations and ensure citation fidelity?">
    CONNEX enforces strict **citation fidelity filters** across all document-grounded reasoning:

    * **In-Text Section Citations:** Responses reference source documents using explicit chunk citations (`[ref:filename#section]`).
    * **Contingency Disclosure Banner:** If an external data source fails and fallback search is engaged, a mandatory notice banner (`[Data Source Contingency Notice]`) is displayed.
    * **Deterministic Business Rules:** Financial computations, statutory clauses, and role verifications are 100% hardcoded in Python, never delegated to LLM conjecture.
  </Accordion>
</AccordionGroup>

***

## 05. CoWorx Collaboration & Cloud VFS

<AccordionGroup>
  <Accordion title="How does the Virtual File System (VFS) synchronize file mutations in real time?">
    CONNEX VFS operates an event-driven 3-tier cache invalidation and broadcast pipeline:

    * **7 Mutation Operations:** Folder creation, upload, deletion, rename, move, copy, and clone trigger instant Redis L2 cache flushes.
    * **SSE VFS\_CHANGED Propagation:** Broadcasts the `VFS_CHANGED` global event immediately, synchronizing file trees across all connected clients in 0ms.
    * **Single Folder Badge Standard:** Selecting folders transmits clean single directory badges without expanding hundreds of individual files on the frontend.
  </Accordion>
</AccordionGroup>

***

## 06. Identity, RBAC & Single Sign-On

<AccordionGroup>
  <Accordion title="Does CONNEX store user passwords in its databases?">
    **No. The CONNEX platform stores zero user password hashes in its databases.**

    * **100% Firebase Delegation:** Credential verification, MFA, and cryptographic password handling are fully delegated to Google Identity / Firebase Authentication.
    * **Decoupled Architecture:** Core credentials reside exclusively within Google IAM infrastructure; Firestore stores non-credential enterprise profile metadata only.
  </Accordion>
</AccordionGroup>

***

## 07. Capital Efficiency & Token Economics

<AccordionGroup>
  <Accordion title="How does CONNEX optimize AI token consumption and reduce operating costs (FinOps)?">
    CONNEX enforces the **Four Laws of Token Capital Allocation** to maximize ROIC:

    * **1-Turn 1-Channel Precision Targeting:** A 0.1s query planner targets the exact required tool instead of triggering wasteful multi-tool searches.
    * **5-Turn Budget Capping:** All agent reasoning loops terminate within 5 turns to prevent infinite token-bleeding loops.
    * **L1 Front-Door Gatekeeper:** Basic metadata lookups and greetings are resolved in 0.1s at the low-cost L1 layer without invoking high-cost reasoning models.
    * **3-Tiered Caching:** L1 Memory and L2 Redis return cached responses for recurrent queries, driving marginal token costs to zero.
  </Accordion>
</AccordionGroup>


## Related topics

- [CONNEX | Docs Center](/index.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.