Describe the behaviour you want. It becomes the rule.
Your requirements are written as readable examples. They are tested in every release, on your own branch — and you take in what’s new when you decide.
Scenario: Overdue invoice
Given an invoice 15 days past due
When the agent prepares the reminder
Then the draft waits for my approval
And no email is sent on its own
Read the transcript
Your software changes without asking you. One update, and the way you work stops working.
With Agent Serein, you describe the behaviour you want with simple examples. When an invoice is late, the agent drafts a reminder — but sends nothing without your approval.
That example becomes an automated test, checked on every release. If it fails, the release doesn’t ship.
Organisations get their own branch, with their own scenarios. When a new release comes out, you merge it at your pace — and your scenarios confirm nothing broke.
Every change comes with its evidence: screenshots, differences, results. You approve knowing exactly what you’re approving.
This method is called acceptance test–driven development. To go further, watch the talk.