Flownix
Sections

Use cases

Whole situations: who arrives with what, what the human does, what the agent does, and what comes out.

The other sections explain parts of the product. This one shows whole situations: what someone arrives with, what they do themselves, what the agent does, and what ends up on the other side.

Every case names its limits: where it does not fit and where a human is unavoidable. A section without a single "this will not work if…" is advertising, not documentation.

A new product from scratch

An intent and nothing else. Out: a tree of work you can start from.

An existing repository

Code exists, documentation does not. Out: a spec assembled from the code and a mapped system.

Day-to-day work

The project is alive, development is under way. Out: a cycle where the next agent does not start from zero.

Code review

A branch is ready. Out: a review with iterations, linked to tasks.

An agent council

A question one agent answers badly. And an honest list of when a council is not needed.