Conventional systems
Deterministic software for the parts that must never surprise anyone.
Loading…
Conventional & Multi-tool Systems
Classic software and agents that use many tools, working together.
Conventional & Multi-tool Systems
The right tool, including the boring one.
Agents are one part of a system. Around them sit databases, queues and services that do exactly what they are told. We design the whole: conventional software where certainty matters, and agents that can reach many tools where flexibility does.
What we build
Multi-tool agents
Agents that choose among maps, messaging, databases and other tools to finish a job.
The boundary
Deciding which parts must be deterministic and which can be left to judgement.
How we work
01Map the parts
List every step of the job and ask of each one: must this always behave the same way?
02Draw the boundary
Deterministic software takes the steps where certainty matters; agents take the ones that need judgement.
03Connect them plainly
Agents reach maps, messaging and databases through defined tools, and each call leaves a record.
What a person checks
01
Where the boundary sits
Moving a step from software to an agent, or back, is a decision a person makes and can explain.
02
What each tool may do
An agent's reach is set by people in advance, not discovered by the agent along the way.
03
The order of events
When something goes wrong, the record shows what was called, by what, and in what order.
Designing a whole system?
If you are deciding which parts of a job should be certain and which can be left to judgement, we would like to think it through with you.
