> For the complete documentation index, see [llms.txt](https://neutron-4.gitbook.io/neutron-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neutron-4.gitbook.io/neutron-docs/overview/key-concepts.md). # Key Concepts myNeutron is built around a few simple but powerful ideas. *** #### 1. Seeds Seeds are Saved Pieces of Knowledge.\ They capture web pages, highlights, files, or emails.\ Each Seed is indexed and stored for quick, intelligent recall. *** #### 2. Combined Context A Combined Context is a focused group of Seeds.\ You merge related Seeds into one clean brief that is ready for any AI.\ Use it inside the dashboard or paste it directly into your preferred AI tool. *** #### 3. myNeutron Assistant The myNeutron Assistant understands your Seeds and Combined Contexts.\ You can search, summarize, and explore your knowledge directly inside myNeutron. *** #### 4. Model Context Protocol (MCP) MCP is the secure bridge that connects your knowledge to AI tools such as Claude, Cursor, VS Code, and Windsurf.\ It lets your AIs access your context even if they do not support plugins. *** > **Core loop:** Capture → Combine → Query → Reuse --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://neutron-4.gitbook.io/neutron-docs/overview/key-concepts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.