Weaver Guide
A weaver is whoever — or whatever — writes a flow: the directory of Python that says which agents are driven, what each is asked, in what order, and when to stop. This section is everything that role needs. The User Guide is for whoever runs what a weaver made.
If you have not run humanize at all yet, the front page has a quickstart per role: run a flow is the basics of running one, and weave a flow is the shortest flow there is.
Tutorials
Taken in order, each a whole flow written from scratch.
| Build under test | The shortest useful flow there is: a writer, pytest between turns, a reviewer |
| Four agents on a maths problem | Several turns at once, answers held to a shape, and nothing to compile |
Writing a flow
| Writing a flow | The dozen lines that make a directory a flow |
| Loops | Ralph, stateful ralph, and the shapes a loop takes |
| Settings of its own | A pydantic model that becomes a settings sheet |
| Many turns at once | async def run, and awaiting several turns |
| A flow that calls a flow | Composition, and whose agents the inner one gets |
| An atlas | Restricted Python compiled into a typed, resumable prophecy |
What an agent can be asked
| Goals | The backend's own goal feature: it decides when it is done |
| Answers in a shape | A turn that answers with a pydantic model instead of prose |
| Hooks | Python callables hung on the moments of a turn |
| Callbacks as tools | Functions of the flow's own, put in front of the agent |
| The person as an agent | You, driven by a flow like any other agent |
| Worktrees | One agent working in several directories at once |
Checking and publishing
| Checking a flow | Static findings and executable proof before a real turn |
| Testing a flow | Checking the loop without spending a turn |
| Flowverses | A git repository of flows, offered by name |
From the User Guide
A flow sets up the agents it drives, so five pages written for whoever runs one are pages a weaver writes against.
| Concepts | The vocabulary the rest of this uses |
| Security | A flow is Python, and reading one means running it |
| Skills | What an agent carries: its CLI's own, and the ones the flow brings |
| Permissions | Four rungs, from read-only to bypass |
| Efforts | How hard to think — and moving it while the flow runs |
Eleven flows already exist, and reading one is the shortest way to see what a twelfth could be: Flows. For the contract in full — every argument, every refusal, every return — Reference › Flows.