Hi HN — I’m exploring an idea and would love your feedback.
I’m a builder and user of Obsidian, validating a concept called Concerns. Today it’s only a landing page + short survey (no product yet) to test whether this pain is real.
The core idea (2–3 bullets):
- Many of us capture tons of useful info (notes/links/docs), but it rarely becomes shipped work.
- Instead of better “organization” (tags/folders), I’m exploring an “action engine” that:
1.detects what you’re actively targetting/working on (“active projects”) 2.surfaces relevant saved material at the right moment 3.proposes a concrete next action (ideally pushed into your existing task tool)
My own “second brain” became a graveyard of good intentions: the organizing tax was higher than the value I got back. I’m trying to validate whether the real bottleneck is execution, not capture.
Before writing code, I’m trying to pin down two things:
- Project context signals (repo/PRs? issues? tasks? calendar? a “project doc”?)
- How to close the loop: ingest knowledge → rank against active projects → emit a small set of next-actions into an existing todo tool → learn from outcomes (done/ignored/edited) and optionally write back the minimal state. The open question: what’s the cleanest feedback signal without creating noise or privacy risk? (explicit ratings vs completion events vs doc-based write-back)
... continue reading