Skip to content

GCRI · زیرەکی دەستکرد و سیستەمە خۆسەرەکان

AI evaluation and assurance

AI evaluation and assurance engineering is the second method this platform stewards. It provides the evidence that an AI system is fit for a stated use: evaluations, red teaming, documentation, monitoring and the structured arguments that tie them together.

01تۆمارکردن

AI evaluation and assurance on the record.

Method recordSTEM method
  1. ڕێگائەندازیاری هەڵسەنگاندن و دڵنیایی لە زیرەکی دەستکرد
  2. پارێزەرزیرەکی دەستکرد و سیستەم
  3. Applied inArtificial Intelligence and Autonomous Systems
  4. Canonical pageSTEM Commons
02بەکارهێنان

What AI evaluation and assurance engineering does here.

AI evaluation and assurance engineering develops methods to test, monitor and provide justified confidence in AI systems. It addresses performance, robustness, safety and societal impact across the system life cycle. In artificial intelligence and data and compute, AI assurance determines whether automated systems can be trusted in high-consequence settings. It helps manage risks when AI is embedded across finance, health and infrastructure. The canonical description is on the STEM Commons.

Assurance cases for AI systems

Claims about a system’s safety and performance for a use are broken into sub-claims, each supported by evaluation evidence, with gaps and assumptions recorded.

Structured red teaming

Adversarial testing is planned around threat models, with testers, scope, time and findings documented so that coverage can be judged.

Post-deployment monitoring

Incidents, complaints and performance metrics are tracked after release, and triggers for review or rollback are defined in advance.

03چاودێری

Evaluation suite.

The screen a team would use to follow this method: its measures, states and decisions. Names are examples and values are illustrative.

Evaluation suite

AI and autonomous systems · AI evaluation and assurance · Run R-0951

One gate pendingGCRI · Artificial Intelligence and Autonomous Systems

Evaluation suites

Capability58589بڵاوکراوەتێپەڕین
Robustness13372بڵاوکراوەتێپەڕین
Bias and fairness16981بڵاوکراوەتێپەڕین
Misuse red team14279DeployOpen findings

Method card

ڕێگا
ئەندازیاری هەڵسەنگاندن و دڵنیایی لە زیرەکی دەستکرد
مۆدێل
M-196 v1
خاوەن
model risk function
ناونیشان
مۆدێلکراو

دۆزینەوەکان

  1. F-1Unsafe completion on edge promptsMitigation before deploy5 d
  2. F-2Lower accuracy on minority dialectData augmentation9 d
Evaluation suite: the screen’s structure, terms and states for AI and autonomous systems.Example names and illustrative values; a design, not a record or a live system.
04داتا

What the method consumes.

Datasets and records used by AI evaluation and assurance engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

داتاڕۆڵناونیشان
Evaluation resultsEvidence for claimsچاودێریکراو
Red-team reportsFailure discoveryڕاپۆرتکراو
Incident logsField evidenceڕاپۆرتکراو
System documentationScope and assumptionsDECLARED
05ڕێگا و بەڵگە

How AI evaluation and assurance is modelled, measured and tested.

مۆدێلەکە، گریمانەکانی، داتاکانی و نادڵنیاییەکەی، بەو شێوەیەی زانا یان ئەندازیارێک دەیپشکنێت. پێکهاتەکان ڕێگا بڵاوکراوەکان دەگرنەبەر. بەهاکانی کێشراو نموونەییە، نەک دۆزینەوە.

مۆدێل، هاوکێشەکان و گریمانەکان

The model structure used for AI evaluation and assurance, the assumptions it makes and how each is tested.

مەترسیی توخمی iRi = f(Hi, Ei, Vi, Ci)مەترسیدەر، ڕووبەڕووبوون، لاوازی و توانای مامەڵەکردن
زیانی ساڵانەی چاوەڕوانکراوEAL = ∑k pk · Lkover events k with annual probability pk
سیستەمە هاوبەستەکانxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error
گریمانەبۆچی دروست دەکرێتچۆن تاقی دەکرێتەوە
مەترسیدەر و ڕووبەڕووبوون لە ناو پێشهاتێکدا سەربەخۆنئینتێگراڵی زیان بە ئاسانی دەهێڵێتەوەبەراورد بکە لەگەڵ گونجاندنی کۆپیولا لەسەر تۆمارە هاوبەشەکان
هاوبەستییەکان لە نزیک خاڵی کارکردن هێڵینڕێگە دەدات شۆکەکان بڵاو ببنەوە لە Aلە دەرەوەی مەودای هێڵیی شڵەژێنە و بەراورد بکە
چەمکەکانی لاوازی لە شوێنێکەوە بۆ شوێنێکی تر دەگوازرێنەوەچەمکی ناوخۆیی بە دەگمەن بەردەستەلەگەڵ زیانە چاودێریکراوەکان پشتڕاستی بکەرەوە کە هەن
تێکردنەکان
کۆمەڵە داتای وەشانکراو لەگەڵ ڕەسەنایەتی
دەرچووەکان
دابەشبوون، نەک یەک ژمارە
کۆد
بڵاوکراوەتەوە لەگەڵ کارتی مۆدێل و تاقیکردنەوەکان
بەرهەمهێنانەوە
هەمان داتا، کۆد، ژینگە و تۆو
فۆرمۆلەکردنی مەترسی و دۆخ-بۆشایی ستاندارد؛ ئەو گریمانانەی لیست کراون ئاسایین بۆ ڕێگاکە، بۆ پێداچوونەوە ڕاگەیەندراون، نەک ئەنجام.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06پشتڕاستکردنەوە

