WitNote · Local Files Knowledgebase is part of Hooosberg's public product diary for WitNote. It turns a real build step into a searchable case study for international readers.
A local-first writing workspace for macOS and Windows, built around private notes, Markdown, Ollama, local models, and OpenAI-compatible APIs.
The original Chinese article was published on 2026-06-19 under Architecture. It focuses on 把文件夹当知识库，意味着导入、索引、预览、权限和同步都要重新设计。
The reusable learning angle is AI writing tools, Local-first architecture, Multi-model integration, App Store launch. The diary format is deliberately practical: context, decision, implementation boundary, review impact, and what another builder can reuse.
This English page is generated from the same public product facts as the Chinese site. It is meant to be indexable and useful now, while still leaving room for later hand-polished translation of the full Chinese narrative.
Context
This entry belongs to the WitNote build series. It should be read as one stage in a larger product journey, not as an isolated announcement.
The site keeps success cases and failure cases together because both create reusable judgment.
Implementation boundary
Relevant product capabilities include WebLLM, Ollama, and OpenAI-compatible APIs, Markdown and TXT editing, Local folders as knowledge bases, Writing roles, completion, and focus mode. The diary explains how these capabilities are selected, constrained, reviewed, or turned into launch material.
Privacy and trust
Notes stay in the local folder selected by the user. When local models are used, writing content does not leave the device.
For an indie product matrix, trust is built through many small facts: local data boundaries, review status, support links, honest postmortems, and stable canonical pages.
What another builder can reuse
Another builder can reuse the pattern: start with a narrow product promise, make the privacy boundary inspectable, connect every public page to a real download or repository, and turn the launch process into a searchable article.
That is why the diary sits next to the product page. The product builds trust, and the diary teaches the path that made the product possible.