diff --git a/docs/twitter/2061124942968545433/thread.md b/docs/twitter/2061124942968545433/thread.md
new file mode 100644
index 00000000..e01c740c
--- /dev/null
+++ b/docs/twitter/2061124942968545433/thread.md
@@ -0,0 +1,27 @@
+---
+title: "hits the easy to debug CPU or GPU stuff in the same framework (simply write and "
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/2061124942968545433"
+post_id: "2061124942968545433"
+timestamp: "2026-05-31 16:37:34"
+post_count: 3
+reply_count: 0
+repost_count: 0
+like_count: 2
+view_count: 541
+---
+
+# @NOTimothyLottes — hits the easy to debug CPU or GPU stuff in the same framework (simply write and 
+
+## Post 1 (2026-05-31 16:32:54)
+
+no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ...
+
+## Post 2 (2026-05-31 16:35:58) — reply to Post 1
+
+moving to this >>> CART file is mmapped on CPU with mapped GPU access (no file IO) - background page walker to ensure OS won't page it out - beginning of CART file is a grid of 32-bit unsigned values - hex dumping that as my 'log file' - either to term or GPU render
+
+## Post 3 (2026-05-31 16:37:34) — reply to Post 2
+
+hits the easy to debug CPU or GPU stuff in the same framework (simply write and it just appears) - it's always a HEX dump, but can show decimal by pretending it's a 4-bit/character terminal with a hex font :)
diff --git a/docs/twitter/2061124942968545433/thread_data.json b/docs/twitter/2061124942968545433/thread_data.json
new file mode 100644
index 00000000..35b53070
--- /dev/null
+++ b/docs/twitter/2061124942968545433/thread_data.json
@@ -0,0 +1,54 @@
+{
+  "root_post_id": "2061124942968545433",
+  "posts": [
+    {
+      "post_id": "2061123768429211767",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ...",
+      "timestamp": "2026-05-31 16:32:54",
+      "media_urls": [],
+      "reply_to_id": null,
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 0,
+        "like_count": 9,
+        "view_count": 2970
+      }
+    },
+    {
+      "post_id": "2061124536729207080",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "moving to this >>> CART file is mmapped on CPU with mapped GPU access (no file IO) - background page walker to ensure OS won't page it out - beginning of CART file is a grid of 32-bit unsigned values - hex dumping that as my 'log file' - either to term or GPU render",
+      "timestamp": "2026-05-31 16:35:58",
+      "media_urls": [],
+      "reply_to_id": "2061123768429211767",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 1,
+        "repost_count": 0,
+        "like_count": 4,
+        "view_count": 567
+      }
+    },
+    {
+      "post_id": "2061124942968545433",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "hits the easy to debug CPU or GPU stuff in the same framework (simply write and it just appears) - it's always a HEX dump, but can show decimal by pretending it's a 4-bit/character terminal with a hex font :)",
+      "timestamp": "2026-05-31 16:37:34",
+      "media_urls": [],
+      "reply_to_id": "2061124536729207080",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 2,
+        "view_count": 541
+      }
+    }
+  ],
+  "source_url": "https://x.com/NOTimothyLottes/status/2061124942968545433"
+}
\ No newline at end of file