How results are checked.

Evaluation methods are checked for reliability and relevance to deployment conditions. Independent replication and third-party audits test claims.

بپشکنەHow it is done
پێداچوونەوەی سەربەخۆAssurance cases are reviewed by people not involved in development
Evidence currencyEvidence is re-checked after model or deployment changes
Coverage reportingEvaluations state what they did not test

Benchmarks may not reflect real-world use or novel capabilities. General-purpose systems have open-ended behaviour that resists complete testing.

07پرۆسە

چۆن پرۆسەکە کار دەکات.

Process explorer · Process

AI evaluation and assurance: AI risk management (NIST)

9 steps5 stages1 gate

پرۆسە

AI evaluation and assurance: AI risk management (NIST)

The AI RMF Core has four functions, GOVERN, MAP, MEASURE and MANAGE, with GOVERN cross-cutting; the order drawn is one common reading, not a checklist.

  1. 01 Govern

    1. 01GOVERN: policies, roles and accountabilityStep · AI risk committeeGOVERN is a cross-cutting function. It is infused throughout AI risk management and enables the other functions.
  2. 02 Map

    1. 02MAP: context and intended useDatasetThe MAP function establishes the context to frame risks related to an AI system, including intended purposes and impacts on people.
  3. 03 Measure

    1. 03MEASURE: evaluate trustworthy characteristicsModelAI systems are evaluated for trustworthy characteristics. They should be tested before deployment and regularly in operation.
    2. 04MEASURE: track identified risks over timeModelMechanisms for tracking identified AI risks over time are in place, including unanticipated and emergent risks.
  4. 04 Manage

    1. 05MANAGE: treat risksStepRisk treatment plans cover response to, recovery from and communication about incidents. Resources go to mapped and measured risks.
    2. 06Proceed or not (MANAGE 1.1)Gate · AI risk committeeA determination is made whether the system meets its purposes and objectives, and whether to proceed. The framework sets no thresholds.
    3. 07Deployment decisionDecision · AI risk committeeThe organisation that owns the system decides whether and under what conditions to deploy.
    4. 08Post-deployment monitoring and incidentsModelPost-deployment monitoring plans are implemented. Incidents and errors are shared with relevant AI actors, including affected communities.
  5. 05 Record

    1. 09Inventory of AI systemsDatasetGOVERN 1.6 asks for mechanisms to inventory AI systems. A model card is common practice and is not named in the framework.

Neutral outline of a published external standard or method, from its issuing body. Not a record of operation. Nexus does not perform, certify or approve any step shown. A gate or decision belongs to the party the source names. The actions are not necessarily an ordered set of steps. The EU AI Act is not drawn in this flow.

09پارێزەرایەتی

Who maintains the method.

Artificial Intelligence and Autonomous Systems stewards AI evaluation and assurance engineering for the Consortium and reviews how it is applied across platforms.

10پرسیارەکان

پرسیار و وەڵام.

What are the limits of AI evaluation and assurance engineering in this field?
Benchmarks may not reflect real-world use or novel capabilities. General-purpose systems have open-ended behaviour that resists complete testing.
How are results checked?
Evaluation methods are checked for reliability and relevance to deployment conditions. Independent replication and third-party audits test claims.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method’s use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
ڕاپۆرتەکانبەشداربە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.

GCRIزیرەکی دەستکرد و سیستەمە خۆسەرەکانتەکنەلۆجیای ئێکسپۆنێنشیاڵبەڵگەی Labs
زیرەکی دەستکرد و سیستەمە خۆسەرەکان

ڕێگایەک، کۆمەڵە داتایەک یان پرسیارێک بهێنە.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.