ayelıne

Guided walk-through

Fourteen flows the product is built around

Walk through each one on the real screens. A bar at the bottom keeps your place; where a flow can go another way, it offers the branch.

Sample data

Deciding

  1. 01Hero

    An agent asks above the line

    The Procurement agent wants an $18,400.00 annual contract with a new vendor. It’s held before any money moves. Emily keeps the idea, changes the terms, and teaches the pact one new rule.

    Who: Emily Carter, CFO

    Walk through : An agent asks above the line
  2. 04

    Nobody decides in time

    Silence never means yes. A held hotel upgrade reminds its owner, asks the backup, and is declined at 4 hours.

    Who: Marcus Reid and Emily Carter

    Walk through : Nobody decides in time
  3. 06

    Decide on a phone at 3 am

    The Cloud agent needs compute during a traffic spike. The lock screen carries the reason; one screen to decide.

    Who: Rachel Hayes, engineering manager

    Walk through : Decide on a phone at 3 am

Rules

  1. 02

    Change a pact in plain words

    Emily writes a rule the way she’d brief a new hire. Ayeline shows how it understood it and replays last month before anything goes live.

    Who: Emily Carter, CFO

    Walk through : Change a pact in plain words
  2. 09

    Look back and roll back a pact

    Every pact version is kept. Compare any two, see the effect on last month, and roll back without losing anything.

    Who: Emily Carter and Marcus Reid

    Walk through : Look back and roll back a pact

Agents

  1. 03

    Add a new agent

    Rachel connects the Cloud agent, gives it a purse and a card, starts from a suggested pact, and watches it for a week before it spends on its own.

    Who: Rachel Hayes, engineering manager

    Walk through : Add a new agent
  2. 08

    Freeze an agent acting strangely

    When an agent behaves unlike itself, one tap stops it. Nothing is lost, nothing queues up silently.

    Who: Emily Carter and Rachel Hayes

    Walk through : Freeze an agent acting strangely
  3. 14

    What the agent sees

    Agents read the pact through the API, ask for permission, and get clear answers with reasons, so they don’t try the same thing again.

    Who: The Procurement agent, and the team that runs it

    Walk through : What the agent sees

Vendors and money

  1. 10

    Approve or block a vendor

    Approve a vendor once and choose which agents may pay it, so they stop asking. Block one, and no agent can pay it.

    Who: Emily Carter and Marcus Reid

    Walk through : Approve or block a vendor
  2. 11

    Dispute a charge and match the refund

    Every payment carries its goal, rule, approver and receipt. When something is wrong, the dispute is one form.

    Who: Marcus Reid, finance controller

    Walk through : Dispute a charge and match the refund
  3. 05

    Close the month

    Marcus starts from 3 exceptions. The other 2,415 payments are already matched to a receipt and a rule.

    Who: Marcus Reid, finance controller

    Walk through : Close the month

Company

  1. 07

    Set up Ayeline for a company

    Connect the card issuer, the accounting and the people who decide. Agents come last.

    Who: Emily Carter, CFO, with IT

    Walk through : Set up Ayeline for a company
  2. 12

    Away, and the backup decides

    When Emily is away, her requests go to Marcus. When she’s back, one summary shows what was decided.

    Who: Emily Carter, with Marcus Reid as backup

    Walk through : Away, and the backup decides
  3. 13

    Report to the board

    Savings and control in one page, built from locked months only, so the board sees final figures.

    Who: Emily Carter, CFO

    Walk through : Report to the board

Fieldstone Supply Co., its people and vendors are fictional.