Partners: work and revenue in checking the actions of autonomous agents
Organizations hand payments, correspondence and data work to software agents, and they answer for every action an agent takes. Checking an action before it runs is becoming a separate kind of work where information security, law and software development meet, and the customer pays for that work rather than for computation. This page names the roles in which a partner works with the institute and what is available to a partner at once, before any agreement.
Neither a price nor a stake appears on the site: both are set after a conversation, not before it. The page describes what the customer pays for and where the partner’s work lies in it, and it promises no revenue.
What the customer pays for
Revenue goes to an operating company that is set up for the first transaction and receives the right to commercial use of the developments under a license agreement with the institute. The customer pays the operator for four things, and each of them contains work that a person does.
| What the customer pays for | Where the partner’s work lies |
|---|---|
| A monthly subscription for each agent connected to MITR | An integrator connects the customer’s agents and keeps the connection current as the customer adds new agents and new tools. |
| Installation of MITR on the customer’s servers | An integrator surveys the site, places the checking service between the agents and the working systems and hands it the keys to the target systems, so that there is no route around the check. |
| Translation of regulations and rules into MITR contracts, and their updates when the norms change | A lawyer or compliance specialist turns a norm into a rule written as a contract, checks the translation by restating it in plain language and prepares it for signature by the customer’s authorized specialist. |
| A report for a period that an outside reviewer recomputes without the institute’s involvement | An auditor recomputes the receipt chain with the open verifier and confirms to the customer that the decision log has not been edited after the fact. |
There is no charge for an individual check or for a refusal, because otherwise payment would compete with safety. Decisions are made by a solver on an ordinary server processor within milliseconds, with no call to a language model, so the price is driven by connection, translation of norms and support, which is to say by the work of people.
Partner roles
Integrator or security vendor
The partner builds MITR and the receipt log into its own deliveries for security operations centers and development environments. The first piece of work at a new customer is a joint pilot: thirty days of observation, then irreversible actions moved into enforce mode one class at a time. The delivery set and the site requirements are on the page “A pilot of MITR at a customer”.
Web service testing team
The INDRA bench tests web services and programming interfaces with safe probes and turns a vulnerability it finds into a draft rule for MITR. On the internal bench on 25 October 2026 it labeled all 28 scenarios correctly: 14 vulnerable and 14 controls. The partner builds the bench into web service testing for its own customers (the INDRA page is in Russian).
Lawyer or compliance specialist
The solver guarantees that a signed rule is kept, but not that a norm has been translated into the rule completely, and that translation is done by a person. The partner translates the customer’s regulations and the norms that apply to it into contracts, and updates them when the norms change. The norms that bear on an agent’s actions are collected on the page “Who is liable for the mistakes of artificial intelligence” and the pages next to it.
Auditor or independent reviewer
The MITR receipt chain is recomputed by a single file on the Python standard library without any of the institute’s software, and the decisions are replayed by any solver for satisfiability modulo theories (SMT) that reads the common SMT-LIB format. The partner gives the customer what the developer cannot give: a check that does not depend on trust in the developer. The procedure is set out in the “Independent verification protocol”.
Research partner or grant-maker
Joint research, papers and targeted funding are arranged by a direct agreement with the institute. The next paper is being prepared for the Open Conference of the Ivannikov Institute for System Programming of the Russian Academy of Sciences, and the research program is on the “Program” page (in Russian).
Investor
The institute does not issue shares: for a transaction, an operating company is set up and receives a license to the developments. What already works, how it is measured and how to take part are set out on the page “Investors and partners”.
What is available at once, before any agreement
- A learning path of eleven pages leads from what an agent is and how incidents happen to checking an action with a solver; each step says what becomes clear. It starts on the page about what an agent is, and the whole route is in the Knowledge section.
- The open packages mcp-sentinel, iss-ledger-117 and iss-agent-kit are distributed under the Apache-2.0 license: an engineer installs them offline and sees the method on their own scenarios. They contain neither the solver nor the chain with an external time witness, which belong to the full version of MITR (packages and checksums).
- The independent verification protocol gives the commands with which an outsider recomputes the MITR receipt chain on their own machine (protocol).
- The book “Proven Action” sets out the method and the strategy up to 2035, and the glossary of the third generation of information security (IS 3.0) defines the terms (book, glossary).
Why this work is appearing now
Agents no longer only advise: they call tools and make payments, delete records and send letters themselves. The cases on the page “Incidents” show that the damage came from an action, not from a text, and that text filters did not stop it. The organization answers for such an action, so it needs a trace of every decision that a reviewer can check independently. Setting up that check at a customer and keeping it running is work for people, and the partner takes it on.
Contact
A conversation about a partnership starts with a letter to info@isslab.ru or a message to the scientific director on Telegram, @afischuk, with the subject “Partnership”. The next step is usually one of two: a trial installation of the open packages at the partner or a joint pilot at the partner’s customer.
Autonomous non-profit organization “Research Institute of System Synthesis”, edition of 26 October 2026. This page is for information and is not a public offer: the terms of a partnership are set by an agreement.