How dotdotgod Query Finds Relevant Documents from a Natural-Language Question

A documentation table of contents is the fastest retrieval method when an agent knows the relevant role and path. A user's question may use different language from a document's filename, and the question and document may even be written in different human languages. dotdotgod query searches locally for document passages that are semantically close to a natural-language question and routes the agent to the maintained sources worth reading. Documents remain the source of project memory. Embeddings and search results are derived retrieval data that connect a question to those sources. Start from Meaning When the Path Is Unknown Consider this question: Why does Load exclude old plans from its default context? The relevant explanation may live in LOAD_PROJECT.md, MEMORY_AREA_CONFIG.md, or a document about context curation. A filename search may not connect “old plans” from the question with terms such as archive, local memory, or stale in the documents. query accepts a