# Project Overview What it is we say that we do here and how it works. {% hint style="info" %} **Welcome!** :wave: **Thanks for your interest in national security and innovation.** This site documents our efforts for this project so that you can understand and engage with it. {% endhint %} {% hint style="success" %} This project is now in the public [Beta](/release-notes/beta) phase, which means everything is live and we're picking up speed. Your thoughts and ideas are welcome either at or in the feedback form on NationalSecurityInnovation.org. :pray: {% endhint %} ### Structure of Docs There are a number of sections you can access to learn more about the project - each section has an overview page just like this one to further explain what you can find there, and you can also use the `Search` feature or sidebar to navigate around: * [About](/) (where you currently are) explains the basics of this project and associated features. * The [Frequently Asked Questions](/frequently-asked-questions/faq-overview) section does just what you might expect: identifies and answers common questions we receive about the project. * [Release Notes](/release-notes/release-notes-overview) are the updates we make to the project over time so you can understand where changes take place (and also planned features). * We use the [Workflow](/workflow/workflow-overview) section to document step-by-step instructions and tutorials for each segment of the project to increase sustainability by making it easy to contribute. * Lastly, [Education](/about/goals/education) captures key elements underpinning the project, some of which are referenced elsewhere as foundational - great references. ### Navigation There are a few different ways to navigate this guide: * Use the `Sidebar` to scroll through and expand different sections * Click on `Links` to different sections in order to hop right there * Type something into `Search` and check out the results Want to get nerdy about this guide? Check out the [GitBook](/learning/tools/gitbook) section to learn more about this platform, otherwise keep on reading! # Story How we got started with this project. The [**Defense Entrepreneurs Forum**](https://www.def.org) (DEF) launched the **Project on Innovation in National Security** (PINS) in 2022 to help address some of the problems we saw in the national security community: 1. **Understanding the innovation ecosystem**, including all of its `Organizations`, `Groups`, `Activities`, `Artifacts`, and `Individuals`. 2. **Data literacy and related data applications**, such as automation and various forms of artificial intelligence. 3. **Supporting a learning mindset** through iterative and exploratory approaches that encourage experimentation and new ideas. > *Innovation is such a buzzword that using it without context or purpose can actually be more harmful than helpful.* With an increase in both resourcing for and evaluation of innovation efforts in defense, intelligence, and related national security fields, we believe this understanding is paramount to improving outcomes. Because our tagline is to inspire, connect, and empower, we started asking ourselves the question "*How might we?*" about this observed challenge and realized one potential starting point was staring us right in the face: [a network graph created in 2018](https://kumu.io/aflazo/def-innovation-ecosystem-map#def-ecosystem-map) by several of our community members. Thus was born this project, a data set and associated applications **designed to help people explore, understand, and build a culture of innovation** in national security through individual action. **Most of this project is free and open-source data** in keeping with the values of our community - it is available for reuse and remixing under the conditions of our [License](/about/support/license). We hope that you are as interested in what this project can contribute as we are and welcome your feedback and ideas! Check out the [Workflow](/workflow/workflow-overview) section to find out ways to get involved and feel free to follow us and our [Partners](/about/support/partners) on [LinkedIn](https://www.linkedin.com/company/defenseentrepreneurs/), [Twitter](https://www.twitter.com/defcommunity), [YouTube](https://www.youtube.com/defenseentrepreneurs), and more! # Goals What we hope to achieve with this project. You know from our [Story](/about/story) that this project is all about innovation in national security, two words about which there is much debate and very little understanding, much less concrete value or clear opportunities. For that reason, we have a few primary goals that we hope to achieve or at least advance toward with this work: 1. Increase **understanding** of the national security innovation ecosystem. 2. Improve **data literacy** of national security stakeholders, especially government employees, in order to support further innovation. 3. Support a **learning mindset** and **opportunities to experiment** by integrating a variety of frameworks for building and questioning. These are certainly not very specific goals, nor are they very measurable, so it is worth taking a look at each one individually to see how they might be further refined and measured. ### Increase Understanding of the Ecosystem When we think about this overarching goal, our minds immediately go to users and value: * Who do we want to better understand the ecosystem? * Why is increased understanding valuable to them? * How will we create or capture value to meet that need? Our hypotheses about these different questions are captured in [Use Cases](/about/use-cases), but we plan to return and add more SMART-style goals. We expect [Feedback](/about/feedback) will help with this as well. ### Improve Data Literacy The topic of data literacy is gaining traction within the national security community as more and more users seek to apply data-enabled capabilities to their activities, be they analytics or artificial intelligence or security factors. Our experience (and also [Research](/learning/research)) strongly supports the need for improved data literacy to adapt to the changing global environment, especially in national security and in developing innovative approaches or solutions. More and more we are overcome by data and unable to advance (especially those of us in [Government](/about/use-cases/government)) because we may lack access to simple [Tools](/learning/tools) or our understanding of seemingly technical [Concepts](/learning/concepts) is not well-founded in [Research](/learning/research). We may not have experience with [Courses](/learning/courses) that could address this and might feel overwhelmed at the number and variety of options that are available. By taking a project-based approach, the creation of which adds value on its own, we hope to inspire, connect, and empower people to seek out opportunities to improve their knowledge, gain experience working with data and associated technologies, and bring others with them. ### Support a Learning Mindset We feel that a learning mindset is important to support broader innovation initiatives because, as you may have experienced yourself, innovative efforts often fail, but failure and national security have a history of not playing well together (turns out national security is a bit of a bully). By setting this out as a goal, we hope people will take these failures and start to ingest them as learnings instead of character flaws. Not all failure is good, to be sure, and we do not believe that there is any one-size-fits-all approach to innovation or a "fail fast" mentality that will be easily and universally adopted. It takes [People](/about/goals/people) for that kind of change to occur, and it is those same [People](/about/goals/people) who are also [Contributors](/about/support/contributors) or even just consumers of this project that will be the change agents needed to keep moving us forward in a very complex world. We think that the [Education](/about/goals/education) opportunities are important, not just to [#improve-data-literacy](#improve-data-literacy "mention"), but for personal growth and a sense of fulfilment regardless of one's job or position. # People Who powers this project. We recognize that this project, as a crowdsourced initiative, is not possible without the support of people. This works out well, since people are a very key part of our goals. When we think about people, we try to keep an open mind, wanting to lower barriers to participation so that even those who are skeptical have the opportunity to contribute or share their thoughts and ideas. > *"There is one body that knows more than anybody, and that is everybody."* - [Talleyrand](https://www.google.com/books/edition/A_Dictionary_of_Thoughts/zlMxAAAAIAAJ?hl=en\&gbpv=1\&dq=“There+is+one+body+that+knows+more+than+anybody,+and+that+is+everybody”\&pg=PA324\&printsec=frontcover) While we offer the option for people to be recognized as [Contributors](/about/support/contributors), we recognize that not everyone will want this recognition, either by name or pseudonym. People, it turns out, have many different preferences, which makes all of this that much more messy and fun. {% hint style="info" %} If this idea of people beign at the center of our project intrigues you, be sure to check out [Learning](/learning/learning-overview) and [Ethics](/about/support/ethics), as those sections are very human-centric {% endhint %} # Education Why the project matters. We know that seeing data contextualized is great, but believe that a foundational understanding of that data is much more important. We also know that such data literacy is sorely missing in the national security community, stifling innovation for lack of comfort brought on by familiarity or existing use cases (what you may hear referred to as "warm fuzzies" in some circles). **One of our explicit aims for this project is to increase data literacy and related confidence across the national security community, which is an educational activity.** Our hope is to work with [Partners](/about/support/partners) and leverage the [Learning](/learning/learning-overview) opportunities already available to connect people with a desire to do so to areas of the project where they can practice. In our experience it is much easier to learn when you have a problem to which those new concepts can be applied, and this project is hopefully one that will inspire people to take a leap and challenge themselves. {% hint style="info" %} If you like this idea and want to get involved, please check out the various sub-elements in the [Learning](/learning/learning-overview) section and feel free to [Contact Us](/about/contact-us) as well! {% endhint %} # Iteration When people use learning to remix data. In starting this project we knew a few things and hypothesized about many others. We also realized that all of those ideas, assumptions, and hypotheses might be completely wrong (e.g. the [Use Cases](/about/use-cases) we set out) and know the only potential outcomes from that reality are: 1. Allow the project to fail by locking ourselves into something with no [Feedback](/about/feedback); 2. Start slowly with something that can be changed and then add features or tweaks over time. We are taking the latter approach, which will be an iterative process of rolling out different [Elements](/about/elements) of the project over time (see [Feature Timeline](/release-notes/feature-timeline)) and then engaging [Contributors](/about/support/contributors) through the [Workflow](/workflow/workflow-overview) process to ensure we are sustainable. # Elements Your starting point for learning to use this project. **At its heart, this project is all about** [People](/about/goals/people) **and** [Education](/about/goals/education)**.** Why those two and not, say, [Data](/about/elements/data)? A couple of reasons: 1. First, we know from research and our own experience that data is a tool used by people for outcomes; building this project only on data would miss the opportunity space offered by the adjacent possible that people discover by asking critical questions. 2. Second, we believe that a mindset shift toward learning will enable a culture of innovation (our mission) in ways that simply having more data or information will not. When starting out, we recalled all the frustrations many of us experienced in our daily work (especially government employees) and determined that it would not suffice to let a particular visualization tool drive applications. You may not *think* you care about the data (though you *should*), but we want to be clear that this is where we start: people and data. What you probably *do* care about, especially if you're reading this page, is **how you can use the project**. To that end, please continue reading to learn more about its core features and future development we are considering, or skip ahead to [Use Cases](/about/use-cases) to see our hypotheses about how someone like you might benefit. * [Data](/about/elements/data): What powers the project. * [Graph](/about/elements/graph): How the project data is connected. * [Map](/about/elements/map): Where to find the project in your neighborhood. * [Timeline](/about/elements/timeline): How the project data shows evolution over time. # Data What we use to power this project. {% hint style="info" %} If you are curious about our reasoning behind the certain aspects of the **`Data`**, check out our [What criteria do you use to collect project data?](/frequently-asked-questions/what-criteria-do-you-use-to-collect-project-data) page in the [Frequently Asked Questions](/frequently-asked-questions/faq-overview) section. {% endhint %} The baseline product of this project is data, sourced from individuals like you, which feeds the [Graph](/about/elements/graph), [Map](/about/elements/map), and [Timeline](/about/elements/timeline) (along with any future efforts or forks). ### Initial Data Set We wanted to start simply, so we took a play from all the existing efforts or maps we could find and dumped everything into [Google Sheets](/learning/tools/google-sheets) to get started:
Data :link: [**Data - Project on Innovation in National Security (Google Sheets)**](https://docs.google.com/spreadsheets/d/1dj9LztlbBCB7BPCNpTHd8ko_Uz1pcLQDjTOfEYJH6Ik/edit#gid=1534616606) Click the above link to open [Google Sheets](/learning/tools/google-sheets) and view the `Data` - the first page will be a `README` and then you can view other sheets with different [Elements](/about/elements).
You will notice (after opening the `Data`) that there are tabs on the bottom to explore [Entities](/about/elements/data/entities) and [Connections](/about/elements/data/connections) - feel free and do that while checking out the [Graph](/about/elements/graph) to get a sense of how it works (HINT: it's not that complicated). ### Future Data Sets We know that Google Sheets is going to start running into issues when we start working with a lot more data and types of [Entities](/about/elements/data/entities) (not to mention addressing the [Dimensionality](/learning/concepts/dimensionality) problems and figuring out [Tags](/about/elements/data/tags)). We have some [Partners](/about/support/partners) in mind to try and help with this, but, for now, we are just hoping to give a little bit of a sense for how data is structured and then move forward with better infrastructure and tools as we go. If you have ideas or questions, but all means, [Contact Us](/about/contact-us)! # Entities The Organizations, Communities, Individuals, Activities, Artifacts, and Repositories that make-up this project. Trying to understand [Data](/about/elements/data) in this project requires a fundamental understanding of [Data Structures](/learning/concepts/data-structures) and [Dimensionality](/learning/concepts/dimensionality), but since you may not want to jump straight into [Learning](/learning/learning-overview) or [Concepts](/learning/concepts) we'll just summarize [Entities](/about/elements/data/entities) as follows: {% hint style="info" %} [Entities](/about/elements/data/entities) **and** [Connections](/about/elements/data/connections) **are the two foundational building blocks of the** [Data](/about/elements/data). {% endhint %} We go into a bit more detail about [Entities](/about/elements/data/entities) in the following two sections: * [#types-of-entities](#types-of-entities "mention") - variations in what we use to ground [Connections](/about/elements/data/connections) * [#filterable-attributes](#filterable-attributes "mention")- attributes that we use with visualizations * [#non-filterable-attributes](#non-filterable-attributes "mention") - attributes that help us learn more ## Types of Entities When reviewing the existing work, we realized that there were a few different types of building blocks that characterized the national security ecosystem as it pertains to innovation. Below you will find each of them listed and defined with an example or two for context. ### Organization {% hint style="success" %} An **`Organization`** is a formally established body of individuals with documented responsibilities. {% endhint %} We recognize that this definition may be obvious, but want to set everyone up with a common understanding of our terms. To simplify the framework across different `Categories` we did not choose any `Entities` that might be used more specificially in a given context (e.g. `Staff` to indicate what type of `Entity` a `Government` `Organization` is, or `Startup` to indicate a more specific `Commercial` `Entity`). We make up for this choice by using [#tags](#tags "mention"), which are more modular and allow for simple `Entity` resolution with more nuanced contextual references (e.g. you can filter the [Graph](/about/elements/graph) by all of the `Organizations` with `Staff` or `Startup` as one of the [#tags](#tags "mention")). {% hint style="warning" %} ***Note:** One of the beneficial aspects about starting with* [Data](/about/elements/data) *and being very specific about what we mean by different terms is that we can more easily make changes and updates based on* [Feedback](/about/feedback)*. We will continue to evaluate this* `Type` *over time.* {% endhint %} > **Example:** The `Defense Innovation Unit` is a `Government` office, `Stanford University` is an `Academic` institution, `Saildrone` is a `Commercial` company, and the `RAND Corporation` is a `Non-Profit`. Each is an `Organization` distinguished by [#categories](#categories "mention"). ### Community {% hint style="success" %} **`Communities`** are similar to **`Organizations`**, but more informal. They are a collection of **`Individuals`**. {% endhint %} This type is valuable because some meaningful contributors to innovation in national security do so within such informal networks and relationships. Sometimes these evolve into more formal structures or `Organizations`, sometimes they originate in such `Organizations` or emerge from `Activities` - regardless, they will typically be more amorphous and less defined, yet worth characterizing. Additionally, a project might be understood in some ways as a `Community` that probably includes `Activities` and produces some sort of `Artifact`. > **Example:** The `Federal Innovators Salon` is gathering of government employees focused on innovation, but not a formal `Non-Profit` `Organization`. It also holds `Events`, which may or may not generate `Artifacts`. ### Individual {% hint style="success" %} An **`Individual`** is a person involved in an **`Organization`**, **`Community`**, or **`Activity`** that is deemed important as a **`Data`** element and either has publicly accessible information available or consents to be included. {% endhint %} Social network analysis (SNA) is a very useful tool in understanding multiple facets of a movement or organization (in fact, [Kumu](/learning/tools/kumu) has a dedicated feature for just this purpose). While the [Graph](/about/elements/graph) will support baseline network analysis across organizations, some of which is representative of underlying social networks, we know from our personal experience that the web of personal ties is much different than the lines draw by organizaitonal charts. We see a couple use cases for this `Entity` type, both of which have pros and cons: * **Public individuals**, such as government leaders or those in key organizational positions, whose tenure and activities can help enrich an understanding of why certain activities did or did not take place. The down-side of this is potentially giving too much weight to said individuals. * **Private individuals**, typically those of lower power or who do not have a public-facing role, whose actions and connections often drive much of the ground-up drive behind innovative efforts. A potential con of this is not being able to represent enough of such individuals to accurately capture a network due to privacy concerns. {% hint style="warning" %} ***NOTE**: While we recognize that* **`Individuals`** *are important to understanding certain aspects of innovation in national security, we want to be thoughtful about how they are integrated (for example, public vs. private figures and contact information).* {% endhint %} > **Example:** `Hondo Guerts` is an `Individual` whose tenure as the Assistant Secretary of the Navy for Research, Development, and Acquisition included the establishment of `NavalX`, a `Government` `Organization`, may benefit those studying innovation in national security. ### Activity {% hint style="success" %} An **`Activity`** is executed by an **`Organization`**, **`Community`**, or **`Individual`** to achieve a goal or end state. {% endhint %} There are many different activities tied to national security as well as innovation. Some are linear processes, some are cycles, others are more like projects or events, but each must be initiated to achieve an outcome and comprise actions, not just individuals (which is what differentiates an `Activity` from a `Community`, since they are otherwise very similar). > **Example:** The `Defense Entrepreneurs Forum` annual conference is an `Activity` geared toward the `Organization` mission of inspiring, connecting, and empowering people in the national security community. ### Artifact {% hint style="success" %} An **`Artifact`** is produced as part of an **`Activity`** by an **`Organization`**, **`Community`**, or **`Individual`** and contributes to an understanding of innovation in national security. {% endhint %} `Artifacts` are the sibling `Entities` to `Activities` and allow for a more nuanced understanding of an `Organization`, `Community`, or `Individual` in the form of physical or digital remnants. > **Example:** `General Charles Brown` is an `Individual` whose tenure as Chief of Staff of the Air Force and associated `Artifact` generation in the form of memos to "Accelerate Change or Lose" may benefit those studying innovation in national security. [Research](/learning/research) is also useful as `Artifacts`. ### Repository {% hint style="success" %} A **`Repository`** is an **`Artifact`** collection tied to a national security-relevant **`Organization`**, **`Community`**, **`Individual`**, or **`Activity`**, especially one where the content is non-public. {% endhint %} `Repositories` store information, some of which may be in the form of `Artifacts`, though most will be so large or non-public that specific `Artifacts` are unlikely to be linked. `Repositories` are typically a data set or database, though the exact structure may be non-public or unknown. > **Example:** `AFWERX` is a `Government` `Organization` that contracted with `Mobilize`, a `Commercial` `Organization`, to create `Vision`, a non-public web platform that includes a `Repository` of `US Air Force` innovation projects and activities, among other data holdings and features. {% hint style="warning" %} ***NOTE**: There are likely to be* **`Repositories`** *whose existence or details would be contrary to this project's goal of supporting national security, so we want to approach any such inclusions holistically (for example, the inclusion of links or other potentially sensitive information that is not publicly available).* {% endhint %} ## Filterable Attributes Now that we have an understanding of what [Entities](/about/elements/data/entities) are, we need to dig into a bit more what characterizes them - for this, we have a few different features or attributes, the most importance of which we use as filters to modify different visualizations in the [Graph](/about/elements/graph), [Timeline](/about/elements/timeline), and [Map](/about/elements/map). ### Categories {% hint style="success" %} A **`Category`** is essentially an attribute with a singular value used to help organize or filter different **`Entities`**. {% endhint %} More is covered on these in the dedicated ensuing [Categories](/about/elements/data/categories) section, but for the purpose of this project, an `Entity` can only have one `Category`. Because this gets into serious questions about [Dimensionality](/learning/concepts/dimensionality) and even has potential implications for [Ethics](/about/support/ethics), we dive deeper into it in the next section. The important thing to understand is that, like [#organization](#organization "mention") and [#tags](#tags "mention"), this attribute is malleable to meet the needs of the project. While we are defaulting to a more robust set of [#tags](#tags "mention") and fewer [#categories](#categories "mention"), this is largely driven by limitations of [Kumu](/learning/tools/kumu), which only allows one set of multi-select fields. The option to sub-divide [#categories](#categories "mention") exists (e.g. making `Government - Staff` an option instead of just `Government`), but we want to give some time to work with users before diving too far into the weeds, since we know whatever the project starts with will inevitably change (and the [Categories](/about/elements/data/categories) page will be the one-stop shop for any such changes to be documented). > **Example:** The `Defense Innovation Unit` cannot be both a `Government` `Entity` and a `Commercial` `Entity` - it must be one or the other, in this case `Government`. ### Tags {% hint style="success" %} **`Entities`** can have multiple **`Tags`**, which allow for greater understanding of their different dimensions by creating multiple facets through which to view them. {% endhint %} `Tags` are both powerful and confusing, which are really two sides of the same coin. To understand them further, we highly recommend learning about [Dimensionality](/learning/concepts/dimensionality), but here's a quick synopsis. Because `Entities` can have multiple `Tags`, they allow for flexible viewing, reducing complexity by filtering out `Entities` that do not meet the relevant criteria when such criteria can easily apply to multiple `Entities` and is not a defining characteristic in the same way `Categories` are set-up. This makes them powerful. They are confusing, though, because of this same feature: who picks the `Tags` and what do they mean? Should `Tags` be defined by the nomenclature of a given `Organization` or their dictionary defition? This gets confusing quickly, so read on in [Tags](/about/elements/data/tags) for more. > **Example:** The Defense Innovation Unit has `Defense`, `Military`, `Innovation`, and `Unit` tags in order to help visualize it alongside other `Entities` with the same tags. ### Range {% hint style="success" %} The **`Range`** is a time period or series of years where an **`Entity`** existed, used most with the **`Timeline`**. {% endhint %} While this feature will likely change over time, we believe there is value in seeing not only the current state of innovation in national security, but also its historical evolution. For this reason we need to capture [Data](/about/elements/data) for the [Timeline](/about/elements/timeline) and this field is where we do so. {% hint style="warning" %} ***NOTE**: This formatting is very specific to* [Kumu](/learning/tools/kumu)*, which is our initial visualization tool, but as we move through various stages of the process the associated* [Data](/about/elements/data) *fields may change to accomodate other tools or approaches.* {% endhint %} > **Example:** The Defense Innovation Unit has a `Range` of `2015..2022` because it was established in 2015 and continues to this day. ## Non-Filterable Attributes In addition to the attributes listed above, which allow us to reduce the size or complexity of our [Data](/about/elements/data) by filtering, there are other attributes which are essentially flat and do not further complicate the [Dimensionality](/learning/concepts/dimensionality) of an `Entity` (though they do still add dimensions). What this functionally means is that some of these attributes might change over time or only apply to certain `Entities` based on whatever helps us better understand the [Data](/about/elements/data). Because these are simple and pretty intuitive, we do not go into much more detail. As much as possible, we try to reduce complexity and be cognizant of [Dimensionality](/learning/concepts/dimensionality) by not creating unique fields for `Organizations` in comparison to `Groups` or `Individuals`. ### All Entities Any entity type can have the following non-filterable attributes: * **Website** * **LinkedIn** * **Twitter** Read on to learn more about [Categories](/about/elements/data/categories) and [Tags](/about/elements/data/tags)! # Categories Singular attributes of Entities that help with filtering and characterization. A `Category` is a means of denoting a core feature that is key in distinguishing [Entities](/about/elements/data/entities) - for now, we have them broken out as follows, but this may change and we will keep this page and the [Data](/about/elements/data) updated accordingly. Feel free to share [Feedback](/about/feedback) as you have it! ## Types of Categories Right now we are using the following `Categories`: ### Government {% hint style="success" %} **`Government`** applies to any of the **`Entities`** that are governmental in nature {% endhint %} We believe this will generally be somewhat simple, but there are [Entities](/about/elements/data/entities) with very close ties to [#non-profit](#non-profit "mention")s we expect may take some disambiguation. > **EXAMPLE**: `Army Futures Command` is a government `Organization` and has various `Projects` associated with it). ### Academic {% hint style="success" %} We applied **`Academic`** to **`Entities`** that have a primary tie to universities or other educational institutions. {% endhint %} Although the majority of these are also `Non-Profit` (at least nominally), the distinction is significant enough to warrant a separate category in our judgment. > **EXAMPLE**: `Stanford` offering of a class focused on `Hacking for Defense`, which is a separate `Project` `Entity` with the `Non-Profit` `Category`. ### Non-Profit {% hint style="success" %} **`Non-Profit`** is applied to non-**`Academic`** **`Entities`** that do not operate for a profit as **`Commercial`** counterparts do. {% endhint %} While sometimes challenging to distinguish from `Government` or `Academic` efforts (at least, we often find it confusing), this distinction applies to a number of `Entities` we think are important (such as us!). > **EXAMPLE**: The `Common Mission Project`, which runs `Hacking for Defense` at universities around the country in coordination with the `National Security Innovation Network`. ### Commercial {% hint style="success" %} We use **`Commercial`** with **`Entities`** whose primary goal is financial gain as measured by stakeholder value or other similar metric. {% endhint %} These are generally wonderful teammates and great folks who care about the mission as much as the rest of us (but it is important to understand how their incentives and structures differ from other `Entities`). > **EXAMPLE**: `BMNT`, a consultancy which originated the `Hacking for Defense` method and spun-off the `Common Mission Project` as a separate `Non-Profit` `Entity`. # Tags Multiple attributes of Entities that help capture their various dimensions. {% hint style="warning" %} The idea of **`Tags`** is one we feel is important, but right now they are sort-of all over the place and we need to find a good balance between the [Google Sheets](/learning/tools/google-sheets) approach and something much more robust. We think [Kumu](/learning/tools/kumu) offers some options with JSON blueprints, but need to explore further. {% endhint %} `Tags` allow for the easy filtering of [Entities](/about/elements/data/entities) based on a single field with multiple keywords (e.g. `Kessel Run` is an `Entity` that might have the `Tags` `Military` `Air Force` `Software`, and so on. By clicking on or filtering by a `Tag` one can easily see all the `Entities` associated with it in the [Data](/about/elements/data), [Graph](/about/elements/graph), [Map](/about/elements/map), and [Timeline](/about/elements/timeline). ### Problems with Tags Unfortunately, executing this in [Google Sheets](/learning/tools/google-sheets) using [Kumu](/learning/tools/kumu) is sort-of a challenge because: 1. [Kumu](/learning/tools/kumu) uses `|` connectors in a single field to separate `Tags` (which means you cannot run a simple `Data Validation` rule against a list of keywords like we do with `Labels`, `Categories`, and `Connections`. 2. The whole idea of `Tags` depends on a common set of terms... but how do you know whether to use `Software` or `DevSecOps` or `Technology` or something else? Who makes these decisions and how do the uninitiated learn? (NOTE: We will keep this page updated with our hypotheses and approaches). ### Future Plans for Tags We are very open to ideas and existing best practices here, so please [Contact Us](/about/contact-us) if you have ideas or examples to share! We think our [Partners](/about/support/partners) may be able to help with this as well. # Connections The links that show how Entities are related. We have a few different types of `Connections` that help characterize [Entities](/about/elements/data/entities) in the [Graph](/about/elements/graph). {% hint style="info" %} [Connections](/about/elements/data/connections) **and** [Entities](/about/elements/data/entities) **are the two foundational building blocks of the** [Data](/about/elements/data). {% 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). 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), 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)*, 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`. # Verification How we manage trust in the Data. {% hint style="warning" %} More details on Verification will be available soon. An overview is provided below. We welcome suggestions, examples, and inputs! {% endhint %} ### Speed vs. Trust One of the inherent challenges of crowd-sourced data is veracity (aka truthfulness). To address this question, we have to balance two factors: speed and trust. Speed is a hallmark feature of crowd-sourcing, with many different inputs and updates being possible across a large number of people in a short period of time. Unfortunately, the resulting data may be inaccurate, resulting in the second factor. Trust is required for users to apply data they come across to their daily lives, which is an objective of this project on numerous levels. With crowd-sourcing not providing an inherent trust in data veracity, we need some method of creating it, at least in some situations. #### Human-Mediated Verification One of the primary means we expect to use for [Verification](/about/elements/data/verification), especially at first or with new [Data](/about/elements/data) sets, will be human-in-the-loop mediation. While specific details and instructions will depend on the tool(s) employed (and be documented in [Workflow](/workflow/workflow-overview)), the general idea as that at least one (though ideally at least two) individuals will evaluate an input or update for whether it is satisfactory (again, using criteria listed elsewhere). If so, it will be marked as Verified as of that time and be updated later if there are additional changes (meaning that either some `Entities` or `Connections` will have their `Verification` status change over time or updates will not be shown until verified (meaning a lag-time between submission and when an update reflects in the broader `Data`, though a public holding tank for unverified updates could mediate this in some cases). The downside of this approach is that it will be somewhat resource-intensive and prone to human failure. That's where the next option comes in. #### Automated Verification Where possible, we would love to be able to automate verification. Then again, easier said than done. Our current hypothesis is that there are probably certain data sources (e.g. those ending in .gov) that are more likely to be inherently trustworthy and could substitute for human intervention in certain cases. If you have ideas or examples, [we're all ears](mailto:hello@def.org)! #### Unverified Data While there are certainly cases where [Verification](/about/elements/data/verification) will matter, there will be many cases where just exploring may be sufficient. This is similar to how social media works, with all the incumbent risks on the part of those who use the [Data](/about/elements/data) (but with some of the speed that can make it still useful). ### More to Follow This is an important topic and we're just starting to scratch the surface. # Graph A network view of national security innovation. {% hint style="danger" %} **WARNING**: While we are experimenting with [Kumu](/learning/tools/kumu) during the [Alpha](/release-notes/alpha) and [Beta](/release-notes/beta) stages of this project, the link to the `Graph` is likely to change (a result of how [Kumu](/learning/tools/kumu) links are structured). We will keep this page linked as those changes occur, so if you get an error going to an old link, please come back here. {% endhint %} The [Data](/about/elements/data) in this project is great, and we are really excited to build it more and more, but what started it all was this idea about a network graph showing `Organizations` in the ecosystem. We want to build on that idea to incorporate other [Entities](/about/elements/data/entities) (like `Groups`, `Activities`, `Artifacts`, and even `Individuals`), but there are a lot of associated [Data](/about/elements/data) challenges there, so we started with [Google Sheets](/learning/tools/google-sheets) and [Kumu](/learning/tools/kumu) and will continue exploring with [Partners](/about/support/partners) to see what else might be helpful and more robust. ### Initial Graph We populated the [Alpha](/release-notes/alpha) with just `Government` `Organizations` and are building from there, trying to capture the right layers while also finding views that simplify the complexity. This will be most of the fun of this project (isn't [Data Visualization](/learning/concepts/data-visualization) always fun?) and we look forward to [Feedback](/about/feedback), so feel free to [Contact Us](/about/contact-us)! {% embed url="" %} Graph of National Security Innovation {% endembed %} ### Future Graphs As we think about the future, we want to expand to include the [Map](/about/elements/map) and [Timeline](/about/elements/timeline) (both of which can be uniuque or just different views of the same [Data](/about/elements/data)) - we don't know the right answer yet on how to do this, and expect that working with [Partners](/about/support/partners) will likely open up other avenues for [Data Visualization](/learning/concepts/data-visualization) that we may want to explore. # Map National security innovation in your neighborhood. {% hint style="info" %} The **`Map`** is currently in an early Alpha stage, taking basic [Data](/about/elements/data) inputs for a **`Location`** and manually updating a Google Map with inputs from a Google Sheet holding the **`Data`**. We expect a more seamless updating process in the coming months. {% endhint %} # Timeline How national security security innovation evolves over time. {% hint style="warning" %} We do not yet have a **`Timeline`** in place for the project and hope to do so in the coming months, depending on how the [Data](/about/elements/data) shakes out and what we learn. Stay tuned! {% endhint %} # Use Cases Ways different groups may benefit from this project. We believe strongly in the need to test hypotheses, so these are our current hypotheses about the types of groups who may benefit from this project, how they might benefit. * [Government](/about/use-cases/government): Learn who else is in the ecosystem and grow connections to learn faster or build more efficiently (while also upskilling on data). * [Non-Profit](/about/use-cases/non-profit): Connect with government and other non-profits that have a similar mission or find new teammates for projects. * [Academic](/about/use-cases/academic): Identify trends for research, use material as part of a course on national security or innovation, and maybe even partner with the project. * [Commercial](/about/use-cases/commercial): Understand the organization and structure of government innovation efforts and connect with other companies. {% hint style="warning" %} **NOTE**: We are assessing whether some user groups may have additional [License](/about/support/license) restrictions to help align incentives based on intended use. {% endhint %} # Government Project applications for public servants and military personnel. {% hint style="warning" %} While we are in the [Alpha](/release-notes/alpha) and early [Beta](/release-notes/beta) stages of this project we expect [Use Cases](/about/use-cases) to be pretty flexible and welcome [Feedback](/about/feedback) to tweak them. {% endhint %} Our hypothesis around the utility of this project for government use is largely about awareness and connectivity, but could also be linked with [Education](/about/goals/education). > **We believe** [Government](/about/use-cases/government) **users will benefit by knowing who else is in the ecosystem in order to build connections, learn faster, and work more efficiently. We think they will learn about data as well, which is a win.** In practice, we know how difficult it is for government people to connect with other government people - it's silly, but also very real! Getting beyond one's own silo is hard, and we believe this project can help people do just that. Adding to the mix a streamlined way to dip into the data game without getting overwhelmed and we have a recipe for some really wonderful collaboration. # Non-Profit Project applications for non-profit communities and teams. {% hint style="warning" %} While we are in the [Alpha](/release-notes/alpha) and early [Beta](/release-notes/beta) stages of this project we expect [Use Cases](/about/use-cases) to be pretty flexible and welcome [Feedback](/about/feedback) to tweak them. {% endhint %} As volunteers in such organizations ourselves, we know the value of [Non-Profit](/about/use-cases/non-profit) [Entities](/about/elements/data/entities) to national security innovation and are excited to engage them through this project. > **We believe** [Non-Profit](/about/use-cases/non-profit) **orgs will benefit by connecting with** [Government](/about/use-cases/government) **and other non-profits that have a similar mission or find new teammates for projects.** There's certainly the [Education](/about/goals/education) aspect around [Data](/about/elements/data) as well, which we hope will be the tide that raises all boats, but at least to start there's this idea around connectivity. # Academic Project applications for students, teachers, and researchers. {% hint style="warning" %} While we are in the [Alpha](/release-notes/alpha) and early [Beta](/release-notes/beta) stages of this project we expect [Use Cases](/about/use-cases) to be pretty flexible and welcome [Feedback](/about/feedback) to tweak them. {% endhint %} Many may be familiar with the role of academia in national security innovation by virtue of `Entities` like `University Affiliated Research Centers (UARCs)` or some sort of `National Security Innovation Network (NSIN)` activity with `Hacking for Defense (H4D)` or the like. > **Our hypothesis is that** [Academic](/about/use-cases/academic) [Entities](/about/elements/data/entities) **will be interested in trends for research, use material as part of a course on national security or innovation, and maybe even partner with the project for mutually beneficial outcomes.** In this vein we hope to add value by offering something unique and curious to poke and prod for study purposes, but also know that the breadth of expertise latent in educational contexts would be a wonderfully symbiotic component of continued project development. # Commercial Project applications for startups, established businesses, and investors. {% hint style="warning" %} While we are in the [Alpha](/release-notes/alpha) and early [Beta](/release-notes/beta) stages of this project we expect [Use Cases](/about/use-cases) to be pretty flexible and welcome [Feedback](/about/feedback) to tweak them. {% endhint %} **There are thousands of individuals and organizations in the commercial world trying to make sense of what the national security community is doing about innovation.** Some of these entities are established and have longstanding ties to government groups like DARPA or one of the military labs. Others are new additions to the community or trying to determine if their products or services would be a good fit. Beyond that, there are investors and institutions who want to see innovation in national security increase and are backing it with funding. ### Why Include Commercial Entities? So how do commercial entities factor into this project? 1. **Understanding the commercial landscape** is important to truly appreciating what is happening in the ecosystem. For example, there are many problems that have nothing to do with technology and everything to do with policy, but [Government](/about/use-cases/government) continues to bemoan its technology challenges... showing how technology is perhaps *not* the problem can be helpful. 2. **Incentives and cycles** are a major part of the ecosystem, and there are key portions that depend on commercial services or capabilities, understanding of which will enable better questions and decisions on the part of [Government](/about/use-cases/government), [Academic](/about/use-cases/academic), and [Non-Profit](/about/use-cases/non-profit) groups. 3. **Commercial entities are always part of the ecosystem** going back as long as national security has been around. Helping those entities understand the ecosystem can help them act in ways that are more supportive of goals beyond their own profits and stakeholders. ### How Do Commercial Entities Contribute? For one thing, commercial entities have a unique perspective and separate interactions that help paint a picture of what this ecosystem contains, to include various feedback loops and gaps in information that reduce the efficacy of innovation efforts. Having contributions from these viewpoints allows us to better appreciate what is really going on and devise questions and experiments that can help address systemic issues. Additionally, there are tons of patriotic and servant-minded people who choose to work in the commercial sector for reasons that extend far beyond a paycheck. Limiting their representation or ability to participate would be not only rude, but also short-sighted. ### Limitations on Project Use by Commercial Entities While we recognize the importance of startups, businesses, and investors in the spread of innovation across national security, we also know that some of the incentives and cycles they operate with are different than those of other project stakeholders. {% hint style="warning" %} **We are considering how to shape the** [License](/about/support/license) **to address commercial use of the project in order to increase alignment and incentives.** {% endhint %} Functionally, this *might* mean that commercial entities (and their employees)could be allowed to contribute in generative and aligned manners, but not use the project as a means of furthering their commercial aims. More details and definitions are outlined in the [License](/about/support/license) and [Additional Licenses](/about/support/additional-licenses) sections. # Support # User Agreement What you agree to by interacting with this project. {% hint style="warning" %} 🐣 You found a page we really need to update! We believe a **User Agreement** will be important, which is why this stub is here, but one is not yet in place. Check back soon! {% endhint %} # Privacy How we protect personal information with this project. {% hint style="warning" %} 🐣 You found a page we really need to update! We believe **Privacy** will be important, which is why this stub is here, but a plan is not yet in place. Check back soon! {% endhint %} # Security How we protect sensitive information with this project. {% hint style="warning" %} 🐣 You found a page we really need to update! We believe **Security** will be important, which is why this stub is here, but a plan is not yet in place. Check back soon! {% endhint %} # Contributors People who have skin in the game through an investment of their time in this project. {% hint style="warning" %} We do not have a contributs list going yet, but hope to do so in the future as we work through the various [Privacy](/about/support/privacy) and [Security](/about/support/security) factors involved. {% endhint %} # Partners Organizations we work with on this project. In thinking about the long-term utility of this project, along with our values as a community, we very early decided that this needed to involve multiple organizations. Our concept with partnerships is simple: the relationship should be mutually-beneficial, time-bound (e.g. no need for lock-in, let's have a good trial period and offer flexibility), and fun. DEF is run by volunteers, so we don't have time to deal with any more painful bureaucracy in our lives. ### Existing Partners We do not yet have any formal partnerships for this project, but DEF already works with the these **existing partners**, who we hope to recruit as supporters for this project as well: * [**Agitare**](https://www.agitare.org) - a facilitation and design-focused community of deep thinkers who offer much in the way of questioning, especially when it comes to [Use Cases](/about/use-cases) and [Ethics](/about/support/ethics). * [**JSOFT**](https://www.jsoftalliance.org) - a community of people passionate about software in defense and national security whose expertise as a bridge for data and related aspects of this project can help grow its reach and connectivity (and with whom we already collaborate). * [**Google**](https://docs.natsec.io/about/support/www.google.com) - you know them, we already work with them on DEFx Software events and use Google Workspace to support this project and DEF overall, but Google Cloud has the potential to take the [Google Sheets](/learning/tools/google-sheets) + [Kumu](/learning/tools/kumu) version of this project and extend it to a much more robust platform, with associated educational resources. ### Potential Partners In addition to those above, we think the following organizations are really cool and good **potential partners**, if it works out: * [**Golden**](https://golden.com) - a commercial company building the world's largest knowledge engine / graph, their software is interesting because it helps apply the kinds of data-centric ideas of this project to day-to-day challenges people in national security face (plus there is no way we could generate that level of detail for our work, so perhaps an opportunity to collaborate exists). * **Data-focused software companies** - way too many to list here, but we think this space has a lot of opportunity to help people explore and learn about these concepts while also driving greater connectivity across the ecosystem. # License Who can use project data or services and in what ways. {% hint style="warning" %} We are currently trying to find the best approach to copywrighting and licensing this project. Below are some thoughts we have, but they are not final - read on for more! {% endhint %} **Our current thoughts about licensing are to use a** [**CC+ BY-NC-SA 4.0**](https://creativecommons.org/licenses/by-nc-sa/4.0/) **license.** Choosing a license and which license to use is a big decision that has cultural and other implications (e.g. deciding with whom and how to share will also affect who participates and how they do so). Because we know not everyone is a lawyer or speaks "licensese," this is how the above-listed permissions break-down, along with some examples to give you a sense of the expectations we have in using those terms, should they be adopted: ### Attribution (BY) *"You must give* [*appropriate credit*](https://creativecommons.org/licenses/by-nc-sa/4.0/#)*, provide a link to the license, and* [*indicate if changes were made*](https://creativecommons.org/licenses/by-nc-sa/4.0/#)*. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use."* \--- We made this inclusion in order to provide credit to the wonderful contributors to this project. There are many similar potential efforts out there, but since DEF is a volunteer organization and many of our [Partners](/about/support/partners) are as well, we felt it important to not only recognize their contributions but also provide a pathway for others to discover the work by attributing it as a source of their efforts. From our perspective, this needn't be arduous, just reference to the project with a link should suffice, since all the license data will be linked to the project itself. ### Non-Commercial (NC) *"You may not use the material for* [*commercial purposes*](https://creativecommons.org/licenses/by-nc-sa/4.0/#)*."* \--- This was an important baseline we felt necessary to include in order to protect contributors, especially government personnel or those with unique insights into a given nook in the ecosystem. Why would they need protection? In many instances, information about how a group or entity functions, much less key personnel or contact information, serves as a barrier. In some cases, this is problematic (as many startups and small businesses can attest when trying to work with government). In other cases, it is protective, such as the fact that contact information and rolodexes of government employees are not publicly posted (protecting against not only unwanted solicitation, but also spam, social engineering, and even information warfare efforts). We chose to take the more protective "non-commercial" baseline so that people would feel more comfortable contributing information. That certainly does not prevent the license from being abused, but sets a standard of behavior for what we expect as a community. The option for [#additional-licenses](#additional-licenses "mention")opens up a side door for the potential to have commercial entities use project efforts under a separate agreement. Additionally, we believe that [Security](/about/support/security) and [Privacy](/about/support/privacy)will be important part of this effort and have [Partners](/about/support/partners) with whom we are exploring ways to offer more robust data while still protecting its use to those unlikely to abuse it (or whose access can be curtailed if abuse occurs). All great [Ethics](/about/support/ethics) questions! ### Share Alike (SA) *"If you remix, transform, or build upon the material, you must distribute your contributions under the* [*same license*](https://creativecommons.org/licenses/by-nc-sa/4.0/#) *as the original."* \--- We felt it was reasonable to request that those who use project material extend the same sharing and openness we establish here to any efforts they may undertake. Here are a few potential applications, just to give a sense of how we interpret this: * For [Academic](/about/use-cases/academic) users, we would expect sharing of research, studies, or other results of the derivative or associated work (at least sufficient to add back to the goals of this project). * Those in [Government](/about/use-cases/government) might find it more challenging to apply this standard, as many derivations might include non-public or even classified observations, but we believe it is wholly reasonable to still expect a reintroduction of findings so long as national security itself is not at stake. * On the [Non-Profit](/about/use-cases/non-profit) front, this maybe looks like a video about the learnings or some sort of event where the benefits or impact is discussed so others can appreciate it. * Lastly, our [Commercial](/about/use-cases/commercial) contributors and collaborators might find that a blog or social media post capturing reflections from studying the networks, relationships, and questions raised by the product fits them well while staying within the [#non-commercial](#non-commercial "mention") constraint. In all cases, we aim to help people act in ways that are going to not only benefit them, but also benefit others in mutually reinforcing ways, creating virtuous (not vicious) cycles. ### Additional Licenses (CC+) *"*[*CC+*](https://wiki.creativecommons.org/wiki/CCPlus) *is a protocol providing a simple way for users to get rights beyond the rights granted by a CC license. For example, a work's Creative Commons license might offer noncommercial rights. With CC+, the license can link to a resource indicating how a reuser may secure commercial rights or other additional permissions or services such as warranty, permission to use without attribution, or even access to physical media."* \--- While we felt it was important to include [#non-commercial](#non-commercial "mention")as an element of the license, we understand that we do not know many potential uses that would benefit the broader national security community, meaning that any restrictions have the potential to be harmful. For this reason we chose the CC+ implementation (indicative of a plain Creative Commons license with additional permissions available under a separate agreement). You can see more under [Additional Licenses](/about/support/additional-licenses) or [Contact Us](/about/contact-us) with any questions or ideas. # Additional Licenses Options for additional use of project data or applications beyond the core CC BY-NC-SA license. {% hint style="warning" %} We do not yet have a formal [License](/about/support/license) decision in place and are not looking to extend any additiona licensing, but expect, based on the [License](/about/support/license) choice, that may happen. {% endhint %} What this means is that the baseline [License](/about/support/license) applies unless or until this section is updated and an additional license is granted. If you have any questions about this, please [Contact Us](/about/contact-us)! #### **Why do we have a whole page to say we are *****not***** doing something?** * We want to adhere to as many of the [open data](https://opendatahandbook.org/guide/en/what-is-open-data/) principles as possible, but know that **commercial use can create challenging incentives**, such as competition or abuse. * **The** [People](/about/goals/people) **who power this project need to feel safe contributing** information and not worry that it will somehow be used against them (for example, sharing contact information of government personnel so they can connect with other government personnel might also expose them to undesired outreach from commercial vendors). * Much of the initiation of this project is based on hypotheses for which **we need more data and feedback**; starting with a more restrictive license and allowing additional options in the future protects the integrity of the work while we evaluate other opportunities. #### What kinds of additional licenses might you consider in the future? Great question! Here's what we are thinking right now: * Grant **free commercial licenses to DEF partners or sponsors** as part of a partnership or sponsorship agreement (supporting DEF financially while limiting commercial use to groups already vetted under partnership or sponsorship agreements). * Grant **commercial licenses to vetted companies for a fee** so that they can apply the crowdsourced knowledge to their businesses and activities while also supporting DEF and this project. There are doubtless other applications we have yet to consider, so feel free to [Contact Us](/about/contact-us) if something else comes to mind! # Ethics Considerations for how and why across the project. {% hint style="warning" %} 🐣 You found a page we really need to update! We believe **Ethics** will be important, which is why this stub is here, but a plan is not yet in place. Check back soon! {% endhint %} # Feedback How you can let us know about the project's value or flaws. {% hint style="warning" %} 🐣 You found a page we really need to update! We believe **Feedback** will be important, which is why this stub is here, but no process is not yet in place. Check back soon! {% endhint %} # Contact Us How you can reach out if you have questions or ideas. You can connect with DEF by shooting an email to - we expect to have other channels for [Feedback](/about/feedback) and to contact us as the project matures. # FAQ Overview How we approach documenting Frequently Asked Questions. # Data FAQ Some of our most frequently asked questions about project data. # Graph FAQ # Map FAQ # Timeline FAQ # Documentation FAQ # How can I support or contribute to this project? # How is this project sustained? # What criteria do you use to collect project data? We include an `Organization`, `Group`, `Activity`, `Artifact`, or `Individual` in our [Data](/about/elements/data) based on two main criteria: * **Is it focused on innovation in national security?** * **Does it help us understand innovation in national security?** To give you an even better sense of this (since we expect a lot of people will have many different views on the subject), we go into more detail below. ## Definitions Our entire project is build on some very widely-debated terms, so let's give you a sense of how we define them first: ### `Innovation` Our simplified version of this term is "*Something new that adds value for someone*" (see [Wikipedia](https://en.wikipedia.org/wiki/Innovation) or [ISO 56000:2020](https://www.iso.org/obp/ui/#iso:std:iso:56000:ed-1:v1:en)) - this requires three elements: **novelty**, **value**, and a **user**. Two out of three doesn't cut it, but we certainly recognize that much of what people call `Innovation` is really just `Technology` (which is `Novelty` and potential `Value` that may be awaiting a `User`) or perhaps the key feature is context, which might be the trigger for meeting the `Novelty` criterion (such as an existing approach reintroduced in new circumstances). When in doubt, we want to be generous about applying this term, since those three core variables are constantly changing; something that was `Innovation` one day might not be `Innovation` the next day and our [Goals](/about/goals) do not include "being the arbiter of dictionary entries." :wink: ### **`National Security`** This term is even more contested than `Innovation`, so we punted and defined it by a structural feature that everyone can agree on: [the National Security Council](https://www.whitehouse.gov/nsc/). Although that entity changes periodically, its members comprise what the government considers to be the core of a national security apparatus. Thus, we consider it to be the foundation for our definition, which looks the most like [what ThoughtCo says](https://www.thoughtco.com/national-security-definition-and-examples-5197450): "*the ability of a country’s government to protect its citizens, economy, and other institutions.*" If you want to dip your toe into the political side of this term (*careful!*), check out different perspectives from [The Center for Strategic and International Studies](https://www.csis.org/programs/international-security-program/civics-national-security-imperative), [The Aspen Institute](https://www.aspeninstitute.org/blog-posts/we-must-expand-the-definition-of-national-security/), and [The Heritage Foundation](https://www.heritage.org/military-strength-essays/2015-essays/what-national-security). Or go straight to [the National Security Act of 1947](https://en.wikipedia.org/wiki/National_Security_Act_of_1947) and see where it all started (maybe top-up that coffee first, though). :coffee: ## Adding Data Given that background, here is how we actually apply the [#definitions](#definitions "mention") to the [Data](/about/elements/data): ### Innovation Entities To break this angle down further, we again ask a couple of questions: 1. If someone came to us asking about national security innovation, would we direct them towards that `Entity`? 2. Would that `Entity` want individuals asking them about national security innovation? If both answers are "yes", we consider that entity a part of the national security innovation ecosystem, and we will include it in our dataset with an `Innovation` as one of the [Tags](/about/elements/data/tags) (which makes it easy to sort out those [Entities](/about/elements/data/entities)from among the many others that exist as infrastructure or for context). ### Infrastructure Entities We know that there is much more to understanding this ecosystem (one of our [Goals](/about/goals)) than just seeing [Entities](/about/elements/data/entities) that are explicitly tied to `Innovation`, which is why we also have many whose main inclusion is to show [Connections](/about/elements/data/connections) across the government bureaucracy or other such factors that shape how `Innovation` actually occurs in `National Security`. Such an `Entity` will not have `Innovation` listed in the `Tags`, but we might include an `Entity` that does not pass our [#innovation-entities](#innovation-entities "mention") test under this reasoning. This also allows us to deal with the crush of people who are very interested in having their `Entity` on the [Graph](/about/elements/graph) and do not care about the project [Goals](/about/goals) because we can just filter them out using different `Views`. # How do I report an error or missing data? # How do I access raw project data? # What is the difference between the graph and the map? # How can I update project documentation? # Release Notes Overview How we document changes in this project over time for transparency and engagement. # Feature Timeline How we plan to release new features. {% tabs %} {% tab title="Data" %} This is a list of planned features and associated requests for project `Data`: ### Planned Features * [ ] Feature ### Feature Requests * [ ] Feature {% endtab %} {% tab title="Graph" %} This is a list of planned features and associated requests for the `Graph`: ### Planned Features * [ ] Feature ### Feature Requests * [ ] Feature {% endtab %} {% tab title="Timeline" %} This is a list of planned features and associated requests for the `Timeline`: ### Planned Features * [ ] Feature ### Feature Requests * [ ] Feature {% endtab %} {% tab title="Map" %} This is a list of planned features and associated requests for the `Map`: ### Planned Features * [ ] Feature ### Feature Requests * [ ] Feature {% endtab %} {% endtabs %} # Beta Our first public offering. We expect the public Beta to launch in Spring 2022. Stay tuned! # Alpha Our private initial offering. You see it, you're special. Our Alpha started in December 2021 with the initial goal of scoping the four [Elements](/about/elements) and the instantiating the first two: * [Data](/about/elements/data) * [Graph](/about/elements/graph) The other two will be addressed either in the [Beta](/release-notes/beta) or some other future release cycle. Some of our tasks pursuant to these are listed below: {% tabs %} {% tab title="Data" %} * [x] Identify existing data sources or maps * [ ] Compile all `Government` `Organization` [Entities](/about/elements/data/entities) from existing data sources * [ ] Add additional `Government` `Organizations` required to make `Org Chart` [Connections](/about/elements/data/connections) * [ ] Make all relevant [Connections](/about/elements/data/connections) between `Government` `Organizations` {% endtab %} {% tab title="Graph" %} {% endtab %} {% tab title="Map" %} No actions for this version. {% endtab %} {% tab title="Timeline" %} No actions for this version. {% endtab %} {% endtabs %} # v0.1.0 31 Dec 2021 This initial version started with the work of several existing efforts, incuding the [2018 version of a similar project](https://kumu.io/aflazo/def-innovation-ecosystem-map#def-ecosystem-map) and data accumulated through crowdsourcing and research conducted by interns at both [FIS](https://www.linkedin.com/company/federal-innovators-salon/) and [DEF](https://docs.natsec.io/release-notes/alpha/www.def.org). **Many thanks to all those who dedicated their time and effort to provide a robust baseline!** :pray: Our overall goal in starting out was simply to learn the best ways to reliably and consistently ingest `Data` and display it in the `Graph` - these two tasks form the main functionality of the project and enabling extensibility (e.g. multiple means of [Adding or Updating Data](/workflow/contribution/adding-or-updating-data) and multiple means of [Cleaning Data](/workflow/evaluation/cleaning-data) are foundational to what we're looking at. {% tabs %} {% tab title="Data" %} * Exported existing lists from various sources and started consolidating them in [Google Sheets](/learning/tools/google-sheets) to serve as an initial public view of `Data` outside a visualization tool * Established initial [Entities](/about/elements/data/entities) list with associated fields based on existing lists noted above (see the `Labels` column in `Entities` sheet) * Created initial [Categories](/about/elements/data/categories) for use with [Entities](/about/elements/data/entities) (see the `Validation (ignore)` sheet) * Built initial list of [Tags](/about/elements/data/tags) to use with [Entities](/about/elements/data/entities) (see the `Validation (ignore)` sheet) * Wrote initial [Connections](/about/elements/data/connections) by type to link [Entities](/about/elements/data/entities) (see the `Validation (ignore)` sheet) {% endtab %} {% tab title="Graph" %} * Connectied [Google Sheets](/learning/tools/google-sheets) to [Kumu](/learning/tools/kumu) to see how the [Graph](/about/elements/graph) data import worked. * Experimented with different [Entities](/about/elements/data/entities), [Categories](/about/elements/data/categories), [Tags](/about/elements/data/tags), and [Connections](/about/elements/data/connections) to see how they look in the [Graph](/about/elements/graph). {% endtab %} {% tab title="Timeline" %} * No `Timeline` features were modified in this release. * While we are currently using [Kumu](/learning/tools/kumu) for visualization and it offers the ability to snap efforts to a `Timeline`, our first `Graph` will focus primarily on connections to show where innovation-focused efforts are housed. {% endtab %} {% tab title="Map" %} * No `Map` features were modified in this release. * As with the `Timeline` we have the capability to display certain `Entities` in a `Map` view and are excited to add that functionality as we learn about the best ways to work with the `Data` and `Graph`. {% endtab %} {% endtabs %} # Workflow Overview How we organize and execute project updates. **Thanks for checking out our workflow!** This section outlines the steps used in various aspects of the project so that anyone can follow along (or check our work to help improve it). # Contribution How people can share their insights with us. # Adding or Updating Data # Modifying the Graph # Modifying the Timeline # Modifying the Map # Updating Documentation # Evaluation # Cleaning Data How to address the messy world of spreadsheets. # Prohibited Content Content we do not allow as part of the project. # Adjudicating Changes How we handle conflicts based on contributions. # Review How we take a step back from it all to think more deeply about the project. # User Feedback What people are saying about the project. # Process Improvement How we can make parts of the project better. # Outcomes What the project is helping people to accomplish. # Learning Overview Ways you can come alongside us or extend this project through personal growth. # Tools # GitBook How we handle project documentation. # Google Forms How we collect project contributions. # Google Sheets How we store project data for cleaning and visualization. # Kumu How we visualize project data. # Slack How we communicate about project activities. # Concepts # Data Structures # Data Visualization # Dimensionality # Courses # Udemy / DigitalU # FreeCodeCamp # Research Content we have found helpful in this project. # Existing Research Great work already accomplished that may be of interest if you like this project. # Questions for Researchers What we ask ourselves (or are asked by others) that bears further investigation.