10 pointsby sethiaakash045 hours ago5 comments
  • sethiaakash045 hours 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.
  • 5 hours ago
    undefined
  • binnaniaditya14 hours ago
    How are you solving identity resolution? What happens when two people share a name at the same company?
    • sethiaakash044 hours 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 system creates a new entity instead of making an incorrect guess.
  • 1209vikas4 hours ago
    How do you handle conflicting facts from two sources when you are extracting the observations?
    • sethiaakash044 hours 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 human-entered data comes first, followed by enriched data, then inferred data. For all other cases, the newest observation is used.
  • bennetglinder15 hours ago
    how is this different from just giving my agent access to my CRM?
    • sethiaakash044 hours 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 tools.
      • bennetglinder14 hours ago
        so I would still need a CRM but agents would use the context graph?
        • sethiaakash044 hours ago
          Exactly, CRM is for your business records and the context graph is for aligning your agent!