Google’s Daily Hub is more complex than it first appears.
It’s part of the broader acceleration toward hyperpersonalization we’ve been seeing in recent months – Preferred Sources, Profile Pages with followable elements in Discover, Brand Profiles in Merchant Center – all converging toward a single goal: anticipating your needs before you even formulate a query.
Daily Hub is the concrete expression of the “News Digest and Daily Brief” agent identified during our investigations this summer into Google’s 90 AI projects via the AI Mode debug menu.
The internal architecture of the system, which Damien Andell managed to decrypt and share with me in advance, reveals a level of technical complexity that also explains why Google temporarily suspended the feature in September 2025, just a month after its launch on the Pixel 10.
The three-tier architecture of Daily Hub
To understand Daily Hub, imagine a conductor (Gemini) who must coordinate three sections of a symphony orchestra, each playing a different score but having to harmonize in real time.
This is exactly what Google is trying to do with this system.
First tier: The ‘memory and embeddings’ layer
Daily Hub relies on two fundamental types of documents that constitute its memory:
MemoryDocument represents the complete content unit. Each document contains:
- Structured textual content (title, summary, rawText divided into segments).
- A list of entity identifiers (entityIds) extracted from the Knowledge Graph.
- Two types of embeddings: contentEmbeddings for the entire document and chunkEmbeddings for each segment.
- Technical metadata (sourceDataIds, memoryTimeMs, servingState).
- Binary data (memoryContentBytes, memoryInfoBytes) for optimized storage.
MemoryEntityDocument is lighter and represents each extracted entity:
- Entity characteristics (entityType, entityText, entityDescription, entityTag).
- Link to parent document via parentMemoryId and memoryQualifiedId.
- A single embedding (contentEmbeddings) without chunk division.
- A specific timestamp (entityTimeMs).
Concretely, if Daily Hub processes an article about “Lionel Messi joins Inter Miami”, the system will create:
- A MemoryDocument containing the complete article with its embeddings.
- Several MemoryEntityDocument: one for “Lionel Messi” (type: Person), one for “Inter Miami CF” (type: Organization), one for “soccer” (type: Sport), etc.
This dual structure allows the system to navigate either by content (via documents) or by entity (for thematic recommendations).
Second tier: The personalization triumvirate
Andell discovered that three parallel systems feed Daily Hub’s personalization:
Nephesh (the universal embeddings system)
This is Google’s universal embeddings system that Andell had already documented in his analyses of Discover (to preserve its anonymity, the name of this model has been changed in this article).
In…
Source link
Disclaimer
We strive to uphold the highest ethical standards in all of our reporting and coverage. We blogs.grocliq.com want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.
Website Upgradation is going on for any glitch kindly connect at [email protected]
