From e7d386ec3ff8c5e4df94b7d9ad82dc47129145a0 Mon Sep 17 00:00:00 2001 From: Oliver Date: Wed, 10 Jun 2026 13:36:28 -0300 Subject: [PATCH] Blog ideas: add filesystem analysis research to idea #001 --- .../001-why-backing-up-an-agent-is-so-hard.md | 47 +++++++++++++++++++ blog/ideas/002-cold-email-at-scale.md | 24 ++++++++++ blog/ideas/003-odoo-beyond-speed-run.md | 27 +++++++++++ operations.html | 33 ++++++++++++- 4 files changed, 130 insertions(+), 1 deletion(-) create mode 100644 blog/ideas/001-why-backing-up-an-agent-is-so-hard.md create mode 100644 blog/ideas/002-cold-email-at-scale.md create mode 100644 blog/ideas/003-odoo-beyond-speed-run.md diff --git a/blog/ideas/001-why-backing-up-an-agent-is-so-hard.md b/blog/ideas/001-why-backing-up-an-agent-is-so-hard.md new file mode 100644 index 0000000..441414a --- /dev/null +++ b/blog/ideas/001-why-backing-up-an-agent-is-so-hard.md @@ -0,0 +1,47 @@ +# 001 — Why backing up an agent is so hard + +**Status:** Research in progress +**Tags:** Technical, Backups, DevOps + +## Research notes + +### Real filesystem changes after one week of work on a Linux agent + +``` +504.6M ./usr + 43.3M ./var +448.9M ./root + 54.0K ./etc +996.8M . +``` + +Most users only back up the home directory (`/root` = 448.9M). But over half the changes live outside it — `/usr` (504.6M) and `/var` (43.3M) contain installed packages, pip/npm global installs, database files, logs, and system configs. A naive home-dir-only backup misses 55% of what changed. + +At restore time, you get your config back but the agent won't run — missing dependencies, missing system packages, missing database files. + +### What this means for the post + +- Agent environments are not just config files — they're full Linux systems with packages, services, and state scattered everywhere +- "Backup your home directory" is dangerously incomplete advice for AI agents +- Derez.ai's full-disk snapshot approach is the right solution +- This is a strong selling point: the agent works after restore, not just the config + +### Next data points + +Oliver will do two more memory analysis snapshots after running the speed-run setups (Odoo + Cold Email). Those will show how much additional state those integrations add. + +### Outline + +1. The sprawl problem — why agents are harder to back up than a standard server + *Include the filesystem analysis table* +2. What a real agent backup needs to capture +3. How Borg/deduplicated snapshots solve it +4. How Derez.ai does it automatically (one-click restore) +5. Best practices for users +6. Better save than sorry — the selling point + +### References + +- Borg backup docs +- Hermes Agent directory structure (~/.hermes/) +- Filesystem analysis: `du -sch /usr /var /root /etc` after one week \ No newline at end of file diff --git a/blog/ideas/002-cold-email-at-scale.md b/blog/ideas/002-cold-email-at-scale.md new file mode 100644 index 0000000..be30e42 --- /dev/null +++ b/blog/ideas/002-cold-email-at-scale.md @@ -0,0 +1,24 @@ +# 002 — Cold email at scale: from one-off to campaign + +**Status:** Idea +**Tags:** Marketing, Cold Email, Automation + +## Research notes + +- We already have a cold email speed-run post — this would be the "next level" +- Moving from single emails to sequenced campaigns +- Follow-ups, A/B testing, reply detection +- CRM integration for tracking + +## Outline + +1. Why one-off cold emails leave money on the table +2. Building a sequence: intro → follow-up 1 → follow-up 2 → breakup +3. Using Hermes Agent tools for reply detection and routing +4. Measuring open rates, reply rates, conversion +5. Tying into a CRM (Odoo?) for pipeline tracking + +## References + +- Existing cold email speed-run post +- Alex Hormozi / Cold email playbooks \ No newline at end of file diff --git a/blog/ideas/003-odoo-beyond-speed-run.md b/blog/ideas/003-odoo-beyond-speed-run.md new file mode 100644 index 0000000..1bb289e --- /dev/null +++ b/blog/ideas/003-odoo-beyond-speed-run.md @@ -0,0 +1,27 @@ +# 003 — Odoo + AI agent: beyond the speed run + +**Status:** Idea +**Tags:** Odoo, Integration, CRM + +## Research notes + +- The speed-run post shows a basic Odoo connection +- This post goes deeper: actual workflows that save time +- Inventory alerts, automated invoice follow-ups, lead scoring + +## Outline + +1. Recap: what the speed run covered +2. Real use cases: + - auto-follow-up on stale leads + - inventory low-stock alerts via email/Slack + - monthly sales report generated and emailed +3. Combining Odoo tools with Hermes Agent skills +4. Security: creating a restricted Odoo user for the agent +5. Next steps for readers + +## References + +- Existing Odoo speed-run post +- Odoo External API docs +- Odoo4projects.com free trial \ No newline at end of file diff --git a/operations.html b/operations.html index 054ad08..75e0a33 100644 --- a/operations.html +++ b/operations.html @@ -716,7 +716,7 @@
-
Why backing up an agent is so hard
+
#001 — Why backing up an agent is so hard
Modern AI agents install packages everywhere — pip in venvs, npm globally, configs scattered across /etc, ~/.config, /opt, custom paths. A naive filesystem backup misses half the environment.
Technical @@ -725,6 +725,37 @@
+
+
+ +
+
+
#002 — Cold email at scale: from one-off to campaign
+
Moving from single cold emails to sequenced campaigns with follow-ups, A/B testing, reply detection, and CRM integration.
+
+ Marketing + Cold Email + Automation +
+
+
+
+
+ +
+
+
#003 — Odoo + AI agent: beyond the speed run
+
Deeper Odoo workflows: auto-follow-up on stale leads, low-stock alerts, monthly sales reports — all via the agent.
+
+ Odoo + Integration + CRM +
+
+
+

+ Research notes at blog/ideas/###-topic.md +