sethiaakash04

3 ms·

1.
by sethiaakash04 2mo ago
Hi, we would love your feedback and what more you expect from your context layer. Please feel free to reach out at sethiaakash04@gmail.com
2.
by sethiaakash04 3mo ago
It's deterministic math: when two observations agree, our confidence goes up. If they conflict, confidence drops. Over time, a decay function lowers confidence as facts get older.
3.
by sethiaakash04 3mo ago
It's a waterfall sequence of hard identifiers such as email, LinkedIn URL, domain, and CRM ID and it only accepts exact matches and does not use fuzzy search. This approach works for most situations. If there is still no match, the sys
4.
by sethiaakash04 3mo ago
Exactly, CRM is for your business records and the context graph is for aligning your agent!
5.
by sethiaakash04 3mo ago
The most recent observation is used as the claim. If there are conflicting observations, each one lowers the confidence score, but the newest still takes priority. The only exception is that CRM fields follow their own priority order. The h
6.
by sethiaakash04 3mo ago
CRMs are built for humans to update records. Nous is built for AI agents to read and write context. It stores observations, derives claims, tracks confidence and freshness, and gives agents one API instead of making them coordinate multiple
7.
by sethiaakash04 3mo ago
It's open source under the AGPL license, so you can self-host it. Happy to discuss identity resolution, the epistemic model (observations to entities to claims), and answer questions.
8.
Show HN: Nous – give GTM agents one context graph across your tools(github.com)
10 points by sethiaakash04 3mo ago|13 comments