# Connections We have a few different types of `Connections` that help characterize [Entities](/about/elements/data/entities.md) in the [Graph](/about/elements/graph.md). {% hint style="info" %} [Connections](/about/elements/data/connections.md) **and** [Entities](/about/elements/data/entities.md) **are the two foundational building blocks of the** [Data](/about/elements/data.md). {% endhint %} ## Links We are currently exploring these `Connections` and may add others. As with `Tags`, there is a lot to debate and try to understand, so we welcome [Feedback](/about/feedback.md). In the `Data`, these types of `Connections` are called `Links` to differentiate from actual `Connections` between `Entities`. ### Org Chart {% hint style="success" %} An **`Org Chart`** connection links parent and child in an organizational hierarchy. {% endhint %} Almost all of the existing maps look at this dimension, which is important, especially for `Government` `Organizations` (which are subject to the views of their parent organizations and leadership, not to mention funding). > **EXAMPLE**: The `Defense Innovation Unit` has an `Org Chart` `Connection` to the `Office of the Undersecretary of Defense for Research and Engineering (OUSD(R&E))`, which is its parent in the organizational chart. ### Collaboration {% hint style="success" %} To be in **`Collaboration`** is to have mutually-supportive shared efforts, which could link any number of **`Entities`**. {% endhint %} While somewhat flexible (and, thus, subject to change or redifinition) we wanted to include this type of connection in order to demonstrate ties that we know exist and make a difference. > **EXAMPLE**: `Platform One` `Collaborates` with `Black Pearl` even though the prior is an `Air Force` `Organization` and the latter is a `Navy` `Organization`. ### Funding {% hint style="success" %} **`Funding`** identifies a connection between an **`Individual`** or **`Organization`** and another **`Organization`**, **`Group`**, or **`Activity`**.. {% endhint %} This type is useful for understanding non-`Org Chart` `Connections` that many might be familiar with, but not fully understand. > **EXAMPLE**: The `Defense Innovation Unit` has a `Funding` connection to `Saildrone`, a `Commercial` `Organization`. ### Research {% hint style="success" %} The **`Research`** link connects an **`Individual`** or **`Organization`** to an **`Organization`**, **`Group`**, or **`Activity`**. {% endhint %} As the name suggests, this . > **EXAMPLE**: `RAND` has `Research` links to the `US Army` and `US Air Force`. ### Member {% hint style="success" %} A **`Member`** **`Connection`** links **`Entities`** through participation in a membership function. {% endhint %} This link type is useful for understanding non-`Org Chart` `Connections` that many might be familiar with, but not fully understand. As with [#contributor](#contributor "mention"), it is unlikely to be receive [Verification](/about/elements/data/verification.md), but may be helpful for some working on their own `Graph` views. > **EXAMPLE**: The `Air Force` is a `Member` of the `Joint Chiefs of Staff`. ### Contributor {% hint style="success" %} **`Contributor`** links connect an **`Individual`** to another type of **`Entity`**, such as a **`Group`**, **`Activity`**, or **`Repository`**. {% endhint %} One of the more prolific types of `Individual` links, `Contributor` allows for flexibility between `Entities`, opening up a number of different `Graph` opportunities. > **EXAMPLE**: As an `Author`, `Jay Long` is also a `Contributor` to the `Modern War Institute`, an `Organization` that maintains a `Repository`. {% hint style="warning" %} ***NOTE**: The most likely source of a* **`Contributor`** *link will be from the* **`Individual`** *in question themselves. As such, it is unlikely, even for public* **`Graph`** *views, that such links will receive* [Verification](/about/elements/data/verification.md)*, if nothing else due to quantity.* {% endhint %} ### Author {% hint style="success" %} The **`Author`** link connects an **`Individual`** with an **`Artifact`**. {% endhint %} Writing is an important part of national security innovation, with ideas penned by some spawning `Activities` generated by others. This link type, similar to [#founder](#founder "mention")and [#contributor](#contributor "mention"), is best suited for evaluating the graph of an `Individual`. > **EXAMPLE**: Writers `August Cole` and `P.W. Singer` each have an `Author` link to the book `Ghost Fleet`, an `Artifact`. ### Founder {% hint style="success" %} A **`Founder`** link ties an **`Individual`** to an **`Organization`**, **`Group`**, or **`Activity`**. {% endhint %} This link is best suited for understanding the impact of `Individuals` on the broader national security innovation ecosystem, in concert with the [#contributor](#contributor "mention") link. > **EXAMPLE**: `Enrique Oti` has a `Founder` connection to `Kessel Run`. {% hint style="warning" %} ***NOTE**: The goal of the* **`Founder`** *connection is to show a specific type of* **`Contributor`**, but may be applied more broadly than to only a couple of **`Individuals`**, depending on the situation. We are also sensitive to "serial fake founders" that seek inappropriate credit and may remove this link type if it proves problematic, as with any link type. {% endhint %} ### DEF Community {% hint style="success" %} The **`DEF Community`** link connects **`Entities`** in a specific configuration for graph visualizations. {% endhint %} This is DEF specific, helping create graph views that summarize the ways DEF links different national security elements as a way of illustrating its value and potential to the community, or opening opportunities for discussion. It is likely to change over time. > **EXAMPLE**: In one `Graph` view, the `Air Force` has a `DEF Community` link to the `Defense Entrepreneurs Forum` and another `DEF Community` link to `AFWERX`. --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://docs.natsec.io/about/elements/data/connections.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.