Editing Chuk Chat Architecture

= Chuk Chat Architecture =

This page explains the system architecture at a level that is useful for curious users, product people, and technical readers.

== Four-layer architecture ==
Chuk Chat is organized in four main layers:

# '''Presentation layer''': pages, chat UI, sidebars, settings screens.
# '''Service layer''': business logic (chat handling, model config, sync, encryption helpers).
# '''Data layer''': models and persisted chat data.
# '''Platform layer''': platform-specific behavior for mobile, desktop, and web.

== Why this architecture is used ==
* Easier maintenance and safer updates
* Better testing and reliability
* Clear separation between UI, logic, and storage

== Platform structure ==
* '''Desktop''' (Windows, macOS, Linux): multi-panel layout with sidebar plus chat workspace.
* '''Mobile''' (Android): single-panel chat with slide-out navigation and mobile input UX.
* '''Web''': desktop-style layout with browser-safe platform stubs where needed.

== State and sync model ==
* UI state (input focus, scroll position) stays local to screens.
* App state (chat content, selected model, preferences) is managed by services.
* Persisted state (chat history, preferences) is stored and synced, with encrypted chat content.

== Streaming architecture ==
Chuk Chat supports both:
* HTTP SSE streaming (POST /v1/ai/chat)
* WebSocket streaming (/v1/ai/chat/ws)

This gives good browser compatibility plus stable mobile streaming behavior.

== Security architecture highlights ==
* End-to-end encrypted chat storage
* Certificate pinning on supported native platforms
* Zero-data-retention provider filtering at the routing layer

== Related pages ==
* [[How Chuk Chat Works]]
* [[Chuk Chat AI Providers and Services]]
* [[Chuk Chat Backend and API]]

[[Category:Chuk Chat]]
[[Category:Architecture]]