From bea100213565de1348375828e14be6e1482a67f8 Mon Sep 17 00:00:00 2001
From: bandicoot-stack <102703343+bandicoot-stack@users.noreply.github.com>
Date: Wed, 30 Mar 2022 23:17:22 -0700
Subject: [PATCH] Updated Zarf readme with the link to Naval Postgraduate
 School Research (#427)

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 8d3700c4a7..a6e0f8c277 100644
--- a/README.md
+++ b/README.md
@@ -8,6 +8,12 @@ It provides a static go binary (can run anywhere) CLI that can pull, package, an
 
 Zarf runs on [a bunch of operating systems](./docs/supported-oses.md) and aims to support configurations ranging from "I want to run one, simple app" to "I need to support & dependency control a _bunch_ of internet-disconnected clusters".
 
+Zarf was theorized and initially demonstrated in Naval Postgraduate School reasearch:
+
+[A DEVSECOPS APPROACH FOR DEVELOPING AND DEPLOYING CONTAINERIZED CLOUD-BASED SOFTWARE ON SUBMARINES](https://calhoun.nps.edu/handle/10945/68688).
+
+Its origin story remains to be told but is of the likes seen in [Kessel Run](https://www.airforcemag.com/article/making-the-kessel-run/).
+
 [![asciicast](https://asciinema.org/a/475530.svg)](https://asciinema.org/a/475530)
 
 ## Why is Zarf Needed?