mfowler
e4453dcfdd
Based on @ponder.ooo's "snake pit agent orchestrator" idea (bsky 2026-05-28) and Claude's metaphor-mapping elaboration: agents are snakes, tasks are food tossed into a shared pit; snakes devour/digest/regurgitate/excrete. A worker-pool-over-a-shared-queue topology (contrast the builder-adversary phase machine): - pit/ is a filesystem queue; snakes claim by atomic mv (no two eat the same food) - species = specialized agents: keeper (zookeeper), planner (regurgitation IS task decomposition), snake-1..3 (worker pool), cleanup (scavenger + coprophagy) - no [loop] phase machine; persistent agents self-pace via /loop - README carries the full bio→compute mapping table from the thread image Verified: `agents.py status --config agents.toml` lists all 6 agents + service. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
10 lines
600 B
Markdown
10 lines
600 B
Markdown
# food-0001-reverse-string
|
|
- **task:** Implement a `reverse(s)` function in `pit/scraps/reverse.py` and a pytest that proves it
|
|
(empty string, ASCII, and a unicode string round-trip: `reverse(reverse(s)) == s`).
|
|
- **done-when:** `python -m pytest pit/scraps/test_reverse.py -q` is green.
|
|
- **tossed-by:** keeper
|
|
|
|
<!-- A sample piece of food so the pit isn't empty on first `up`. Snakes devour it per
|
|
pit/README.md: mv it into pit/claimed/<snake-id>.food-0001-reverse-string.md, digest, then
|
|
write pit/done/food-0001-reverse-string.result.md. The keeper tosses real food the same way. -->
|