Agents in your own software,
with people overseeing them.

1. Start with the App, for free.

Use Chirality App on a real job and see what it’s like to direct agents: how they need to be briefed, where they go wrong, and how you check what they produce.

A workflow is instructions an agent can follow. The hard part is describing your problem well enough, and that’s what the App is for: a structured way to talk yourself through the problem, with an agent helping you write the instructions. You don’t need our help for that. The patterns the App walks you through can be a good way to learn how to direct agents, and the instructions it helps you write are plain text, saved on your own machine.

2. Then talk to us about doing it better yourselves.

The harder problem comes when agents go into your own software and people have to oversee them. One agent is easy to watch. As the number grows, you are in effect adding to your headcount, because each agent can change things in your organization much as a person can.

To trust agents at scale, you need controls, and insight into who is doing what, under whose direction, from which instructions, and how the result was checked and validated.

We’ve been answering those questions for ourselves. Two public manuals set out how: Project Management for Human–Agent Teams, and the Chirality Agent User Manual, the guide written for the agents building our own software. They describe how to divide a large job among agents in defined roles, each with its own written brief, and how to keep a record of who prepared what, and under whose direction. We can help you decide how your agents’ tasks are divided, how they’re briefed, how their results are checked, and how people oversee them, so you can add agents without losing track of what they do.

3. Then, if it’s worth investing in, we build it.

When there’s an area worth focusing on, we build software for it: built around your own workflows, with agents that take the same actions people do, at a person’s direction. Every part of it belongs to you. The workflows are plain text, the files stay on your machines, and you get the code, so you can change how the agents behave. No vendor holds your process.

Our pipe stress program, SWBPIPE, is being built that way, and its record is public.