[{"data":1,"prerenderedAt":493},["ShallowReactive",2],{"blog-posts":3},[4,96,176,255,334,414],{"id":5,"title":6,"author":7,"avatar":8,"body":9,"categories":77,"date":79,"description":80,"extension":81,"image":82,"meta":83,"navigation":84,"path":85,"premium":86,"seo":87,"stem":88,"takeaways":89,"tldr":94,"__hash__":95},"blog\u002Fzh\u002Fblog\u002Fatoms-instead-of-files.md","为什么 Chronnote 用「原子」而不是文件","Chronnote","\u002Flogo.png",{"type":10,"value":11,"toc":70},"minimark",[12,17,21,34,38,41,52,56,59],[13,14,16],"h2",{"id":15},"原子解决了什么问题","原子解决了什么问题？",[18,19,20],"p",{},"原子解决的是知识分散问题。用户不需要把同一个想法复制到文档、白板、任务和导图里，而是保留一份真实内容，让不同视图引用它。",[22,23,24,28,31],"ul",{},[25,26,27],"li",{},"PDF 摘录可以进入笔记，也可以出现在白板上。",[25,29,30],{},"任务可以继续连接到产生它的材料。",[25,32,33],{},"AI 可以读取更完整的上下文，而不是零散片段。",[13,35,37],{"id":36},"原子和文件有什么不同","原子和文件有什么不同？",[18,39,40],{},"文件通常属于一个文件夹，需要出现在别处时就会被复制。原子则天然适合被引用，同一份知识可以参与多个工作流而不分裂成多个版本。",[22,42,43,46,49],{},[25,44,45],{},"页面可以包含多种原子的引用。",[25,47,48],{},"白板可以空间化排列原子，但不拥有内容本身。",[25,50,51],{},"导图可以组织原子关系，而不破坏原子的身份。",[13,53,55],{"id":54},"这为什么有助于-ai-工作流","这为什么有助于 AI 工作流？",[18,57,58],{},"AI 需要真实上下文才更有用。Chronnote 的原子模型让 Chron 引擎可以围绕已连接的材料搜索和组织，而不是只依赖空白提示词。",[22,60,61,64,67],{},[25,62,63],{},"阅读高亮、笔记和白板片段都可以参与回答。",[25,65,66],{},"旧上下文可以在需要时被重新带回。",[25,68,69],{},"用户保留判断，AI 沿着已有材料继续推进。",{"title":71,"searchDepth":72,"depth":72,"links":73},"",2,[74,75,76],{"id":15,"depth":72,"text":16},{"id":36,"depth":72,"text":37},{"id":54,"depth":72,"text":55},[78],"产品","2026-05-27","原子模型让笔记、PDF、待办、导图和白板能在不同视图中复用，而不需要在工具之间反复复制。","md","\u002Fimages\u002Fblog\u002Fpost-1.webp",{},true,"\u002Fzh\u002Fblog\u002Fatoms-instead-of-files",false,{"title":6,"description":80},"zh\u002Fblog\u002Fatoms-instead-of-files",[90,91,92,93],"原子是可复用的知识单元，不是被复制的文件。","引用让同一个原子出现在页面、导图和白板中。","编辑任意引用，都会更新背后的真实原子。","这个模型让 AI 可以从连续上下文中工作。","Chronnote 使用原子模型，是因为知识很少只属于一个文件。笔记、PDF、待办、导图和白板都可以被多个位置引用，同时保持为一份同步的真实内容。","G9ZN5mLLSCSngl0ZptNF0Ma2GebEgn2K_6OAeet7Iqw",{"id":97,"title":98,"author":7,"avatar":8,"body":99,"categories":160,"date":162,"description":163,"extension":81,"image":164,"meta":165,"navigation":84,"path":166,"premium":86,"seo":167,"stem":168,"takeaways":169,"tldr":174,"__hash__":175},"blog\u002Fzh\u002Fblog\u002Flocal-first-notes.md","本地优先笔记，适合长期思考",{"type":10,"value":100,"toc":155},[101,105,108,119,123,126,137,141,144],[13,102,104],{"id":103},"为什么本地优先适合知识工作","为什么本地优先适合知识工作？",[18,106,107],{},"本地优先能让知识不完全依赖单一服务或网络状态。对于笔记、PDF 和个人研究来说，这种长期可用性比短期便利更重要。",[22,109,110,113,116],{},[25,111,112],{},"用户可以围绕本地材料继续工作。",[25,114,115],{},"知识档案更接近创建它们的设备。",[25,117,118],{},"同步可以成为增强能力，而不是访问基础。",[13,120,122],{"id":121},"chronnote-如何平衡本地工作和-ai","Chronnote 如何平衡本地工作和 AI？",[18,124,125],{},"Chronnote 把用户自己的材料放在工作区中心，再让 AI 读取和组织这些材料。目标是帮助思考，而不是把判断完全移到远程聊天框里。",[22,127,128,131,134],{},[25,129,130],{},"Chron 引擎从笔记、PDF、原子和引用开始。",[25,132,133],{},"Reader 与白板材料继续留在工作区。",[25,135,136],{},"AI 输出可以回到结构化笔记中。",[13,138,140],{"id":139},"谁最适合本地优先笔记","谁最适合本地优先笔记？",[18,142,143],{},"本地优先笔记适合写作者、学生、研究者和长期知识工作者。这些用户会在数月甚至数年后回到同一批材料。",[22,145,146,149,152],{},[25,147,148],{},"长期项目依赖稳定的参考资料。",[25,150,151],{},"个人知识常包含隐私和未完成想法。",[25,153,154],{},"耐久的本地工作区让未来检索更容易。",{"title":71,"searchDepth":72,"depth":72,"links":156},[157,158,159],{"id":103,"depth":72,"text":104},{"id":121,"depth":72,"text":122},{"id":139,"depth":72,"text":140},[161,78],"公司","2026-05-20","Chronnote 把核心知识工作留在本地设备上，同时保留同步与 AI 协作空间，减少长期资料被平台锁死的风险。","\u002Fimages\u002Fblog\u002Fpost-2.webp",{},"\u002Fzh\u002Fblog\u002Flocal-first-notes",{"title":98,"description":163},"zh\u002Fblog\u002Flocal-first-notes",[170,171,172,173],"本地优先降低平台锁定风险。","私人笔记和阅读材料需要更强的数据控制。","AI 围绕用户材料工作时才更有价值。","长期思考需要稳定结构，而不只是快速捕捉。","本地优先笔记重要，是因为重要知识应该更耐久、更可控、更接近用户。Chronnote 把云同步和 AI 当作工作区周围的助手，而不是知识所有权的替代品。","TyjbE_ePf825CjsS85zF9tW2omxWZMcgwrEdQoHW_VE",{"id":177,"title":178,"author":7,"avatar":8,"body":179,"categories":240,"date":241,"description":242,"extension":81,"image":243,"meta":244,"navigation":84,"path":245,"premium":86,"seo":246,"stem":247,"takeaways":248,"tldr":253,"__hash__":254},"blog\u002Fzh\u002Fblog\u002Fpdf-reading-context.md","阅读 PDF 时，如何不丢掉上下文",{"type":10,"value":180,"toc":235},[181,185,188,199,203,206,217,221,224],[13,182,184],{"id":183},"为什么-pdf-高亮经常消失","为什么 PDF 高亮经常消失？",[18,186,187],{},"PDF 高亮经常消失，是因为它们停留在阅读器里，没有进入活跃的知识系统。Chronnote 把阅读视为工作流开始，而不是结束。",[22,189,190,193,196],{},[25,191,192],{},"重要摘录可以连接到笔记。",[25,194,195],{},"用户可以围绕选中材料提问。",[25,197,198],{},"阅读片段可以变成之后整理的原子。",[13,200,202],{"id":201},"reader-如何保留上下文","Reader 如何保留上下文？",[18,204,205],{},"Reader 让 PDF 摘录、翻译和问题进入同一个工作区，与笔记、待办和白板继续连接。后续工作仍能追溯到源材料。",[22,207,208,211,214],{},[25,209,210],{},"选区可以成为可复用材料。",[25,212,213],{},"笔记可以保留高亮段落的意义。",[25,215,216],{},"Chron 引擎可以从文档上下文中回答。",[13,218,220],{"id":219},"这会如何改变研究流程","这会如何改变研究流程？",[18,222,223],{},"它缩短了阅读和综合之间的距离。用户可以从 PDF 证据进入笔记、导图、白板和提纲，而不必在另一个工具里重建上下文。",[22,225,226,229,232],{},[25,227,228],{},"研究证据可以贴近最终输出。",[25,230,231],{},"导图可以组织观点和来源。",[25,233,234],{},"任务可以连接到产生它们的阅读材料。",{"title":71,"searchDepth":72,"depth":72,"links":236},[237,238,239],{"id":183,"depth":72,"text":184},{"id":201,"depth":72,"text":202},{"id":219,"depth":72,"text":220},[78],"2026-05-13","Reader 的高亮、划词翻译和选区提问可以回流到笔记与 Chron 引擎，让阅读材料继续参与后续整理。","\u002Fimages\u002Fblog\u002Fpost-3.png",{},"\u002Fzh\u002Fblog\u002Fpdf-reading-context",{"title":178,"description":242},"zh\u002Fblog\u002Fpdf-reading-context",[249,250,251,252],"PDF 阅读应该进入后续写作和规划。","高亮与笔记连接后才更有价值。","AI 回答应该引用正在阅读的材料。","Reader 上下文可以延续到导图、白板和待办。","Chronnote Reader 的目标，是让 PDF 阅读不止停留在孤立高亮里。选区、翻译、问题和笔记可以回到原子工作区，并在之后继续发挥作用。","x6-YJ8lZfSQpVnDeZDiMXk6fxXC-55qBsWY_6ijLQ6A",{"id":256,"title":257,"author":7,"avatar":8,"body":258,"categories":319,"date":320,"description":321,"extension":81,"image":322,"meta":323,"navigation":84,"path":324,"premium":86,"seo":325,"stem":326,"takeaways":327,"tldr":332,"__hash__":333},"blog\u002Fzh\u002Fblog\u002Fwhiteboard-to-workflow.md","从白板碎片到结构化工作流",{"type":10,"value":259,"toc":314},[260,264,267,278,282,285,296,300,303],[13,261,263],{"id":262},"为什么白板容易变成死角","为什么白板容易变成死角？",[18,265,266],{},"白板会变成死角，是因为草图和卡片常常脱离知识系统。Chronnote 通过原子引用，让白板上的内容继续连接到真实材料。",[22,268,269,272,275],{},[25,270,271],{},"笔记可以作为白板卡片出现。",[25,273,274],{},"PDF 片段可以和相关想法放在一起。",[25,276,277],{},"任务可以保留产生它的白板上下文。",[13,279,281],{"id":280},"碎片如何变成结构","碎片如何变成结构？",[18,283,284],{},"当用户把原子分组、连线，并从白板推进到页面或导图时，碎片会变成结构。视觉排列成为组织工作的中间层。",[22,286,287,290,293],{},[25,288,289],{},"相关原子可以被空间化聚合。",[25,291,292],{},"导图把关系变成层级。",[25,294,295],{},"页面收束最终结构，同时保留引用。",[13,297,299],{"id":298},"ai-在这个流程里做什么","AI 在这个流程里做什么？",[18,301,302],{},"AI 可以帮助总结聚类、发现缺失连接，或把白板材料整理成提纲。区别在于 Chron 引擎从白板上的真实原子开始工作。",[22,304,305,308,311],{},[25,306,307],{},"白板上下文让 AI 不再面对空白提示词。",[25,309,310],{},"引用保留了可检查的源材料。",[25,312,313],{},"AI 协助后，用户仍能继续编辑结构。",{"title":71,"searchDepth":72,"depth":72,"links":315},[316,317,318],{"id":262,"depth":72,"text":263},{"id":280,"depth":72,"text":281},{"id":298,"depth":72,"text":299},[78],"2026-05-06","白板草图、思维导图和页面引用可以连接成一条脉络，让临时想法逐步变成可执行的计划。","\u002Fimages\u002Fblog\u002Fpost-4.png",{},"\u002Fzh\u002Fblog\u002Fwhiteboard-to-workflow",{"title":257,"description":321},"zh\u002Fblog\u002Fwhiteboard-to-workflow",[328,329,330,331],"白板适合捕捉早期混乱想法。","原子引用让白板内容连接到源材料。","导图和页面可以把碎片变成结构。","用户不需要在工具之间复制内容。","Chronnote 白板不是孤立画布。它可以承载真实原子的引用，让早期的空间化思考逐步变成笔记、计划、导图和任务。","Svp8GzHP5mKHo2_i9IB7eeVK9eDkc56cG4f0431i2n8",{"id":335,"title":336,"author":7,"avatar":8,"body":337,"categories":398,"date":400,"description":401,"extension":81,"image":402,"meta":403,"navigation":84,"path":404,"premium":86,"seo":405,"stem":406,"takeaways":407,"tldr":412,"__hash__":413},"blog\u002Fzh\u002Fblog\u002Fchron-engine-real-materials.md","围绕真实材料设计 Chron 引擎",{"type":10,"value":338,"toc":393},[339,343,346,357,361,364,375,379,382],[13,340,342],{"id":341},"为什么要从真实材料开始","为什么要从真实材料开始？",[18,344,345],{},"从真实材料开始，AI 回答会更相关，也更容易验证。工作区已经包含用户的证据、判断和未完成问题。",[22,347,348,351,354],{},[25,349,350],{},"PDF 摘录提供来源上下文。",[25,352,353],{},"笔记记录用户如何理解材料。",[25,355,356],{},"待办和白板显示意图与下一步。",[13,358,360],{"id":359},"原子模型如何支持检索","原子模型如何支持检索？",[18,362,363],{},"原子模型给 Chron 引擎提供了可连接的检索单元。它不必把每份文档当作孤岛，而是可以沿着笔记、白板、导图和阅读材料之间的引用继续查找。",[22,365,366,369,372],{},[25,367,368],{},"相关原子可以出现在多个视图中。",[25,370,371],{},"引用保留材料之间的关系。",[25,373,374],{},"上下文可以从工作区结构中恢复。",[13,376,378],{"id":377},"用户在其中扮演什么角色","用户在其中扮演什么角色？",[18,380,381],{},"用户仍然决定什么重要。Chron 引擎可以建议结构、找回相关材料和生成草稿，但工作区会让人的判断保持可见。",[22,383,384,387,390],{},[25,385,386],{},"AI 输出可以被继续编辑和重组。",[25,388,389],{},"源原子保留给用户检查。",[25,391,392],{},"系统支持继续工作，而不是只输出最终答案。",{"title":71,"searchDepth":72,"depth":72,"links":394},[395,396,397],{"id":341,"depth":72,"text":342},{"id":359,"depth":72,"text":360},{"id":377,"depth":72,"text":378},[161,399],"新闻","2026-04-29","Chron 引擎不是从空白提示词开始回答，而是读取工作区里的笔记、PDF 与原子，再帮助你继续判断。","\u002Fimages\u002Fblog\u002Fpost-5.png",{},"\u002Fzh\u002Fblog\u002Fchron-engine-real-materials",{"title":336,"description":401},"zh\u002Fblog\u002Fchron-engine-real-materials",[408,409,410,411],"AI 基于已有材料才更有用。","Chron 引擎从工作区上下文开始，而不是空白提示词。","原子让检索与推理更连贯。","用户仍然负责判断和最终结构。","Chron 引擎围绕用户真实材料设计。它的价值来自读取工作区上下文：笔记、PDF 摘录、原子引用、导图、白板和待办。","VKVnOoTKGR2N2vta2Cg8vaqdHyrbXO1u7LVocFBHJnI",{"id":415,"title":416,"author":7,"avatar":8,"body":417,"categories":478,"date":479,"description":480,"extension":81,"image":481,"meta":482,"navigation":84,"path":483,"premium":86,"seo":484,"stem":485,"takeaways":486,"tldr":491,"__hash__":492},"blog\u002Fzh\u002Fblog\u002Fdesktop-early-access.md","Chronnote 桌面版内测说明",{"type":10,"value":418,"toc":473},[419,423,426,437,441,444,455,459,462],[13,420,422],{"id":421},"内测包含什么","内测包含什么？",[18,424,425],{},"内测让用户提前尝试围绕原子、阅读、白板、导图和 AI 辅助展开的桌面工作流。重点是来自真实知识工作的反馈。",[22,427,428,431,434],{},[25,429,430],{},"用户可以测试本地优先工作区。",[25,432,433],{},"Reader 与白板是核心流程的一部分。",[25,435,436],{},"反馈会影响更大范围发布前的产品优先级。",[13,438,440],{"id":439},"为什么从桌面端开始","为什么从桌面端开始？",[18,442,443],{},"桌面端更适合验证深度知识工作，因为用户需要阅读、书写、对照、排列和规划。移动端可以在核心模型稳定后继续推进。",[22,445,446,449,452],{},[25,447,448],{},"PDF 阅读和白板更需要大屏空间。",[25,450,451],{},"长时间写作更适合桌面。",[25,453,454],{},"本地优先存储也更适合先在桌面验证。",[13,456,458],{"id":457},"早期用户应该如何反馈","早期用户应该如何反馈？",[18,460,461],{},"早期用户最值得反馈的是上下文在哪里丢失、原子引用哪里不清楚、Chron 引擎哪里没有用好已有材料。这比泛泛的功能请求更重要。",[22,463,464,467,470],{},[25,465,466],{},"工作流断点能暴露优先级。",[25,468,469],{},"引用困惑能定位模型问题。",[25,471,472],{},"AI 反馈最好绑定真实材料。",{"title":71,"searchDepth":72,"depth":72,"links":474},[475,476,477],{"id":421,"depth":72,"text":422},{"id":439,"depth":72,"text":440},{"id":457,"depth":72,"text":458},[399],"2026-04-22","整理桌面版早期用户最关心的内测入口、早鸟价格、版本节奏和下一轮工作流改进方向。","\u002Fimages\u002Fblog\u002Fpost-6.webp",{},"\u002Fzh\u002Fblog\u002Fdesktop-early-access",{"title":416,"description":480},"zh\u002Fblog\u002Fdesktop-early-access",[487,488,489,490],"内测重点是工作流反馈。","桌面端优先验证深度知识工作。","早鸟价格支持早期用户和持续开发。","社区反馈会影响后续产品迭代。","Chronnote 桌面版内测关注真实用户对原子工作区、Reader、白板、导图、待办和 Chron 引擎的反馈，再进入更大范围发布。","iEMyxbf4Au6_bgzMuHzLSlS209FIUhQTFS5d8cq1jjU",1780978351857]