Reader
The journey begins where readers live — library shelves, the interactive reader, immersive listening, and voice. Every gesture here is intent waiting to travel downward through the stack.
AliveBookOpen the readerAliveBook platform architecture: seven coordinated layers from User Experience through Infrastructure, connecting library and reader surfaces to a shared experience runtime, grounded intelligence, content identity pipelines, replaceable AI capability adapters, backend APIs, and traced infrastructure.
AliveBook Platform Architecture
The Architecture of a Living Book
Seven coordinated layers with replaceable AI capabilities — from infrastructure and intelligence to narration, conversation, and the reader experience.
01
User Experience
Digital reader + headphones
Surfaces readers touch — library, reader, immersive modes, and voice.
02
Experience Engine
Gears + waveform
Coordinated runtime for sessions, sync, voice FSMs, and shared Ask streaming.
03
Intelligence
Neural brain
Grounded dialogue, voice intent contracts, RAG, and safety rules.
04
Content Engine
Manuscript → structure
Ingests books, stable IDs, sync manifests, embeddings, and narration assets.
05
AI Services
Capability chip
Replaceable capability adapters for LLM, TTS, STT, and embeddings.
06
Backend
Server + API + DB
APIs, auth, libraries, progress, and operational services.
07
Infrastructure
Cloud + shield
Runtime, storage, delivery, tracing, and engineering foundations.
How the layers work together
Experience Engine
A coordinated runtime — playback, voice FSMs, shared Ask streaming, and ambient presence. Narration, scroll, and voice stay aligned without friction.
Intelligence
Grounded conversation, voice intent, and retrieval keep answers chapter-faithful while feeling like dialogue with the book — not a generic chatbot bolted on.
Content
Manuscripts become structured chapters, sync manifests, embeddings, and narration assets. This layer is the substrate that powers search, sync, and dramatized delivery.
AI + Backend
Replaceable capability adapters, auth, libraries, and progress services translate reader intent into secure responses — the bridge between surfaces and AI providers.
Infrastructure
Hosting, storage, delivery, and request tracing carry AliveBook globally. Trace IDs on AI routes tie logs to reader sessions.
Coordinated System
Each layer stays independently understandable, but the living book emerges from a coordinated runtime — replaceable capabilities, shared contracts, and seven layers operating in concert.
One platform. Seven coordinated layers.
A digital reader with headphones at the top — peel the stack apart to see how experience, intelligence, content, and infrastructure coordinate underneath.
01
User Experience
Digital reader + headphones
12 nodes
02
Experience Engine
Gears + waveform
15 nodes
03
Intelligence
Neural brain
14 nodes
04
Content Engine
Manuscript → structure
15 nodes
05
AI Services
Capability chip
13 nodes
06
Backend
Server + API + DB
17 nodes
07
Infrastructure
Cloud + shield
17 nodes