[{"data":1,"prerenderedAt":958},["ShallowReactive",2],{"blog-posts-zh":3},[4,96,174,254,332,411,488,567,644,724,802,881],{"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":79,"description":162,"extension":81,"image":82,"meta":163,"navigation":84,"path":164,"premium":86,"seo":165,"stem":166,"takeaways":167,"tldr":172,"__hash__":173},"blog\u002Fen\u002Fblog\u002Fatoms-instead-of-files.md","Why Chronnote Uses Atoms, Not Files",{"type":10,"value":100,"toc":155},[101,105,108,119,123,126,137,141,144],[13,102,104],{"id":103},"what-problem-do-atoms-solve","What problem do atoms solve?",[18,106,107],{},"Atoms solve the problem of scattered knowledge. Instead of copying the same idea between a document, whiteboard, task list, and mind map, Chronnote keeps one source of truth and lets each view reference it.",[22,109,110,113,116],{},[25,111,112],{},"A PDF excerpt can become a note, appear on a whiteboard, and later feed a mind map.",[25,114,115],{},"A task can remain connected to the material that created it.",[25,117,118],{},"AI can retrieve a richer context because the material stays linked.",[13,120,122],{"id":121},"how-are-atoms-different-from-files","How are atoms different from files?",[18,124,125],{},"Files usually live in one folder and get copied when they need to appear elsewhere. Atoms are designed for reference, so the same knowledge unit can appear in multiple workflows without splitting into separate versions.",[22,127,128,131,134],{},[25,129,130],{},"A page can contain references to many atom types.",[25,132,133],{},"A whiteboard can arrange atoms spatially without owning their content.",[25,135,136],{},"A mind map can structure atoms without breaking their original identity.",[13,138,140],{"id":139},"why-does-this-help-ai-workflows","Why does this help AI workflows?",[18,142,143],{},"AI assistants work better when they can read real context. Chronnote’s atom model gives Chron Engine connected material to search and reason from, instead of relying on a blank prompt or an isolated note.",[22,145,146,149,152],{},[25,147,148],{},"Reader highlights, notes, and board fragments can all participate in answers.",[25,150,151],{},"The system can recover older context when a question depends on it.",[25,153,154],{},"Users keep judgment in the workspace while AI continues from existing material.",{"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],"Product","How atoms let notes, PDFs, tasks, mind maps, and whiteboards stay reusable without being copied between tools.",{},"\u002Fen\u002Fblog\u002Fatoms-instead-of-files",{"title":98,"description":162},"en\u002Fblog\u002Fatoms-instead-of-files",[168,169,170,171],"Atoms are reusable knowledge units, not duplicated files.","References let one atom appear in pages, maps, and whiteboards.","Editing any reference updates the underlying atom.","The model helps AI work from connected context instead of fragments.","Chronnote uses atoms because knowledge rarely belongs in only one file. A note, PDF, task, mind map, or whiteboard can be referenced from multiple places while remaining one synchronized entity.","bAXdglaMXE-mpcSl9ywanHGrv9j1X8FxhiG_LHF2GYo",{"id":175,"title":176,"author":7,"avatar":8,"body":177,"categories":238,"date":240,"description":241,"extension":81,"image":242,"meta":243,"navigation":84,"path":244,"premium":86,"seo":245,"stem":246,"takeaways":247,"tldr":252,"__hash__":253},"blog\u002Fzh\u002Fblog\u002Flocal-first-notes.md","本地优先笔记，适合长期思考",{"type":10,"value":178,"toc":233},[179,183,186,197,201,204,215,219,222],[13,180,182],{"id":181},"为什么本地优先适合知识工作","为什么本地优先适合知识工作？",[18,184,185],{},"本地优先能让知识不完全依赖单一服务或网络状态。对于笔记、PDF 和个人研究来说，这种长期可用性比短期便利更重要。",[22,187,188,191,194],{},[25,189,190],{},"用户可以围绕本地材料继续工作。",[25,192,193],{},"知识档案更接近创建它们的设备。",[25,195,196],{},"同步可以成为增强能力，而不是访问基础。",[13,198,200],{"id":199},"chronnote-如何平衡本地工作和-ai","Chronnote 如何平衡本地工作和 AI？",[18,202,203],{},"Chronnote 把用户自己的材料放在工作区中心，再让 AI 读取和组织这些材料。目标是帮助思考，而不是把判断完全移到远程聊天框里。",[22,205,206,209,212],{},[25,207,208],{},"Chron 引擎从笔记、PDF、原子和引用开始。",[25,210,211],{},"Reader 与白板材料继续留在工作区。",[25,213,214],{},"AI 输出可以回到结构化笔记中。",[13,216,218],{"id":217},"谁最适合本地优先笔记","谁最适合本地优先笔记？",[18,220,221],{},"本地优先笔记适合写作者、学生、研究者和长期知识工作者。这些用户会在数月甚至数年后回到同一批材料。",[22,223,224,227,230],{},[25,225,226],{},"长期项目依赖稳定的参考资料。",[25,228,229],{},"个人知识常包含隐私和未完成想法。",[25,231,232],{},"耐久的本地工作区让未来检索更容易。",{"title":71,"searchDepth":72,"depth":72,"links":234},[235,236,237],{"id":181,"depth":72,"text":182},{"id":199,"depth":72,"text":200},{"id":217,"depth":72,"text":218},[239,78],"公司","2026-05-20","Chronnote 把核心知识工作留在本地设备上，同时保留同步与 AI 协作空间，减少长期资料被平台锁死的风险。","\u002Fimages\u002Fblog\u002Fpost-2.webp",{},"\u002Fzh\u002Fblog\u002Flocal-first-notes",{"title":176,"description":241},"zh\u002Fblog\u002Flocal-first-notes",[248,249,250,251],"本地优先降低平台锁定风险。","私人笔记和阅读材料需要更强的数据控制。","AI 围绕用户材料工作时才更有价值。","长期思考需要稳定结构，而不只是快速捕捉。","本地优先笔记重要，是因为重要知识应该更耐久、更可控、更接近用户。Chronnote 把云同步和 AI 当作工作区周围的助手，而不是知识所有权的替代品。","TyjbE_ePf825CjsS85zF9tW2omxWZMcgwrEdQoHW_VE",{"id":255,"title":256,"author":7,"avatar":8,"body":257,"categories":318,"date":240,"description":320,"extension":81,"image":242,"meta":321,"navigation":84,"path":322,"premium":86,"seo":323,"stem":324,"takeaways":325,"tldr":330,"__hash__":331},"blog\u002Fen\u002Fblog\u002Flocal-first-notes.md","Local-First Notes for Long-Term Thinking",{"type":10,"value":258,"toc":313},[259,263,266,277,281,284,295,299,302],[13,260,262],{"id":261},"why-is-local-first-useful-for-knowledge-work","Why is local-first useful for knowledge work?",[18,264,265],{},"Local-first design helps knowledge survive beyond a single service or network condition. For notes, PDFs, and personal research, that durability matters more than short-term convenience.",[22,267,268,271,274],{},[25,269,270],{},"Users can keep working with local materials.",[25,272,273],{},"Knowledge archives remain available on the device where they are created.",[25,275,276],{},"Sync can become an enhancement instead of the foundation of access.",[13,278,280],{"id":279},"how-does-chronnote-balance-local-work-and-ai","How does Chronnote balance local work and AI?",[18,282,283],{},"Chronnote keeps the workspace centered on user-owned materials, then lets AI participate by reading and organizing those materials. The goal is to improve thinking without moving every judgment into a remote chat box.",[22,285,286,289,292],{},[25,287,288],{},"Chron Engine starts from notes, PDFs, atoms, and references.",[25,290,291],{},"Reader and whiteboard materials stay part of the workspace.",[25,293,294],{},"AI output can be folded back into structured notes.",[13,296,298],{"id":297},"who-benefits-most-from-local-first-notes","Who benefits most from local-first notes?",[18,300,301],{},"Local-first notes are most useful for writers, students, researchers, and knowledge workers who return to material over months or years. These users need continuity, privacy, and structure.",[22,303,304,307,310],{},[25,305,306],{},"Long projects depend on stable reference material.",[25,308,309],{},"Personal knowledge often includes private or unfinished thinking.",[25,311,312],{},"A durable local workspace makes future retrieval easier.",{"title":71,"searchDepth":72,"depth":72,"links":314},[315,316,317],{"id":261,"depth":72,"text":262},{"id":279,"depth":72,"text":280},{"id":297,"depth":72,"text":298},[319,161],"Company","Why Chronnote keeps core knowledge work close to your device while still making room for sync and AI assistance.",{},"\u002Fen\u002Fblog\u002Flocal-first-notes",{"title":256,"description":320},"en\u002Fblog\u002Flocal-first-notes",[326,327,328,329],"Local-first design reduces platform lock-in.","Private notes and reading material deserve stronger user control.","AI is more useful when it works around the user’s own material.","Long-term thinking needs durable structure, not only fast capture.","Local-first notes matter because important knowledge should remain durable, portable, and close to the user. Chronnote treats cloud sync and AI as assistants around the workspace, not substitutes for ownership.","87tTemJOkImLxydpp07eXVpLBZBlxnYLIJc8K3NzoX0",{"id":333,"title":334,"author":7,"avatar":8,"body":335,"categories":396,"date":397,"description":398,"extension":81,"image":399,"meta":400,"navigation":84,"path":401,"premium":86,"seo":402,"stem":403,"takeaways":404,"tldr":409,"__hash__":410},"blog\u002Fzh\u002Fblog\u002Fpdf-reading-context.md","阅读 PDF 时，如何不丢掉上下文",{"type":10,"value":336,"toc":391},[337,341,344,355,359,362,373,377,380],[13,338,340],{"id":339},"为什么-pdf-高亮经常消失","为什么 PDF 高亮经常消失？",[18,342,343],{},"PDF 高亮经常消失，是因为它们停留在阅读器里，没有进入活跃的知识系统。Chronnote 把阅读视为工作流开始，而不是结束。",[22,345,346,349,352],{},[25,347,348],{},"重要摘录可以连接到笔记。",[25,350,351],{},"用户可以围绕选中材料提问。",[25,353,354],{},"阅读片段可以变成之后整理的原子。",[13,356,358],{"id":357},"reader-如何保留上下文","Reader 如何保留上下文？",[18,360,361],{},"Reader 让 PDF 摘录、翻译和问题进入同一个工作区，与笔记、待办和白板继续连接。后续工作仍能追溯到源材料。",[22,363,364,367,370],{},[25,365,366],{},"选区可以成为可复用材料。",[25,368,369],{},"笔记可以保留高亮段落的意义。",[25,371,372],{},"Chron 引擎可以从文档上下文中回答。",[13,374,376],{"id":375},"这会如何改变研究流程","这会如何改变研究流程？",[18,378,379],{},"它缩短了阅读和综合之间的距离。用户可以从 PDF 证据进入笔记、导图、白板和提纲，而不必在另一个工具里重建上下文。",[22,381,382,385,388],{},[25,383,384],{},"研究证据可以贴近最终输出。",[25,386,387],{},"导图可以组织观点和来源。",[25,389,390],{},"任务可以连接到产生它们的阅读材料。",{"title":71,"searchDepth":72,"depth":72,"links":392},[393,394,395],{"id":339,"depth":72,"text":340},{"id":357,"depth":72,"text":358},{"id":375,"depth":72,"text":376},[78],"2026-05-13","Reader 的高亮、划词翻译和选区提问可以回流到笔记与 Chron 引擎，让阅读材料继续参与后续整理。","\u002Fimages\u002Fblog\u002Fpost-3.png",{},"\u002Fzh\u002Fblog\u002Fpdf-reading-context",{"title":334,"description":398},"zh\u002Fblog\u002Fpdf-reading-context",[405,406,407,408],"PDF 阅读应该进入后续写作和规划。","高亮与笔记连接后才更有价值。","AI 回答应该引用正在阅读的材料。","Reader 上下文可以延续到导图、白板和待办。","Chronnote Reader 的目标，是让 PDF 阅读不止停留在孤立高亮里。选区、翻译、问题和笔记可以回到原子工作区，并在之后继续发挥作用。","x6-YJ8lZfSQpVnDeZDiMXk6fxXC-55qBsWY_6ijLQ6A",{"id":412,"title":413,"author":7,"avatar":8,"body":414,"categories":475,"date":397,"description":476,"extension":81,"image":399,"meta":477,"navigation":84,"path":478,"premium":86,"seo":479,"stem":480,"takeaways":481,"tldr":486,"__hash__":487},"blog\u002Fen\u002Fblog\u002Fpdf-reading-context.md","Reading PDFs Without Losing Context",{"type":10,"value":415,"toc":470},[416,420,423,434,438,441,452,456,459],[13,417,419],{"id":418},"why-do-pdf-highlights-often-disappear","Why do PDF highlights often disappear?",[18,421,422],{},"PDF highlights often disappear because they stay inside a reader instead of entering the user’s active knowledge system. Chronnote treats reading as the beginning of a workflow, not the end.",[22,424,425,428,431],{},[25,426,427],{},"Important excerpts can be connected to notes.",[25,429,430],{},"Questions can be asked from the selected material.",[25,432,433],{},"Reading fragments can become atoms for later organization.",[13,435,437],{"id":436},"how-does-reader-keep-context-alive","How does Reader keep context alive?",[18,439,440],{},"Reader keeps context alive by letting PDF excerpts, translations, and questions flow into the same workspace as notes, tasks, and whiteboards. The source material remains connected to later work.",[22,442,443,446,449],{},[25,444,445],{},"Selections can become reusable material.",[25,447,448],{},"Notes can retain the meaning of a highlighted passage.",[25,450,451],{},"Chron Engine can respond from the document context.",[13,453,455],{"id":454},"what-does-this-change-for-research-workflows","What does this change for research workflows?",[18,457,458],{},"It reduces the gap between reading and synthesis. A user can move from PDF evidence to notes, mind maps, whiteboards, and draft structure without rebuilding context in another app.",[22,460,461,464,467],{},[25,462,463],{},"Research evidence can stay close to the output it supports.",[25,465,466],{},"Mind maps can organize claims and sources.",[25,468,469],{},"Tasks can be linked to the reading that created them.",{"title":71,"searchDepth":72,"depth":72,"links":471},[472,473,474],{"id":418,"depth":72,"text":419},{"id":436,"depth":72,"text":437},{"id":454,"depth":72,"text":455},[161],"A closer look at how Reader highlights, translations, and selected passages can flow back into notes and Chron Engine.",{},"\u002Fen\u002Fblog\u002Fpdf-reading-context",{"title":413,"description":476},"en\u002Fblog\u002Fpdf-reading-context",[482,483,484,485],"PDF reading should feed later writing and planning.","Highlights become more useful when linked to notes.","AI answers should reference the material being read.","Reader context can continue into mind maps, whiteboards, and tasks.","Chronnote Reader is designed so PDF reading does not end as isolated highlights. Selected passages, translations, questions, and notes can return to the atom workspace and remain useful later.","ib7-fy9GpaI3Aokal8Ya2UYKLX8XRbihHn5_yvmUtO8",{"id":489,"title":490,"author":7,"avatar":8,"body":491,"categories":552,"date":553,"description":554,"extension":81,"image":555,"meta":556,"navigation":84,"path":557,"premium":86,"seo":558,"stem":559,"takeaways":560,"tldr":565,"__hash__":566},"blog\u002Fzh\u002Fblog\u002Fwhiteboard-to-workflow.md","从白板碎片到结构化工作流",{"type":10,"value":492,"toc":547},[493,497,500,511,515,518,529,533,536],[13,494,496],{"id":495},"为什么白板容易变成死角","为什么白板容易变成死角？",[18,498,499],{},"白板会变成死角，是因为草图和卡片常常脱离知识系统。Chronnote 通过原子引用，让白板上的内容继续连接到真实材料。",[22,501,502,505,508],{},[25,503,504],{},"笔记可以作为白板卡片出现。",[25,506,507],{},"PDF 片段可以和相关想法放在一起。",[25,509,510],{},"任务可以保留产生它的白板上下文。",[13,512,514],{"id":513},"碎片如何变成结构","碎片如何变成结构？",[18,516,517],{},"当用户把原子分组、连线，并从白板推进到页面或导图时，碎片会变成结构。视觉排列成为组织工作的中间层。",[22,519,520,523,526],{},[25,521,522],{},"相关原子可以被空间化聚合。",[25,524,525],{},"导图把关系变成层级。",[25,527,528],{},"页面收束最终结构，同时保留引用。",[13,530,532],{"id":531},"ai-在这个流程里做什么","AI 在这个流程里做什么？",[18,534,535],{},"AI 可以帮助总结聚类、发现缺失连接，或把白板材料整理成提纲。区别在于 Chron 引擎从白板上的真实原子开始工作。",[22,537,538,541,544],{},[25,539,540],{},"白板上下文让 AI 不再面对空白提示词。",[25,542,543],{},"引用保留了可检查的源材料。",[25,545,546],{},"AI 协助后，用户仍能继续编辑结构。",{"title":71,"searchDepth":72,"depth":72,"links":548},[549,550,551],{"id":495,"depth":72,"text":496},{"id":513,"depth":72,"text":514},{"id":531,"depth":72,"text":532},[78],"2026-05-06","白板草图、思维导图和页面引用可以连接成一条脉络，让临时想法逐步变成可执行的计划。","\u002Fimages\u002Fblog\u002Fpost-4.png",{},"\u002Fzh\u002Fblog\u002Fwhiteboard-to-workflow",{"title":490,"description":554},"zh\u002Fblog\u002Fwhiteboard-to-workflow",[561,562,563,564],"白板适合捕捉早期混乱想法。","原子引用让白板内容连接到源材料。","导图和页面可以把碎片变成结构。","用户不需要在工具之间复制内容。","Chronnote 白板不是孤立画布。它可以承载真实原子的引用，让早期的空间化思考逐步变成笔记、计划、导图和任务。","Svp8GzHP5mKHo2_i9IB7eeVK9eDkc56cG4f0431i2n8",{"id":568,"title":569,"author":7,"avatar":8,"body":570,"categories":631,"date":553,"description":632,"extension":81,"image":555,"meta":633,"navigation":84,"path":634,"premium":86,"seo":635,"stem":636,"takeaways":637,"tldr":642,"__hash__":643},"blog\u002Fen\u002Fblog\u002Fwhiteboard-to-workflow.md","From Whiteboard Fragments to Structured Workflows",{"type":10,"value":571,"toc":626},[572,576,579,590,594,597,608,612,615],[13,573,575],{"id":574},"why-do-whiteboards-become-dead-ends","Why do whiteboards become dead ends?",[18,577,578],{},"Whiteboards become dead ends when sketches and cards are disconnected from the rest of the knowledge system. Chronnote avoids this by letting whiteboard items reference real atoms.",[22,580,581,584,587],{},[25,582,583],{},"A note can appear as a board card.",[25,585,586],{},"A PDF fragment can sit beside related ideas.",[25,588,589],{},"A task can remain tied to the board that created it.",[13,591,593],{"id":592},"how-do-fragments-become-structure","How do fragments become structure?",[18,595,596],{},"Fragments become structure when users group, connect, and move atoms from a whiteboard into pages or mind maps. The visual arrangement becomes a bridge into organized work.",[22,598,599,602,605],{},[25,600,601],{},"Related atoms can be clustered spatially.",[25,603,604],{},"Mind maps can turn relationships into hierarchy.",[25,606,607],{},"Pages can collect the final structure without losing references.",[13,609,611],{"id":610},"where-does-ai-fit-into-the-workflow","Where does AI fit into the workflow?",[18,613,614],{},"AI can help summarize clusters, identify missing links, or turn whiteboard material into an outline. The difference is that Chron Engine works from the atoms already on the board.",[22,616,617,620,623],{},[25,618,619],{},"Board context gives AI more than a blank prompt.",[25,621,622],{},"References preserve source material for later checks.",[25,624,625],{},"Users can keep editing the structure after AI assists.",{"title":71,"searchDepth":72,"depth":72,"links":627},[628,629,630],{"id":574,"depth":72,"text":575},{"id":592,"depth":72,"text":593},{"id":610,"depth":72,"text":611},[161],"How Chronnote connects whiteboard sketches, mind maps, and page references so rough ideas can become usable plans.",{},"\u002Fen\u002Fblog\u002Fwhiteboard-to-workflow",{"title":569,"description":632},"en\u002Fblog\u002Fwhiteboard-to-workflow",[638,639,640,641],"Whiteboards help capture early, messy thinking.","Atom references keep board items connected to source material.","Mind maps and pages can turn fragments into structure.","Structured work emerges without copying content between tools.","Chronnote whiteboards are not isolated canvases. They can hold references to real atoms, so rough spatial thinking can gradually become notes, plans, mind maps, and tasks.","wdZL4IcA23Zl_8Zlw4VssLRFHN3QLMfksptArStXGm4",{"id":645,"title":646,"author":7,"avatar":8,"body":647,"categories":708,"date":710,"description":711,"extension":81,"image":712,"meta":713,"navigation":84,"path":714,"premium":86,"seo":715,"stem":716,"takeaways":717,"tldr":722,"__hash__":723},"blog\u002Fzh\u002Fblog\u002Fchron-engine-real-materials.md","围绕真实材料设计 Chron 引擎",{"type":10,"value":648,"toc":703},[649,653,656,667,671,674,685,689,692],[13,650,652],{"id":651},"为什么要从真实材料开始","为什么要从真实材料开始？",[18,654,655],{},"从真实材料开始，AI 回答会更相关，也更容易验证。工作区已经包含用户的证据、判断和未完成问题。",[22,657,658,661,664],{},[25,659,660],{},"PDF 摘录提供来源上下文。",[25,662,663],{},"笔记记录用户如何理解材料。",[25,665,666],{},"待办和白板显示意图与下一步。",[13,668,670],{"id":669},"原子模型如何支持检索","原子模型如何支持检索？",[18,672,673],{},"原子模型给 Chron 引擎提供了可连接的检索单元。它不必把每份文档当作孤岛，而是可以沿着笔记、白板、导图和阅读材料之间的引用继续查找。",[22,675,676,679,682],{},[25,677,678],{},"相关原子可以出现在多个视图中。",[25,680,681],{},"引用保留材料之间的关系。",[25,683,684],{},"上下文可以从工作区结构中恢复。",[13,686,688],{"id":687},"用户在其中扮演什么角色","用户在其中扮演什么角色？",[18,690,691],{},"用户仍然决定什么重要。Chron 引擎可以建议结构、找回相关材料和生成草稿，但工作区会让人的判断保持可见。",[22,693,694,697,700],{},[25,695,696],{},"AI 输出可以被继续编辑和重组。",[25,698,699],{},"源原子保留给用户检查。",[25,701,702],{},"系统支持继续工作，而不是只输出最终答案。",{"title":71,"searchDepth":72,"depth":72,"links":704},[705,706,707],{"id":651,"depth":72,"text":652},{"id":669,"depth":72,"text":670},{"id":687,"depth":72,"text":688},[239,709],"新闻","2026-04-29","Chron 引擎不是从空白提示词开始回答，而是读取工作区里的笔记、PDF 与原子，再帮助你继续判断。","\u002Fimages\u002Fblog\u002Fpost-5.png",{},"\u002Fzh\u002Fblog\u002Fchron-engine-real-materials",{"title":646,"description":711},"zh\u002Fblog\u002Fchron-engine-real-materials",[718,719,720,721],"AI 基于已有材料才更有用。","Chron 引擎从工作区上下文开始，而不是空白提示词。","原子让检索与推理更连贯。","用户仍然负责判断和最终结构。","Chron 引擎围绕用户真实材料设计。它的价值来自读取工作区上下文：笔记、PDF 摘录、原子引用、导图、白板和待办。","VKVnOoTKGR2N2vta2Cg8vaqdHyrbXO1u7LVocFBHJnI",{"id":725,"title":726,"author":7,"avatar":8,"body":727,"categories":788,"date":710,"description":790,"extension":81,"image":712,"meta":791,"navigation":84,"path":792,"premium":86,"seo":793,"stem":794,"takeaways":795,"tldr":800,"__hash__":801},"blog\u002Fen\u002Fblog\u002Fchron-engine-real-materials.md","Designing Chron Engine Around Real Materials",{"type":10,"value":728,"toc":783},[729,733,736,747,751,754,765,769,772],[13,730,732],{"id":731},"why-start-from-real-materials","Why start from real materials?",[18,734,735],{},"Starting from real materials makes AI answers more relevant and easier to verify. A workspace already contains the user’s evidence, decisions, and unfinished questions.",[22,737,738,741,744],{},[25,739,740],{},"PDF excerpts provide source context.",[25,742,743],{},"Notes show how the user interpreted material.",[25,745,746],{},"Tasks and whiteboards reveal intent and next steps.",[13,748,750],{"id":749},"how-does-the-atom-model-support-retrieval","How does the atom model support retrieval?",[18,752,753],{},"The atom model gives Chron Engine connected units to search and combine. Instead of treating every document as isolated, it can follow references across notes, whiteboards, mind maps, and reading material.",[22,755,756,759,762],{},[25,757,758],{},"Related atoms can appear across multiple views.",[25,760,761],{},"References preserve relationships between materials.",[25,763,764],{},"Context can be recovered from the workspace structure.",[13,766,768],{"id":767},"what-is-the-role-of-the-user","What is the role of the user?",[18,770,771],{},"The user still decides what matters. Chron Engine can suggest structure, surface related material, and draft outlines, but the workspace keeps human judgment visible.",[22,773,774,777,780],{},[25,775,776],{},"AI output can be edited and reorganized.",[25,778,779],{},"Source atoms remain available for checking.",[25,781,782],{},"The system supports continued work, not only final answers.",{"title":71,"searchDepth":72,"depth":72,"links":784},[785,786,787],{"id":731,"depth":72,"text":732},{"id":749,"depth":72,"text":750},{"id":767,"depth":72,"text":768},[319,789],"News","Chron Engine is built to answer from the notes, PDFs, and atoms already in your workspace, instead of starting from a blank prompt.",{},"\u002Fen\u002Fblog\u002Fchron-engine-real-materials",{"title":726,"description":790},"en\u002Fblog\u002Fchron-engine-real-materials",[796,797,798,799],"AI is more useful when grounded in existing materials.","Chron Engine starts from workspace context, not blank prompts.","Atoms make retrieval and reasoning more coherent.","Users remain responsible for judgment and final structure.","Chron Engine is designed around the user’s real materials. Its value comes from reading workspace context: notes, PDF excerpts, atom references, mind maps, whiteboards, and tasks.","U6yyQhh__IV3PR-Fp7SeXu_hP7GFrdaGSh8a0fgcdYs",{"id":803,"title":804,"author":7,"avatar":8,"body":805,"categories":866,"date":867,"description":868,"extension":81,"image":869,"meta":870,"navigation":84,"path":871,"premium":86,"seo":872,"stem":873,"takeaways":874,"tldr":879,"__hash__":880},"blog\u002Fzh\u002Fblog\u002Fdesktop-early-access.md","Chronnote 桌面版内测说明",{"type":10,"value":806,"toc":861},[807,811,814,825,829,832,843,847,850],[13,808,810],{"id":809},"内测包含什么","内测包含什么？",[18,812,813],{},"内测让用户提前尝试围绕原子、阅读、白板、导图和 AI 辅助展开的桌面工作流。重点是来自真实知识工作的反馈。",[22,815,816,819,822],{},[25,817,818],{},"用户可以测试本地优先工作区。",[25,820,821],{},"Reader 与白板是核心流程的一部分。",[25,823,824],{},"反馈会影响更大范围发布前的产品优先级。",[13,826,828],{"id":827},"为什么从桌面端开始","为什么从桌面端开始？",[18,830,831],{},"桌面端更适合验证深度知识工作，因为用户需要阅读、书写、对照、排列和规划。移动端可以在核心模型稳定后继续推进。",[22,833,834,837,840],{},[25,835,836],{},"PDF 阅读和白板更需要大屏空间。",[25,838,839],{},"长时间写作更适合桌面。",[25,841,842],{},"本地优先存储也更适合先在桌面验证。",[13,844,846],{"id":845},"早期用户应该如何反馈","早期用户应该如何反馈？",[18,848,849],{},"早期用户最值得反馈的是上下文在哪里丢失、原子引用哪里不清楚、Chron 引擎哪里没有用好已有材料。这比泛泛的功能请求更重要。",[22,851,852,855,858],{},[25,853,854],{},"工作流断点能暴露优先级。",[25,856,857],{},"引用困惑能定位模型问题。",[25,859,860],{},"AI 反馈最好绑定真实材料。",{"title":71,"searchDepth":72,"depth":72,"links":862},[863,864,865],{"id":809,"depth":72,"text":810},{"id":827,"depth":72,"text":828},{"id":845,"depth":72,"text":846},[709],"2026-04-22","整理桌面版早期用户最关心的内测入口、早鸟价格、版本节奏和下一轮工作流改进方向。","\u002Fimages\u002Fblog\u002Fpost-6.webp",{},"\u002Fzh\u002Fblog\u002Fdesktop-early-access",{"title":804,"description":868},"zh\u002Fblog\u002Fdesktop-early-access",[875,876,877,878],"内测重点是工作流反馈。","桌面端优先验证深度知识工作。","早鸟价格支持早期用户和持续开发。","社区反馈会影响后续产品迭代。","Chronnote 桌面版内测关注真实用户对原子工作区、Reader、白板、导图、待办和 Chron 引擎的反馈，再进入更大范围发布。","iEMyxbf4Au6_bgzMuHzLSlS209FIUhQTFS5d8cq1jjU",{"id":882,"title":883,"author":7,"avatar":8,"body":884,"categories":945,"date":867,"description":946,"extension":81,"image":869,"meta":947,"navigation":84,"path":948,"premium":86,"seo":949,"stem":950,"takeaways":951,"tldr":956,"__hash__":957},"blog\u002Fen\u002Fblog\u002Fdesktop-early-access.md","Chronnote Desktop Early Access Notes",{"type":10,"value":885,"toc":940},[886,890,893,904,908,911,922,926,929],[13,887,889],{"id":888},"what-is-included-in-early-access","What is included in early access?",[18,891,892],{},"Early access gives users a way to try desktop workflows built around atoms, reading, whiteboards, mind maps, and AI assistance. The focus is practical feedback from real knowledge work.",[22,894,895,898,901],{},[25,896,897],{},"Users can test the local-first workspace.",[25,899,900],{},"Reader and whiteboard workflows are part of the core loop.",[25,902,903],{},"Feedback informs product priorities before wider release.",[13,905,907],{"id":906},"why-start-with-desktop","Why start with desktop?",[18,909,910],{},"Desktop is the best place to validate deep knowledge work because users read, write, compare, arrange, and plan with more space. Mobile support can follow after the core model is stable.",[22,912,913,916,919],{},[25,914,915],{},"PDF reading and whiteboards benefit from larger screens.",[25,917,918],{},"Long writing sessions fit desktop workflows.",[25,920,921],{},"Local-first storage is easier to validate on desktop first.",[13,923,925],{"id":924},"how-should-early-users-give-feedback","How should early users give feedback?",[18,927,928],{},"Early users should report where context gets lost, where atom references feel unclear, and where Chron Engine could make better use of existing materials. These signals matter more than generic feature requests.",[22,930,931,934,937],{},[25,932,933],{},"Workflow breaks reveal product priorities.",[25,935,936],{},"Reference confusion identifies model issues.",[25,938,939],{},"AI feedback is most useful when tied to real materials.",{"title":71,"searchDepth":72,"depth":72,"links":941},[942,943,944],{"id":888,"depth":72,"text":889},{"id":906,"depth":72,"text":907},{"id":924,"depth":72,"text":925},[789],"What early users can expect from the desktop beta, early-bird pricing, and the next round of workflow improvements.",{},"\u002Fen\u002Fblog\u002Fdesktop-early-access",{"title":883,"description":946},"en\u002Fblog\u002Fdesktop-early-access",[952,953,954,955],"Early access is focused on workflow feedback.","Desktop is the first priority for deep knowledge work.","Early-bird pricing supports early users and ongoing development.","Community feedback shapes the next product iterations.","Chronnote desktop early access focuses on validating the atom workspace, Reader, whiteboard, mind map, tasks, and Chron Engine with real users before a broader release.","xUeDmRZz70muAd10aACHV_oKjKsy4hYrS2gxPioHl6Q",1781184123848]