> For the complete documentation index, see [llms.txt](https://docs.cosmik.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cosmik.network/semble/basic-concepts/connections.md).

# Connections

Connections in Semble link two pieces of content with a typed semantic relationship. Each connection has a **source** (A), a **target** (B), an optional **relation type** that describes how they relate, and an optional **note** for additional context.

<figure><img src="https://3266811452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCC62olUyfbqBWZOz06Pi%2Fuploads%2FWI0c4DL38oxpo6xzHz16%2Fimage.png?alt=media&amp;token=78486ffb-f635-4816-8b1f-cfa08aa36f22" alt=""><figcaption></figcaption></figure>

## Semble Connection Types

| Type              | Lexicon ID    | Description                                       | Example                                                             |
| ----------------- | ------------- | ------------------------------------------------- | ------------------------------------------------------------------- |
| Related (default) | `related`     | A is related to B in some unspecified way         | Paper A and paper B both deal with collective intelligence          |
| Supports          | `supports`    | A provides evidence or reasoning in favor of B    | Dataset A supports the findings of paper B                          |
| Opposes           | `opposes`     | A provides evidence or reasoning against B        | Evidence A contradicts claim B                                      |
| Addresses         | `addresses`   | A responds to or answers B                        | Paper A addresses the open question posed in paper B                |
| Helpful           | `helpful`     | A is helpful for contextualizing/understanding B  | Essay A offers a thoughtful critique of research paper B            |
| Explainer         | `explainer`   | A explains or summarizes B for a broader audience | Thread A walks through the key findings of paper B                  |
| Leads to          | `leads_to`    | A led me to B — a trail segment worth walking     | Listening to podcast A led me to find book B                        |
| Supplements       | `supplements` | A is supplemental material for B                  | Dataset A accompanies and supports the methods described in paper B |
| References        | `references`  | A mentions or references B                        | Podcast episode A references and discusses paper B                  |
| Same as           | `same_as`     | A refers to the same underlying entity as B       | A and B are two URLs hosting the same paper (same DOI)              |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cosmik.network/semble/basic-concepts/connections.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.