Maggie Appleton 写设计、人类学和智能体界面时，习惯先画清楚隐喻，再谈工具。把「Epistemic Disclosure」整理成可阅读的中文笔记：问题在哪、界面默认会把人带去哪、落地时该改什么。原站导航、评论回响和广告已去掉。

The Context

For most of the words we read online, we have a limited amount of context about the writer and how much effort they’ve put into the piece we’re reading.

We might have a name and a tiny 32px profile image. We don’t know how long it took them to write these words, how many hundreds of tabs they read through, or whether they spent years earning a graduate degree on the topic. We rarely have a rich backstory with a comprehensive educational and professional history at hand.

The Pattern

If we disagree with their points, we’re more likely to be ungenerous Epistemic Peers who assume the worst: they’ve barfed this garbage up in a single, frenzied caffeine rush and haven’t so much as opened Google Scholar to check for prior art.

That might all be true. Which is fine. As long as they disclose the situation upfront. The only true source of disappointment – in both reading and life – is unmet expectations.

References and Further Reading

At the beginning of a piece of writing, the author writes a sentence or two about the epistemic status of the work. Epistemology is the study of knowledge – how we know things, the methods we use to gain knowledge, and how we validate knowledge as “true.” So an epistemic status usually covers how the author came to know what they know. This includes how much effort they put into researching it, how they validated the information, and how sure they are abou

Scott Alexander of Slate Star Codex was one of the earliest well-known bloggers to do this. Many of his posts include statuses that range from “total conjecture” to “pretty good, but I make no claim this is original.” Here are a few more choice examples:

落地时建议先做的 5 件事

1. 先写清这个工具在强化思考还是在替人思考。
2. 默认交互不要只会谄媚：该追问、该给反例、该要求证据。
3. 智能体界面要露出推理步骤，而不是只给一个光滑答案。
4. 知识发布用可生长的笔记，而不是一次性营销长文。
5. 改产品前先画隐喻：用户以为自己在做什么，系统实际在做什么。

和智能体产品怎么接

龙虾PRO做 OpenClaw 落地时，最该从这类笔记里拿走的是「别把聊天框当唯一界面」。数字员工要能追问、能验证、能把过程摊开，而不是只负责说好话。

本文侧重全链路风控方法论。落地时请用自身业务单据做回放验证，不要把示例阈值直接当生产策略。 相关：风控体检 · 方案资源