A response to Eno Reyes' question about agent boundaries, and why I think the durable unit is the work container rather than the agent team.

What Amp's paved-road thesis and Truss Labs' prepared-work-item thesis reveal about Soul CLI, and why the next useful layer is a real case packet for agent work.

A note on wiring Hermes, wallabag, and Soul together without turning every reading workflow into another chat transcript or another vault.

Why I added tasks, runs, worktrees, reviews, and plan-bound execution to Soul CLI, and how they turn AI-assisted development into an auditable local system.

Why Soul keeps registry coordination separate from git, and why remote continuity should mean projection plus promotion rather than distributed writes.

How I built a repeatable link-to-podcast pipeline that extracts a source, writes a spoken two-host script, generates audio, saves notes, and publishes an RSS episode to podcast apps.

How I built an automated, self-healing pipeline that generates a command-line reference directly from the active parser schema without manual translation.

How I structured my local agent environment using isolated execution surfaces, dedicated background runtimes, and a unified file-based session registry.

How I consolidated dozens of loose shell and Python scripts into a single, cohesive command-line tool to manage my agentic workspace.

The rise of CLI/TUIs isn't about nostalgia. It's about building software that agents can inspect, tweak, and extend—something cloud-locked SaaS simply can't offer.