Flownix
Начать
Sections
On this page

The decision lifecycle

From input context to an approved decision: steps isolate independent analysis, collect reviewable objections, and involve a person at the right moment.

  1. 01Version
  2. 02Run
  3. 03Analysis
  4. 04Review
  5. 05Decision
  6. 06Approval
  7. 07Task plan

Typical flow

  1. A person starts a Harness version with a question and links to Flownix nodes.
  2. Roles receive only allowed context and independently create proposals.
  3. Participants test proposals through claims, evidence, and critiques; authors can submit a revision.
  4. A ballot or judge produces a decision, then a human gate accepts, rejects, or sends it back for revision.
  5. An approved decision produces a task-plan draft; applying it to the Flownix tree remains a separate confirmed action.

Two orchestration modes

External host — recommended first

Flownix is the coordination plane: an external agent reads its assignment through MCP, works in its own environment, and publishes structured results.

Embedded runner — target capability

Flownix calls models, builds context, and starts the next step itself. This mode will only be marked available after it ships.