Delegate only what you can check.
Teqsa is a model-based engineering platform for the age of AI agents.
Who checks what the agents do?
- AI agents arrive with every industrial software product. They know the vendor's data, not your process.
- AI output cannot be released unchecked, and review capacity is the bottleneck.
- Knowledge of existing systems sits in source code and in people's heads.
Agent proposes. Teqsa checks. You decide.
A real run on a small sample model of a field service system.
$ teqsa transact -f required.yaml --format human
operations[0] patch wrote visit-completed.teqsa.yaml
assertions[0] impact failed: failed
failed, wrote nothing
$ teqsa transact -f required.yaml | jq -c '.assertions[0]|{allow,classes,affected}'
{"allow":["documentation-only"],"classes":["contract-breaking"],"affected":6}
$ teqsa transact -f optional.yaml --format human
operations[0] patch wrote visit-completed.teqsa.yaml
assertions[0] impact held
held, wrote visit-completed.teqsa.yaml
- A change to an event is proposed and declared as documentation only.
- Teqsa measures it: the change breaks a contract and reaches six elements. Nothing is written.
- The corrected change adds the field as optional and declares itself as additive. It is written.
What Teqsa is
Its core is the intent layer: one verified, versioned model of a product, the processes around it and the knowledge behind them.
- Model
- One verified, versioned model of the product, its processes and the knowledge behind them, such as requirements, regulations, decisions and open questions.
- Check
- More than 200 automated consistency rules. Contracts and code are checked against the model.
- Trace
- From regulation and requirement to code.
- Change
- A change, by engineer or agent, is accepted only if its declared impact matches the measured one.
- Generate
- Specifications, contracts, database schemas, scenarios and documentation come from the model.
- Reconstruct
- The model is built from scratch or from the code of an existing system. Every legacy behaviour is kept, changed or dropped by decision.
- Release and share
- Versioned releases, and governed access to the model for any agent, your own or a software vendor's.
Six processes, from the first conversation to a release
In every process the agent proposes, Teqsa checks, and you decide.
From practice
The model of Pleqsa, our own fintech and regtech platform, holds more than 7,000 elements, among them over 2,300 specified scenarios, 320 recorded decisions and 136 requirements, every one traced to what realises it.
With Teqsa we also build a heating-equipment manufacturer's field service system for a second country, with every legacy behaviour kept, changed or dropped by decision.
Where we are
- Teqsa is a prototype, in use in our own engineering.
- We look for pilot partners, with one real process each.
- Process vocabulary (ISA-88/95) and readers for PLC code and plant data are our 2027 roadmap.
- Production stays deterministic: agents work in engineering, never in the control loop.