Comment by 41d
4 hours ago
I completely agree, and I've been thinking about how to utilize the knowledge I've accumulated recently. In the end, I settled on the mundane solution of saving it locally in YAML or JSON, and now I'm considering how to get the AI to suggest and utilize it, and where and when to execute it. I think this is a great idea, and I'd love to be on the waitlist when the landing page is ready, so please let me know.
1. search & execution The problem is that if your goal is to accumulate knowledge or take notes, and you then want to use that knowledge to do something, you have to search for it yourself, and you have to think about the text in the first place. The search may not find anything that has a similar meaning to the text, or similar events, and as a result, you are unable to put it into action.
2. calendar
3. migration cost.
Good luck.
Thanks — this is extremely helpful, especially the constraints: you want semantic search + “where/when to execute”, calendar as a key context source, and migration cost as a hard friction point.
YAML/JSON as a local knowledge store is a nice wedge too: it keeps things portable and makes “AI suggestions” easier to reason about.
Re the waitlist: the landing page is up now (https://concerns.vercel.app), and you can leave an email there. I’ll make sure you get an update when there’s something testable.
One quick follow-up: if you could get only one capability first, would you pick
a) semantic recall (find related knowledge without exact keywords), or
b) a daily “top 3” plan generated from calendar + your knowledge store (pulled on demand, no interruptions)?
Details are in my HN profile/bio if you want more context.