From 7ec495334bb92a2caa1ae0bdf85ff664ffc45567 Mon Sep 17 00:00:00 2001
From: sigil-03 <sigil@glyphs.tech>
Date: Fri, 18 Jul 2025 14:57:51 -0600
Subject: [PATCH] add comment 939decab121b6b4b3095a3b20d5d13f4 on issue
 7e2a3a59fb6b77403ff1035255367607

---
 .../comments/939decab121b6b4b3095a3b20d5d13f4/description      | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 7e2a3a59fb6b77403ff1035255367607/comments/939decab121b6b4b3095a3b20d5d13f4/description

diff --git a/7e2a3a59fb6b77403ff1035255367607/comments/939decab121b6b4b3095a3b20d5d13f4/description b/7e2a3a59fb6b77403ff1035255367607/comments/939decab121b6b4b3095a3b20d5d13f4/description
new file mode 100644
index 0000000..38f265e
--- /dev/null
+++ b/7e2a3a59fb6b77403ff1035255367607/comments/939decab121b6b4b3095a3b20d5d13f4/description
@@ -0,0 +1,3 @@
+for now, let's just add the ability to mark dependencies, and then later we can build functionality on top of it which allows an application to decide what to do based on the state of those dependencies. 
+
+i think regardless we should always keep the dependencies, unless they get removed intentionally, and should instead operate off of the `state` of those dependencies.