Dashboard: remove blog post ideas section (posts are live)

2026-06-10 13:46:40 -03:00
parent d99f4c1a63
commit 10b03c3ecb
4 changed files with 0 additions and 209 deletions
@@ -1,47 +0,0 @@
-# 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
@@ -1,24 +0,0 @@
-# 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
@@ -1,27 +0,0 @@
-# 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