Independent perspective. Global context.

Technology

Who tests AI? Poland joins the effort.

OpenAI and Poland’s NASK National Research Institute announced an agreement on 23 October to explore collaboration on AI safety, security and technical research. NASK’s AI Safety Research Center is to work with the developer on evaluation, vulnerabilities and safeguards.

Archive photo: NASK premises on Kolska Street in Warsaw; not the signing
Archive photo: Adrian Grycuk / Wikimedia Commons · CC BY-SA 3.0 · Source and rights

An agreement to explore joint research

OpenAI and Poland’s NASK National Research Institute announced an agreement on 23 October to explore collaboration on AI safety, security and technical research. NASK’s AI Safety Research Center is to work with the developer on evaluation, vulnerabilities and safeguards. [1]

The stated priorities

The announcement names risks from more capable systems, synthetic content and multilingual challenges. It also describes earlier work with CERT Polska on MikroTik vulnerabilities. The agreement is a research framework, not certification that a model is safe or that a new universal standard has been adopted. [1]

Why independent testing matters

A useful evaluation needs a clear threat model: what can the system do, what could go wrong and under what conditions? Tests should be repeatable and should distinguish a laboratory demonstration from exploitation in the real world. A partnership becomes more informative when it publishes methods, scope and limitations, rather than only a statement of intent. Those are criteria for assessing future work, not claims about results already delivered here.

The questions for deployment

For an organisation using AI, the practical issues include access to tools, handling of sensitive data and escalation when a system behaves unexpectedly. Model-level safeguards are only one layer; deployment permissions and human review shape the outcome too. Future reports from the partners could show what was tested and which weaknesses were fixed. This article is based on the developer’s announcement, not an independent audit. The archive photograph is illustrative and does not show the signing.