Government customers: how to commission a test

A state customer needs work with a defined output — an assessment, tests, a report, a method — rather than “AI in general”. So we describe the scope, the timeline and what we do not do.

Procurement starts with a folder, not a promise Procurement starts with a folder, not a promise
Procurement starts with a folder, not a promise

Public procurement is a procedure before it is a technology. The scope of work, the deliverable and the criteria for accepting it are written down first; the model appears inside them, not instead of them.

Legal status matters in advance. While the Institute is being established, no contracts are signed: we discuss the task, its boundaries and the plan, and activity codes and admission are a separate part of the preparation.

The report is written so that it can be attached to an internal audit or handed to a contractor without being retold. The Russian section of the site carries the current legal position for procurement inside the country.

Materials on this topic

Other topics

AI red teaming: what a test shows, and what it does notAI standards: where the rules actually applyAI supply chain: what enters before the model runsMulti-agent systems: behaviour between the agentsIncident chronicle: documented consequences, not forecastsBehavioural audit: how agent behaviour drifts over timePrompt injection: where text becomes an instructionRussian practice: who is held responsible for AIMethodology: how the Institute tests AI systemsData and benchmarks: what our conclusions rest onSociology of AI: relations between the agentsGovernance and funding of the InstituteCases: scenarios of work and what they show

Page updated 02 November 2026 · site build 2026.11.13 · ANO «ISAIS»