|
|
|
|
|
by item007
182 days ago
|
|
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. |
|
Of those two, I'd choose A.
I'm looking forward to hearing more.