Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agentic Resource Discovery Specification

agenticresourcediscovery.org

Post reply on HN
Print view View original

21–23 of 23 posts

Re: Agentic Resource Discovery Specification

#21

Post by gavinray »

xtiansimon wrote: post #20
gavinray wrote: post #3

I work at a company with an LLM-adjacent tool. The best solution we could find for this problem was a combination of a Wiki + "Saved Programs" (executable scripts). When you ask a question, the system does a fuzzy Wiki search to see if any topic has relevant info. Wiki links serve as "graph edges" that form a Knowledge Graph. So lets say I ask "What products from the FOOBAR API sold least last month?" The agent would…

Does this solution use a private/local LLM or something else? Sorry if the answer is obvious. I’ve just started considering this for an internal wiki to my company.

We use Opus/Codex models

Re: Agentic Resource Discovery Specification

#22

Post by smcleod »

gavinray wrote: post #3

I work at a company with an LLM-adjacent tool. The best solution we could find for this problem was a combination of a Wiki + "Saved Programs" (executable scripts). When you ask a question, the system does a fuzzy Wiki search to see if any topic has relevant info. Wiki links serve as "graph edges" that form a Knowledge Graph. So lets say I ask "What products from the FOOBAR API sold least last month?" The agent would…

Similar conclusion I've come to. For all the complex RAG and many SaaS startups selling knowledge engines - what we keep falling back to is simple a wiki (markdown) + simple tools to solve problems and help answer questions programmatically where possible. Cheap, fast, low complexity and no lock-in.
Post reply on HN