Notes

A note is Markdown you supply directly: an excerpt from a document Context cannot read, a summary of a decision, a field observation, a checklist from experience. Context saves it as a source under sources/note/YYYYMMDD/topic.md. There is no registry and no capture phase — the saved file is the evidence that pages cite.

Use a note when the material is text you already hold. Use a session summary when it comes from an Agent conversation, and a document source or Lark source when Context can capture the original itself.

Prepare the content

A note may hold original text, selected verbatim excerpts, a summary, or a mix. No fixed template is required, but when both originals and a summary are present, separate them with headings or prose, and label any summary as a summary rather than a transcript.

• Keep qualifications, exceptions, disagreements and open questions that affect the conclusion.
• State where the material came from and what was left out, when the omission matters.
• Quote only actual input; do not invent links, speakers, dates or confirmations.
• A link in a note does not mean its target was read.

Pages cite the note as saved, so leave out anything the eventual readers must not see before you save it.

Save and select it

Ask the Agent in plain language:

Save these release-process notes as a Context note, then use them for a
page on hotfix releases.

The Agent saves the body with context source import. Saving alone starts no knowledge work. To use the note in a production task, the Agent adds its typed reference to src/index.ts, keeping existing sources and phases:

source("20261012/release-process.md", { type: "note" });

A note that only supports an existing page does not need this: it joins that page's reading scope during a revision.

How notes become knowledge

The Agent integrates what is useful into explanations, rules or steps for the reader; it does not copy the note wholesale or turn proposals into facts. A short exact passage is quoted only when its wording matters. Citations point at the stored note, never at an original the Agent could not read.

Correcting a note

Two different problems, two different fixes:

Problem	Fix
The note misrepresents the material	Correct the note itself through source import, passing its current base_digest.
The note is right but a page is misleading	Revise only that page and send it through Review.

Approving knowledge never changes or removes the note. To rename one, context source rename <ref> --name <name> previews the change and then updates existing references safely.

笔记

笔记是你直接提供的 Markdown：Context 无法读取的文档中的摘录、一项决策的摘要、一线观察记录、经验总结出的检查清单。Context 将其保存为来源，路径为 sources/note/YYYYMMDD/topic.md。它没有登记表，也没有采集阶段——保存下来的文件本身就是页面所引用的证据。

当材料是你手头已有的文本时，使用笔记。如果内容来自 Agent 对话，使用会话摘要；如果 Context 能自行采集原文，则使用文档来源或飞书来源。

准备内容

笔记可以包含原文、精选的逐字摘录、摘要，或几者混合。没有固定模板要求，但如果同时包含原文和摘要，请用标题或文字把它们分开，并将摘要明确标注为摘要，而不是原始记录。

• 保留会影响结论的限定条件、例外、分歧和未决问题。
• 当省略内容很重要时，说明材料的出处以及略去了什么。
• 只引用真实的输入；不要编造链接、发言人、日期或确认信息。
• 笔记中出现某个链接，并不代表其目标已被读取。

页面按保存时的样子引用笔记，所以在保存之前，请删去最终读者不应看到的任何内容。

保存并选用

用自然语言告诉 Agent：

Save these release-process notes as a Context note, then use them for a
page on hotfix releases.

Agent 会通过 context source import 保存正文。仅保存不会启动任何知识工作。要在生产任务中使用该笔记，Agent 会在 src/index.ts 中加入它的类型化引用，同时保留已有的来源和阶段：

source("20261012/release-process.md", { type: "note" });

如果笔记只用于支撑某个已有页面，则无需这样做：在修订时它会被纳入该页面的阅读范围。

笔记如何变成知识

Agent 会把有用的内容融入面向读者的讲解、规则或步骤中；它不会整篇照搬笔记，也不会把提议当成事实。只有在措辞本身很重要时，才会引用一小段原文。引用指向存储的笔记，绝不指向 Agent 无法读取的原始材料。

修正笔记

两类不同的问题，对应两种不同的修复方式：

问题	修复方式
笔记没有如实反映材料	通过 source import 修正笔记本身，并传入它当前的 base_digest。
笔记无误，但某个页面有误导	只修订该页面，并提交审核。

批准知识绝不会修改或删除笔记。如需重命名笔记，context source rename <ref> --name <name> 会先预览变更，再安全地更新已有引用。