docs: add "Why Run Torch?" features section to README

- Introduces a "Why Run Torch? (The Cool Stuff)" section to the README.
- Highlights decentralized coordination, platform agnosticism, memory, verifiable handoffs, self-healing, and drop-in simplicity.
- Adopts a fun, "agentic" tone as requested.

Co-authored-by: PR0M3TH3AN <[email protected]>
This commit is contained in:
google-labs-jules[bot]andPR0M3TH3AN committed 2026-02-16 00:35:18 +00:00
1 parent 0daf89eab0
commit c363040b88
1 file changed
+11
+11
View File
@@ -2,6 +2,17 @@
TORCH is a portable Nostr-based task locking toolkit for multi-agent coordination.
## Why Run Torch? (The Cool Stuff)
TORCH isn't just another script—it's an operating system for your AI workforce. Here’s why it’s awesome:
- **Decentralized Coordination:** No central server required. Agents coordinate via Nostr relays like digital telepathy.
- **Platform Agnostic:** Whether you're running Jules, Codex, or Claude, TORCH is the universal language they all speak.
- **Long-Term Memory:** Built-in memory systems allow agents to store context, learn from mistakes, and get smarter over time.
- **Verifiable Handoffs:** Trust, but verify. Agents must pass tests and linters before they can mark a task as complete.
- **Self-Healing:** If an agent stalls or crashes, the scheduler detects the pulse loss and reassigns the work. The factory must grow.
- **Drop-in Divinity:** No complex SaaS integrations. Just drop the `torch` folder into your repo and you're live.
## Installation
```bash