Case: turning scattered company files into a knowledge base
- Colin Li
Material: CodingMind's operating files, spread across a laptop and Google Drive, including legal files and partner agreements. About 1.4 GB, as said in class.
The tool was given goals, not steps: future marketing material and partnership agreements should have references to draw on, and outdated material should be updated. It chose its own way to organise them.
It took about half a day. The output is a set of Markdown files and an index. The index is mainly for the tool to read: where each kind of information is and how the parts connect. The Markdown files can be read in Obsidian.
One use: a 2024 school introduction used California data. Asked to update it, the tool found Seattle data in the registration spreadsheets and rewrote it.
This demonstration had the tool read files beyond one project folder. That is the advanced tier on the course's reference page: the work gets its own folder under git; name specific folders, never the whole home folder; decide first what may go to the provider. Beginners follow the Session 1 rule: only the project folder.
Question from class: can files leak? Answer: on personal plans, data is uploaded to the provider's servers.