Back to home

Compare

Comparing: Same Book, Different Reports: An Engineer Cut AI's Right to Rewrite Preferences & 同书不同报告:这位工程师把'AI 改写用户偏好'的权限关掉了

AEN
AI personalizationreading profilesBookGraph·

Same Book, Different Reports: An Engineer Cut AI's Right to Rewrite Preferences

What This Is

A developer on Juejin called BookMap (问书地图) published a long post detailing how he built an AI book-report product. Same web novel, different readers get different versions—but the key insight isn't "AI understands you." It's "AI doesn't draw conclusions for you."

The system splits in two: BookGraph (a structured factual base for the book) answers "what happens in the book"; the reading profile answers "what matters most to this reader." The first is AI-extracted from the full text; the second can only be confirmed and edited by the reader themselves. The AI can only "suggest" profile changes based on reading statistics—it cannot rewrite them directly.

In other words: personalization isn't stuffing preferences into a prompt and letting the model guess for you. It's separating "guess" from "decide"—AI offers observations, humans make the final call.

The Industry View

We think this deserves to be read against a bigger trend. This year, every Agent product is racing to own the "actively understand the user" narrative—from memory systems to behavior prediction, models increasingly act as if they're deciding for users. This developer's counter-move is, in our reading, a rare clear-headed voice: he admits that "recently read" ≠ "long-term liked," and "didn't abandon the book" ≠ "can accept it"—so he'd rather have users confirm one extra time.

That said, counter-arguments are real. Critics will point out: user confirmation creates friction—every extra step loses a batch of users; from a growth standpoint, "AI auto-memory + inference" is the path to scale. We agree this design may fit a niche of heavy readers and may not generalize to mainstream Agents. Meanwhile, AI reading statistics are themselves model inferences—whether those supposedly "objective signals" carry bias still needs verification.

The more practical risk, in our view, is engineering cost: understanding an entire book and consolidating it into structured knowledge is expensive for long-form content, and hard for small teams to replicate.

What It Means for Regular People

For enterprise IT: When building AI products, "user data ownership" and "AI inference authority" should be written into product docs—not just promises buried in the privacy policy. This approach (AI can only suggest, never rewrite) is worth copying.

For professionals: When using AI assistants, pay attention to the "profile of you" they quietly accumulate without your notice. The rights to check and delete may not actually be in your hands.

For the consumer market: "Guess what you like" recommendations are getting more aggressive, and the side effects are starting to be debated. "User-controlled AI personalization" may become the differentiator for the next product generation.

Source: juejin.cn
BZH
问书地图AI 个性化阅读画像·

同书不同报告:这位工程师把'AI 改写用户偏好'的权限关掉了

这是什么

掘金上开发者「问书地图」写了一篇长文,讲他怎么做一个 AI 扫书报告产品。同一本网文,不同读者拿到不同版本——但关键不在「AI 懂你」,而在「AI 不替你下结论」。

系统被拆成两半:BookGraph(书的结构化事实底座)回答「书里发生了什么」;阅读画像回答「什么对这个读者最重要」。前者由 AI 从全书提取,后者只能由读者本人确认后修改。AI 只能根据阅读统计「建议」画像变化,不能直接改写。

也就是说:个性化不是把偏好塞进 Prompt 让模型替你猜,而是把「猜」和「决定」分开——AI 提供观察,人做最终判断。

行业怎么看

这件事值得放进更大趋势里看。今年各家 Agent 产品都在抢「主动理解用户」的叙事——从记忆系统到行为预测,模型越来越像在替用户做决定。这位开发者的反向选择是个少见的清醒声音:他承认「最近看过」≠「长期喜欢」,「没立刻弃书」≠「能接受」,所以宁可让用户多确认一次。

但也有反对意见。有人会指出:用户确认有摩擦,多一步交互就流失一批人;从增长角度看,「AI 自动记忆+推断」才是规模化路径。这套设计可能更适合重度阅读玩家这种小众场景,未必能复制到通用 Agent。同时,AI 阅读统计本身也是模型推断,所谓「客观信号」是否真不带偏见,还需要验证。

更现实的风险是工程成本:一次全书理解要沉淀成结构化知识,对长内容开销不小,小团队难复制。

对普通人的影响

对企业 IT:做 AI 产品时,「用户数据所有权」和「AI 推断权限」应该写进产品文档,不只是隐私政策里的承诺。这套做法(AI 只能建议、不能改写)值得抄。

对个人职场:用各种 AI 助手时,留意它在你没注意时自动积累的「关于你的画像」。勾选和删除权,未必真在你手上。

对消费市场:「猜你喜欢」型推荐越来越激进,副作用开始被讨论。「用户可控的 AI 个性化」可能成为下一代产品的差异化卖点。

Source: juejin.cn