How to Build a Declarative Flow

A practical guide to structuring a declarative flow: defining the tools, setting the order, and establishing the verification contracts.

How do you start a flow?

By defining the expected outcome and the tools required to achieve it. The expected outcome becomes the basis for verification.

How are tools ordered?

The flow specifies the order. The kernel executes them sequentially or in parallel based on the rules defined in the flow.

What happens if a step fails?

Verification catches the failure, the AST engine repairs the tool if possible, and the cycle updates its strategy weights.

What are verification contracts?

They define the expected result for a tool or flow. Without a defined expectation, there is nothing to compare during verification.

Can tools be reused?

Yes. A flow can reference existing tools. A cycle may reuse an existing tool, refine a flow, or produce a new tool.