adam — industrial and workplace safety briefings
adam is a deterministic assistant for occupational safety briefings and knowledge checks. It is written in Rust, runs on the enterprise’s own machine and never reaches the network.
What it does
It runs the whole session, not a piece of it:
briefing → knowledge check → assessment (admitted or failed) → protocol
That is the sequence Kazakhstan’s Labour Code article 182 and Order No. 1019 prescribe. Order No. 223, in force since 12 July 2026, permits the check to be conducted remotely.
The corpus holds 33 procedures covering the safety lifecycle an industrial site actually runs. It is not a single procedure but an annual programme of topics: each is briefed, and each is examined.
Industrial, occupational and technical safety — three regimes, one cycle
At a site with hazardous production facilities, workers are trained and examined on three fronts, and these are separate legal regimes with separate deadlines.
Occupational safety and safety technique fall under the Labour Code and Order No. 1019: a knowledge check at least once a year, a repeat briefing every six months.
Industrial safety falls under the Civil Protection Act and Emergencies Ministry Order No. 332: workers at hazardous production facilities are examined annually after at least ten hours of training; managers, specialists and engineering staff once every three years.
One enterprise merges these into a single exam, another spreads them across separate dates. The cycle is the same either way, and adam runs it on any of the three: the content is yours.
Clause 15 of Order No. 332 sets out what software taking an industrial-safety exam must do: entry by personal details and the examinee’s individual number, questions shuffled between variants, no repetition within one test, a timer, and a protocol printed at the end reading passed or failed. adam meets all five — and it does not merely print the protocol, it signs it cryptographically.
The exam itself is held by a training organisation, or by an enterprise training centre holding the attestation, through its standing examination board. adam works inside that order, not instead of it.
Why it works offline
No GPU, no internet. Everything is computed on the spot: 13.6 ms response at the median, 314 MB peak memory. A laptop on Apple Silicon with 8 GB of memory is enough.
For an enterprise that is not a technical footnote but a question about data. Workers’ names, test results and protocols never leave the perimeter, because there is nowhere for them to go.
Kazakh and Russian as equals
The briefing and the knowledge check run in the language the worker chose, from the first question to the protocol. The Kazakh here is not translated from Russian: the system carries its own morphology and lexicon.
There is a voice mode, for people whose hands are busy.
A protocol that can be verified
The finished admission protocol is cryptographically signed and can be verified independently, without coming back to us. In form it is a work-admission credential shaped after W3C Verifiable Credentials.
At the start of a session the camera takes a photograph, and its checksum is sealed inside the admission. That answers the question any inspector will ask: was it this person who sat the test?
How to start
The system is finished. What is fitted to an enterprise is not the system but the content: every industry has its own kinds of work, its own rules and its own briefing programme.
That is what the pilot is — loading your data. You hand over the procedures and requirements in force at your site; the system teaches and examines against those. Not against a general template, against yours.
What it needs from you: one machine, one technical contact and two weeks. What you get: a working admission cycle on your own procedures, and a direct line to the developer.
Write to baimurza.daulet@gmail.com