diff --git a/docs/twitter/2078349730204078527/media/2078347557474849137_1.png b/docs/twitter/2078349730204078527/media/2078347557474849137_1.png
new file mode 100644
index 00000000..92fd53f7
Binary files /dev/null and b/docs/twitter/2078349730204078527/media/2078347557474849137_1.png differ
diff --git a/docs/twitter/2078349730204078527/media/2078348323287716101_1.png b/docs/twitter/2078349730204078527/media/2078348323287716101_1.png
new file mode 100644
index 00000000..404c4a79
Binary files /dev/null and b/docs/twitter/2078349730204078527/media/2078348323287716101_1.png differ
diff --git a/docs/twitter/2078349730204078527/media/2078349730204078527_1.png b/docs/twitter/2078349730204078527/media/2078349730204078527_1.png
new file mode 100644
index 00000000..b3eef3fe
Binary files /dev/null and b/docs/twitter/2078349730204078527/media/2078349730204078527_1.png differ
diff --git a/docs/twitter/2078349730204078527/thread.md b/docs/twitter/2078349730204078527/thread.md
new file mode 100644
index 00000000..fa297e7c
--- /dev/null
+++ b/docs/twitter/2078349730204078527/thread.md
@@ -0,0 +1,37 @@
+---
+title: "I realized at some point I can have most interpreted forth-style words in an ali"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/2078349730204078527"
+post_id: "2078349730204078527"
+timestamp: "2026-07-18 05:22:44"
+post_count: 4
+reply_count: 1
+repost_count: 0
+like_count: 5
+view_count: 502
+---
+
+# @NOTimothyLottes — I realized at some point I can have most interpreted forth-style words in an ali
+
+## Post 1 (2026-07-18 05:14:06)
+
+All {0-6} argument syscall options in 32-bytes. The plan is to embed the interpreter inside the words with a 3-byte overhead {AD (lodsd), FF E0 (jmp rax)} so levering lots of x86-64 stuff for minimal size
+
+![Media 1](./media/2078347557474849137_1.png)
+
+## Post 2 (2026-07-18 05:17:08) — reply to Post 1
+
+Everything forced in lower 32-bit, but still building around 64-bit support. Since I'm not using x86-64 CALL/RET I can free up the stack ops strictly for the data stack.
+
+![Media 1](./media/2078348323287716101_1.png)
+
+## Post 3 (2026-07-18 05:22:44) — reply to Post 2
+
+I realized at some point I can have most interpreted forth-style words in an aligned 8-bytes. So can make a very small interpreter.
+
+![Media 1](./media/2078349730204078527_1.png)
+
+## Post 4 (2026-07-18 06:01:49) — reply to Post 3
+
+@NOTimothyLottes Even smaller code size possible with custom compression scheme, where you design bytecode not for immediate execution but to be decompressed on load.
diff --git a/docs/twitter/2078349730204078527/thread_data.json b/docs/twitter/2078349730204078527/thread_data.json
new file mode 100644
index 00000000..32b386b1
--- /dev/null
+++ b/docs/twitter/2078349730204078527/thread_data.json
@@ -0,0 +1,76 @@
+{
+  "root_post_id": "2078349730204078527",
+  "posts": [
+    {
+      "post_id": "2078347557474849137",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "All {0-6} argument syscall options in 32-bytes. The plan is to embed the interpreter inside the words with a 3-byte overhead {AD (lodsd), FF E0 (jmp rax)} so levering lots of x86-64 stuff for minimal size",
+      "timestamp": "2026-07-18 05:14:06",
+      "media_urls": [
+        "https://pbs.twimg.com/media/HNfFmXoXkAAMHM9?format=png&name=orig"
+      ],
+      "reply_to_id": null,
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 1,
+        "repost_count": 0,
+        "like_count": 9,
+        "view_count": 1016
+      }
+    },
+    {
+      "post_id": "2078348323287716101",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "Everything forced in lower 32-bit, but still building around 64-bit support. Since I'm not using x86-64 CALL/RET I can free up the stack ops strictly for the data stack.",
+      "timestamp": "2026-07-18 05:17:08",
+      "media_urls": [
+        "https://pbs.twimg.com/media/HNfGRZvXEAEtaKH?format=png&name=orig"
+      ],
+      "reply_to_id": "2078347557474849137",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 1,
+        "repost_count": 0,
+        "like_count": 4,
+        "view_count": 559
+      }
+    },
+    {
+      "post_id": "2078349730204078527",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "I realized at some point I can have most interpreted forth-style words in an aligned 8-bytes. So can make a very small interpreter.",
+      "timestamp": "2026-07-18 05:22:44",
+      "media_urls": [
+        "https://pbs.twimg.com/media/HNfHl-dXcAAf6Om?format=png&name=orig"
+      ],
+      "reply_to_id": "2078348323287716101",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 1,
+        "repost_count": 0,
+        "like_count": 5,
+        "view_count": 502
+      }
+    },
+    {
+      "post_id": "2078359568636080568",
+      "author": "Boris Chuprin",
+      "handle": "noop_dev",
+      "text": "@NOTimothyLottes Even smaller code size possible with custom compression scheme, where you design bytecode not for immediate execution but to be decompressed on load.",
+      "timestamp": "2026-07-18 06:01:49",
+      "media_urls": [],
+      "reply_to_id": "2078349730204078527",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 1,
+        "view_count": 29
+      }
+    }
+  ],
+  "source_url": "https://x.com/NOTimothyLottes/status/2078349730204078527"
+}
\ No newline at end of file