A conversation on the subject of this page starts with a message to the scientific director of the institute.
Write to the scientific directorCustom automation: a bot, a website, a service or a software agent that acts by the organization’s rules
The institute builds programs that take routine work off an organization: answering customers, collecting and checking documents, keeping records, moving data between systems and carrying a task through to an action, such as a payment, a record or a letter. The work starts from the customer’s task rather than from a technology: first the thing that costs time or money is named, then the simplest program that removes it is built, and only after that anything complex.
There is no price on the site: it is named after a conversation about the task and a survey, not before. The page describes what is built and how; timing is named after the survey.
What people come with
Five situations that usually open the conversation. For each one the simplest remedy is named; something more complex is built only when the simple one is not enough.
| What is happening | What is built |
|---|---|
| Routine eats the working day: the same letters, requests, reconciliations and reports. | A bot or an assistant that answers by the organization’s own rules, records each request and hands over to a person only what needs a decision. |
| A process rests on one person, and when that person is on leave everything stops. | The procedure is written down as rules and executed by a program; a log shows every step, and the knowledge stops living in one head. |
| Data is spread across systems, such as the accounting program, e-mail, spreadsheets and a messenger, and is brought together by hand. | A link between the systems: data moves by stated rules, and discrepancies are shown rather than lost. |
| A neural network looks useful, but giving it access to data and money is frightening. | A software agent gets access only through a check of every action: the organization’s rule, a refusal with its reason named, and a record of every decision. |
| A website or a service is needed, and contractors promise and disappear, with no way to check the result. | A website or a service with measurable acceptance: speed, availability, forms and calculations are checked by an instrument rather than by a report. |
What is built, from simple to complex
Five steps, each resting on the previous one. The customer stops at the step that closes the task.
- A bot and an assistant. It answers from the organization’s knowledge base in Telegram or on the website, records requests and passes on what needs a decision. The shortest job and the fastest result.
- A website or a service. Pages, forms, calculations, a client area. Acceptance is measurable: response time, availability, forms and calculations checked on agreed examples.
- A link between systems. Data moves between the accounting program, e-mail, spreadsheets and services by rules, with a log of transfers and a reconciliation.
- A software agent under rules. The program carries out a chain of actions itself, such as preparing a document, sending a letter or running an operation, and every irreversible action passes a check against the organization’s rule before it runs.
- A check of every action. The rule is written as data and signed by an authorized person; a refusal names the violated condition; every decision is written to a log that an outsider recomputes. This is MITR, the proven-action system, which has been running at the institute since 24 April 2026.
Steps one to three are built with open tools and ordinary development means. Steps four and five rest on MITR; what it is and how it is proven is set out on the page MITR.
How the work goes
| Step | What happens |
|---|---|
| Conversation | The task is named: what costs time or money and what the result should be. That is enough for a first letter. |
| Survey | Which systems take part, which actions are irreversible, who signs the rules, what counts as acceptance. The survey yields the scope, the timing and the price. |
| Agreement | An agreement with the institute: scope, acceptance procedure, timing, support. |
| Build and acceptance | Every step is checked by an instrument rather than by a report; the work has a log; acceptance runs on the customer’s own examples. |
| Support | Under the agreement: rules and data stay with the customer, and changes are made by the log. |
Rules, data, keys to the systems and the log of the work stay with the customer. What exactly stays with the customer when MITR is installed is set out on the page A pilot of MITR at a customer.
What already works
- The institute’s own setup. Development, checking and record keeping at the institute are done by software agents under the same rules that are offered to a customer, and their actions pass through MITR: 3,877 checks of coding-agent commands, 623 calls from services and 30 requests over the Model Context Protocol as of 25 October 2026. How this is organized is told on the page Institute.
- Legal services. The court-practice analysis system SUDFACT holds 14,899 court acts as of 25 October 2026, and the state-duty calculator computes the duty under the Tax Code of the Russian Federation (both in Russian). Both were built and are run in the way offered to a customer.
- Open tools. The packages mcp-sentinel, iss-ledger-117 and iss-agent-kit under the Apache-2.0 license install without a network; the customer’s engineer sees the method on his own examples before any agreement (packages and checksums).
What this page does not promise
- Timing or price before the survey: they depend on the systems involved and on which actions are irreversible.
- That a neural network does not make mistakes. The program’s action is checked, not its text; a mistake in text remains possible, a mistake in action is stopped by a rule.
- Replacing people. The program takes over execution; decisions, the signing of rules and responsibility stay with the organization’s people.
- Certification. Internal automation does not require it; at significant objects of critical information infrastructure the established procedure applies, and this work does not replace it.
Contact
A conversation about a task starts with a letter to info@isslab.ru or a message to the scientific director in Telegram, @afischuk, with the subject “Automation”. In a first message it is enough to name what takes the time and what the result should be. Correspondence is in English or Russian.
Autonomous Non-Profit Organization (ANO) “Research Institute of System Synthesis”, edition of 26 October 2026. This page is for information and is not a public offer: the scope and terms of work are set by an agreement.