Teach your agent
to check the whole application.

Reflow connects what your application should do with flows that exercise it and snapshots your agent can compare.

Connect your agent

A knowledge base
for your application’s rules.

Your agent learns how a refund should work and who can invite a teammate. Keep those rules with references to the source, screens and flows that check them.

Explore the knowledge base
reflow / Application knowledgeIllustrative example
team-access.mdRevision 3f2a · example

Team access

Expected behaviorAn invitation keeps the role the owner selected.

Owners can invite teammates as editors or viewers. Accepting an invitation must grant that role.

Referencessrc/team/invitations.ts/settings/team
Exercised by
  1. seed-data
  2. invite-member
  3. verify-role

Selected role = accepted role

Expired invitations: coverage not recorded.

checkout.mdRevision 3f2a · example

Checkout

Expected behaviorCharge the total shown at checkout.

Apply the customer’s discount before payment. The saved order and the receipt must show the same total.

Referencessrc/orders/checkout.ts/checkout
Exercised by
  1. seed-cart
  2. place-order
  3. verify-total

Cart total = payment = receipt

Multiple discount codes: behavior not documented.

refunds.mdRevision 3f2a · example

Refunds

Expected behaviorA full refund restores the balance and returns stock.

The customer receives the amount paid. The order is marked refunded and its items become available again.

Referencessrc/orders/refunds.ts/orders
Exercised by
  1. place-order
  2. refund-order
  3. verify-refund

Balance restored · stock returned

Partial refunds: coverage not recorded.

Connect every part
of the application.

All plugins

Run the graph.
Review the application change.

Declare dependencies, inspect the plan and bring the results into your pull request.