compose-orglisted

# Run a task as a liquid-org org (you ARE the runtime) liquid-org treats a *team of agents* as first-class, evolving data: topologies that scored well on past tasks are cached and retrieved for similar new ones. The native way to use it from inside a Claude session is **not** to shell out to another model — *you are already the model*. So: liquid-org tells you **which team to run**, and **you run it** by playing each talent as an independent subagent. No `claude -p`, no API key. > There is also a batch launcher (`liquid-org compose`) for *unattended* runs that > drive the model through an external backend — see "Unattended alternative" at > the end. Prefer the native path below when you're in an interactive session. ## Why subagents (not you role-playing inline) The entire value of an org is that the perspectives are **independent**. An auditor auditing a proposer is only worth something if it didn't write the proposal. If you play every role in one context, the "auditor" already knows what the "proposer" was thinking — that's theater, not a team. So **dispatch a real subagent per talent**: each gets a fresh context and only sees what the topology says it should. ## Requirements & the CLI - **Prerequisite — the `liquid-org` CLI on PATH.** Install the package once: `pip install "git+https://github.com/U0001F3A2/liquid-org.git"` (or, from a clone, `pip install .`). That puts the unified `liquid-org` command (subcommands `plan` / `compose` / `record`) on PATH — the